MautoEqualizerLinearPhase and MSpectralDynamics questions

[pheeleep]

I have been playing with MautoEqualizerLinearPhase and MSpectralDynamics and... well...

You are a genius Vojtech!

I have a question regarding the "modes" of MautoEqualizerLinearPhase.

The first mode, "normal", what is this? On a song I am working on, the Fl Studio CPU counter hits 31% when I use the "normal" mode.

Linear Phase. This is the best mode, correct? When I use it, CPU usage is 32%. Only 1% more than normal mode.

Linear Phase FFT based. This is what would be considered "crap" compared to linear phase mode, correct? If so, why does it use more CPU then the linear phase mode? CPU hit is 37%.

I notice that the latency is the same for all 3 modes.

So my question is...

Is there a reason anyone would want to use anything but the linear phase mode? I am curious.



On another note, I LOVE the Equalizer in MSpectralDynamics ( drawing the frequency) and being able to attenuate the sound by 80db! I was able to isolate a kick drum by making a "hole" in the spectrum using the EQ and by moving it until I no longer heard the kick. This allowed me to know exactly which frequencies the kick occupied. And doing this was a lot easier than with a standard EQ since you can litterally cut out a whole chunk of frequencies that you can make completely inaudible. Any chance of adding -80db attenuation in MAutoEqualizer?


Finally, this time regarding MSpectralDynamics. Using the EQ. Let's say I add some points and create a vertical line. I notice if I hold the bottom point and drag to the left, the top point follows, so the line stays vertical as I move it to the left. But this doesn't work when I move the bottom point to the right. The top point doesn't follow so the line doesn't stay vertical and I have to keep adjusting the top point and bottom point to make the line straight (vertical) again once I move one of the points. Could you add the little drag arrows that you have for moving the threshold up and down in the graph to the EQ vertical line?( when you hover over the threshold line, the little arrows appear, and when you then click and move the line, it moves up and down horizontally).

If I created a vertical line with the equalizer, I'd like to be able to hover over the line it, have the arrows appear, click and drag the vertical line and both points would follow in the same way.



Some additional comments:

I want to say that MAutoEqualizer (not the linear phase version, but the zero latency version that is also included with MautoEqualizerLinearPhase) has quickly become my very favorite EQ. My favorite "transparent" EQ. Sorry fruity PEQ2...

I haven't tried the Soft Saturation yet, but I know you can add some analog EQ emulation. I have a lot of colorful EQ's that I love, but I'll make sure to give it a go


I explored the deeper functions last night, analyzing a drum pattern and comparing it's frequencies to a bass line, to make them "unclash" and I have to say the results are better than what I though possible. A little fine tweaking here and there and I ended up with some very nice results.

Finally, MSpectralDynamics. Man, what a nice plugin.. Ha, I wish there was a zero latency version of this (I know it's not possible..... yet?).
Awesome mastering plugin...

I MeldaProduction!!!!!!!

[wetdentist]

i am also a big fan now of MeldaProduction (as owner of their incredible CreativeBundle) and am stunned sometimes, well, oftentimes, by the innovation going on with their software.

[pheeleep]

I am also the proud owner of the creative bundle It's what got me hooked on MeldaProduction products.

My favorite plugins, bar none. I find myself turning off built in synth effects and using the Melda ones instead all the time now, on top of using them on samples, recorded audio, etc. They are stellar.

MeldaProduction has become my favorite audio software company. Next would be Image-line and Applied Acoustics. I could blindly buy a Melda plugin without even trying it at this point, and I usually always try demos first..

I only discovered MeldaProduction a few months ago, and I am so glad I did. Everything Vojtech makes is brilliant. Some companies offer one or two great products and then a bunch of average products, but Vojtech consistently delivers super high quality, innovative, great sounding, low on the CPU plugins. How could I resist...

I am a fan of this company, and proud to be! I hope more people try the demos, and I hope we see more activity on this forum in the near future. It's awfully quiet in here... Let's talk Melda, shall we?

[AL321]

Finally, this time regarding MSpectralDynamics. Using the EQ. Let's say I add some points and create a vertical line. I notice if I hold the bottom point and drag to the left, the top point follows, so the line stays vertical as I move it to the left. But this doesn't work when I move the bottom point to the right. The top point doesn't follow so the line doesn't stay vertical and I have to keep adjusting the top point and bottom point to make the line straight (vertical) again once I move one of the points. Could you add the little drag arrows that you have for moving the threshold up and down in the graph to the EQ vertical line?( when you hover over the threshold line, the little arrows appear, and when you then click and move the line, it moves up and down horizontally).

If I created a vertical line with the equalizer, I'd like to be able to hover over the line it, have the arrows appear, click and drag the vertical line and both points would follow in the same way.

This is something that affects all Melda modulation, i think.
A node can move points on it's left out of place, but not points on it's right. Personally, i think a node should not be able to knock any other nodes out of place. Many times, i've spent 10 - 15 minutes+ getting a node in the perfect position, and then later on i accidentally knock it out of place with another node. Quite annoying.

So i agree with Pheeleep on the vertical line, but i would also like some way of locking nodes in place, or not have them affected by the movement of other nodes.

Also, Pheeleep brought up the spectrum analyzer in another thread. Well, i really think you need a way to hold peaks permanantly, so they don't fade back down over time. I know you put in a freeze function, but that completely freezes the whole analyzer, rather than just holding the peak.
I like to be able to watch the held peak, while making EQ changes, and comparing the held peak to the realtime peak. Not possible with your plugin at the moment. Ideally, i would like to be able to copy the held peak to 'B', and compare it with a new held peak on 'A'.

I'm actually a perfectly happy Blue Cat analyzer user, but it would be nice to able to use the Melda one for a second opinion.

[pheeleep]

i would also like some way of locking nodes in place, or not have them affected by the movement of other nodes.

+1

Maybe right click a node to select a "lock it" option, and everything that is not locked would still move?

[MeldaProduction]

I have been playing with MautoEqualizerLinearPhase and MSpectralDynamics and... well...

You are a genius Vojtech!

Hehem thank you!

I have a question regarding the "modes" of MautoEqualizerLinearPhase.

The first mode, "normal", what is this? On a song I am working on, the Fl Studio CPU counter hits 31% when I use the "normal" mode.

Linear Phase. This is the best mode, correct? When I use it, CPU usage is 32%. Only 1% more than normal mode.

Linear Phase FFT based. This is what would be considered "crap" compared to linear phase mode, correct? If so, why does it use more CPU then the linear phase mode? CPU hit is 37%.

I notice that the latency is the same for all 3 modes.

So my question is...

Is there a reason anyone would want to use anything but the linear phase mode? I am curious.

Yeah, it's probably not self-explaining enough - "normal" mode is minimum phase with latency compensation. That's also why it is the fastest one. FFT based was the first developed as linear-phase, obviously, because it is extremely simple and most cheap lpeqs use it. Linear-phase mode is definitely the best one and it is most like a matter of design, which makes it almost as fast as minimum phase. And it is definitely better LP eq.

For me the question is "LP or minimum phase"? I don't use FFT, but it may serve for comparison. Who knows, maybe it is better sometimes .

On another note, I LOVE the Equalizer in MSpectralDynamics ( drawing the frequency) and being able to attenuate the sound by 80db! I was able to isolate a kick drum by making a "hole" in the spectrum using the EQ and by moving it until I no longer heard the kick. This allowed me to know exactly which frequencies the kick occupied. And doing this was a lot easier than with a standard EQ since you can litterally cut out a whole chunk of frequencies that you can make completely inaudible. Any chance of adding -80db attenuation in MAutoEqualizer?

Well, here I strongly suggest you read the eq tutorial at

http://www.meldaproduction.com/audiotut ... lizers.php

There is an explanation, why this processing should be avoided. The thing is, you removed the kick using such a super-strong low-pass, but the problem is what you didn't hear - the eq creates a huge "ripple in the passband". There are methods for designing convolution filters providing small ripple ( in fact one of them will be part of the MMutliBandConvolution to be released ), but this concerns only specific filters, such as low-pass, not generally any shape you want (well, that's definitely possible as well, somehow, but I'm not aware of any reasonable method).

Also with a parametric eq like MAutoEq it is impossible to add any attenuation. You can create a higher order filter by combining multiple high-pass filters for example.

Finally, this time regarding MSpectralDynamics. Using the EQ. Let's say I add some points and create a vertical line. I notice if I hold the bottom point and drag to the left, the top point follows, so the line stays vertical as I move it to the left. But this doesn't work when I move the bottom point to the right. The top point doesn't follow so the line doesn't stay vertical and I have to keep adjusting the top point and bottom point to make the line straight (vertical) again once I move one of the points. Could you add the little drag arrows that you have for moving the threshold up and down in the graph to the EQ vertical line?( when you hover over the threshold line, the little arrows appear, and when you then click and move the line, it moves up and down horizontally).

If I created a vertical line with the equalizer, I'd like to be able to hover over the line it, have the arrows appear, click and drag the vertical line and both points would follow in the same way.

I think you can do that by selecting both points. Just click outside any point and drag a selection rectangle. Then you can move both points.

With the line dragging - the trouble is the lines can already be dragged vertically and that's intentional, since from my experience in most cases like this you want the X coordines not to change.

Some additional comments:

I want to say that MAutoEqualizer (not the linear phase version, but the zero latency version that is also included with MautoEqualizerLinearPhase) has quickly become my very favorite EQ. My favorite "transparent" EQ. Sorry fruity PEQ2...

I haven't tried the Soft Saturation yet, but I know you can add some analog EQ emulation. I have a lot of colorful EQ's that I love, but I'll make sure to give it a go


I explored the deeper functions last night, analyzing a drum pattern and comparing it's frequencies to a bass line, to make them "unclash" and I have to say the results are better than what I though possible. A little fine tweaking here and there and I ended up with some very nice results.

Finally, MSpectralDynamics. Man, what a nice plugin.. Ha, I wish there was a zero latency version of this (I know it's not possible..... yet?).
Awesome mastering plugin...

I MeldaProduction!!!!!!!

Hehe thank you!!!
Though I'm afraid MSpectralDynamics cannot be zero-latency . Once I though I invented a pitch-shifting algorithm with zero-latency. Well, it took a few hours and I found out, that cannot really work ...

[MeldaProduction]

This is something that affects all Melda modulation, i think.
A node can move points on it's left out of place, but not points on it's right. Personally, i think a node should not be able to knock any other nodes out of place. Many times, i've spent 10 - 15 minutes+ getting a node in the perfect position, and then later on i accidentally knock it out of place with another node. Quite annoying.

So i agree with Pheeleep on the vertical line, but i would also like some way of locking nodes in place, or not have them affected by the movement of other nodes.

Okay, lock added to to-do .

Also, Pheeleep brought up the spectrum analyzer in another thread. Well, i really think you need a way to hold peaks permanantly, so they don't fade back down over time. I know you put in a freeze function, but that completely freezes the whole analyzer, rather than just holding the peak.
I like to be able to watch the held peak, while making EQ changes, and comparing the held peak to the realtime peak. Not possible with your plugin at the moment. Ideally, i would like to be able to copy the held peak to 'B', and compare it with a new held peak on 'A'.

I'm actually a perfectly happy Blue Cat analyzer user, but it would be nice to able to use the Melda one for a second opinion.

Well, I'll see what I can do .

[pheeleep]

Thanks for your replies Vojtech! Very helpful info

I am still wondering why the FFT method takes the most CPU, but I can live without knowing, since I will be avoiding this setting

[MeldaProduction]

Thanks for your replies Vojtech! Very helpful info

I am still wondering why the FFT method takes the most CPU, but I can live without knowing, since I will be avoiding this setting

My pleasure. And well, it's the FFT algorithm...
Btw. you said 31% - I hope this was overall. Or the single instance of the plugin took so much???

[pheeleep]

Ha. Yes of course I mean overall That was after inserting the plugin in an already well developed project I'll have to check but I think 1 insance in linear phase mode only eats up 2% CPU on my quad core.

[MeldaProduction]

Uf, thanks god .