What does the analog knob do in MTurboEQ?

[Hexspa]

I don't know all the ways to analyze a plugin's effect but RMS, harmonic distortion, stereo spread, and frequency response don't tell the whole story like you'd think

According to audio expert Ethen Winer:

Only four parameters are needed to define everything that affects audio quality: Noise, frequency response, distortion, and time-based errors.

You can read the whole explanation here:

https://ethanwiner.com/audiophoolery.html

Of course he's mainly talking about audio (hi-fi) gear, but virtual gear follows the same rules, I would think.

Plugindoctor helps to analyze frequency response and distortion brilliantly. Noise, not so much, and time-based errors not at all. Still, it's a gem of an analytical tool for audio-engineering geeks.

THD+N:

thd-n-small.gif

I read his book, btw. Took awhile though Not sure if you can just subtract THD from THD+N to just get noise, however. Also, I realize it's not in percentages but I don't want to convert it now

[steve2KVR]

@hexspa, I've got all that on hand (use PDR all the time). How did you create the image capture?.../s~

[Hexspa]

@hexspa, I've got all that on hand (use PDR all the time). How did you create the image capture?.../s~

https://www.cockos.com/licecap/

You can only have 1MB per attachment. If your video is larger, go here and use the resize feature:

https://ezgif.com/resize

I set it to 10% and force aspect ratio. Just aim for about 300px wide and it should be fine.

[steve2KVR]

...very cool, thank you for sharing.../s~

[Aesaire]

It does nothing for the low pass filter but here's what it does for the high pass:

mturboeq-hpf-analog.gif

Some models, it appears to do nothing; or at least not for every control.

Before I made this thread I tried a few of the EQs through plugin doctor and it didn't do anything, I must've hit the ones with no response to the analog knob. Thanks for posting the results of the ones that do have an effect.

Would be good to remove the analog button from the EQ's where it doesn't do anything.

[Hexspa]

Yes, I was surprised that there are non-functioning models (and at what the knob actually does).

[Hexspa]

I've submitted a bug report.

[magmagwa]

Basically randomization to emulate instability of analog hardware.

No randomization that I could tell.

Great research, thanks!

[Hexspa]

Ok, so Luke got back to me and basically the Analog knob does something different for each model. It adds harmonics to almost all the bands (except for low pass filters) but only changes the linear response of some bands of some models. If no bands are active then it does nothing. In other words, depending on which bands and models you're using, you might hear a drastic difference or no change at all.

[mark50]

Interesting, thanks.

[Svama]

Is there a difference in the saturation/analog behaviour of mturboeq and mautodynamiceq?
I think, the answer was no, correct?!

[Starship Krupa]

I consider Plugin Doctor to be an essential tool.

It's great for cloning things like EQ curves and compressor behavior. For "black box" plug-ins like the MTurbo line (when using devices), it's helpful for getting a better idea of what all those knobs actually do. You can come up with credible emulations for a number of classic compressors and EQ's using MEQualizer and MCompressor.

It reveals aliasing, therefore determining whether to upsample or not.

One of the things that it can measure is "performance," which confirms that Meldaproduction's plug-ins are typically much easier on the resources. In some cases, such as with the reverbs, they are about even with such FX as iZotope's Nimbus, but seldom if ever do they consume more resources than similar plug-ins from other developers.

Interestingly, according to Plugin Doctor, Meldaproduction FX run a hair more efficiently with High-Quality Upsampling enabled. This is of course counter to what the Meldaproduction docs say, but if there is a difference, it's negligible, so I leave HQ enabled.

[Hexspa]

I consider Plugin Doctor to be an essential tool.

It's great for cloning things like EQ curves and compressor behavior. For "black box" plug-ins like the MTurbo line (when using devices), it's helpful for getting a better idea of what all those knobs actually do. You can come up with credible emulations for a number of classic compressors and EQ's using MEQualizer and MCompressor.

It reveals aliasing, therefore determining whether to upsample or not.

One of the things that it can measure is "performance," which confirms that Meldaproduction's plug-ins are typically much easier on the resources. In some cases, such as with the reverbs, they are about even with such FX as iZotope's Nimbus, but seldom if ever do they consume more resources than similar plug-ins from other developers.

Interestingly, according to Plugin Doctor, Meldaproduction FX run a hair more efficiently with High-Quality Upsampling enabled. This is of course counter to what the Meldaproduction docs say, but if there is a difference, it's negligible, so I leave HQ enabled.

I never figured out how to read the performance graph. Any tips?

[Starship Krupa]

Hmm. Yeah, I'm not sure what it's doing under the hood, I just go by the milliseconds graph on the left. Assuming that it measures how fast and hard it's hitting the CPU.