MeldaProduction

Svama · Post by **Svama** » Fri Sep 29, 2017 4:39 am

Hi Vojtech,

a small, but handy one. Is it possible to change the position of the lp filter in the upper left corner to the upper right corner. Less mouse movement.

Thanks and greets,
Marek

DarkStar · Post by **DarkStar** » Fri Sep 29, 2017 11:30 am

You mean the LP filter drop-down list, I guess. I believe that that would not fit in with the standard layout of common tools to the right.

Just thinking out loud (but this may not be possible either:

-- display the current filter slope value on the red flags,
-- display the drop-down selection list on right-clicking the flag,
-- and make the drop-down list thinner.

==>> less visual clutter

Svama · Post by **Svama** » Fri Sep 29, 2017 11:38 am

Hi Darkstar,

great idea. It’s a bit of cosmetic, but also a workflow winner.

alexis1 · Post by **alexis1** » Sat Sep 30, 2017 1:41 am

I don't know if it's better etiquette to post here, or start a different thread about MAutoDynamicEQ, sorry if I made the wrong choice:

I find when I click-hold on the red lines of the hpf/lpf, for example to read the value, the frequency of the red line shifts a little bit. It's not a mouse problem in general, only happens in this circumstance.

Anyone else?

MeldaProduction · Post by **MeldaProduction** » Wed Oct 04, 2017 11:34 am

DarkStar: Easier said than done

. I'll check.

alexis1: When you click on it, you probably move the mouse already a bit, so... It's actually really hard to click without moving

. But it may set the value already, not sure. Try holding Ctrl (finetuning).

DarkStar · Post by **DarkStar** » Wed Oct 04, 2017 11:43 am

MeldaProduction wrote:DarkStar: Easier said than done . I'll check.

That's my thing

alexis1 · Post by **alexis1** » Wed Oct 04, 2017 12:32 pm

MeldaProduction wrote:...
alexis1: When you click on it, you probably move the mouse already a bit, so... It's actually really hard to click without moving . But it may set the value already, not sure. Try holding Ctrl (finetuning).

Hi, thank you for reply!

Actually I don't use a mouse, I use a trackball "rat", so there is actually no motion associated with clicking. That's why I don't understand why there is changing of the value with clicking!

I guess maybe from lack of response I'm the only one this happens to, somehow ...

.

I'll try holding down CTRL next time, thank you for the hint ...

MeldaProduction · Post by **MeldaProduction** » Wed Oct 04, 2017 1:28 pm

It's quite possible that the system automatically sends mousemove notification, so the plugin responds by placing the filter at the exact position defined by the mouse.

nosucherror · Post by **nosucherror** » Wed Oct 04, 2017 1:29 pm

Hey Dark Star,
I really like that drop down menu idea. +1

Soarer · Post by **Soarer** » Fri Oct 06, 2017 4:55 pm

May I too make a request here?
Any chance we can have one more band in MAutoDynamicEQ? I'm EQing my own field recording sounds in an audio editor and find that I often use up all 7 bands. So at least one more band would be great. Bands not used are turned off anyway so I assume there'll be no extra resources used.
Just for a comparison, FF Pro-Q 2 has up to 24 bands (not dynamic though).

Another thing: I'd like there to be a clear indicator (typically yellow) on all input/output meters when the signal is clipping. Presently as far as I can see on the red graphical top part of the meter it's not possible to see if a signal hits 0 dB or is clipping (apart from the readout down at the bottom of course).

steve2KVR · Post by **steve2KVR** » Fri Oct 06, 2017 5:19 pm

...fwiw...on an acoustic guitar track a client brought in and insisted on using (rather than re-track), I ended up using MSD for room noise, and then followed by two instances of MADEQ to remove "resonances/squeaks/etc"...it "worked" (sigh)...hth.../s~

MeldaProduction · Post by **MeldaProduction** » Mon Oct 09, 2017 10:02 pm

I agree that sometimes the 7 bands are not enough. Right now there's a certain limitation to the automation system, so it's a no. But I'd like to make a brutal kernel restructuralization which I'm scared of for a long time

, and that would then be possible, so we'll see

. I personally think that if you need so many bands, multiple instances should be the best option anyways. The situation is likely to be what steve says - one instance for the sculpting, another for resonances and other detail stuff.
As for clipping indicator, I'm not sure, I think the readout should be enough. It doesn't matter after all, we are in digital domain, so worry not

.

Soarer · Post by **Soarer** » Tue Oct 10, 2017 9:23 am

Alright, I’ll use two instances -for now!

. Just thought I’d mention it.

But what would be the harm of just having a single yellow line or other indicator at the top of the meter? It would make it much easier to spot when there is clipping.

MeldaProduction · Post by **MeldaProduction** » Fri Oct 13, 2017 3:50 pm

Well, it's a bit more complex than that I'm afraid

. Long story. To be honest, the level of busy-ness right now is through the roof, so I just cannot allocate anything if it's not really important...sadly...

Soarer · Post by **Soarer** » Fri Oct 13, 2017 4:06 pm

Busy-ness through the roof is definitely 100% top priority, yes!

No problem then. I'm always exited to see what you will come up with next.
Also remember to breathe deeply - and drink lots of water! Don't stress!

MeldaProduction

KVR Audio

MautoDynamicEq Feature Request