All MeldaProduction effects and MPowerSynth updated to 10.07

[MeldaProduction]

Hi folks,

next update is here . 10.07 is an important update which fixes/improves several problems, but also provides several new features. It is recommended to install this update. To do that, get the newest version from MeldaProduction download page and use it.

See the list of changes for effects and list of changes for MPowerSynth for further information:
http://www.meldaproduction.com/changes/ ... otalBundle
http://www.meldaproduction.com/changes/ ... PowerSynth

[nosucherror]

Sidechain input to MCompressor is very welcome! Couldn't see that new style option though, maybe next time?
Cheers Vojtech.

[provoc]

Sidechain input to MCompressor is very welcome! Couldn't see that new style option though, maybe next time?
Cheers Vojtech.

+1 Thanks for sidechain on MCompressor, this will replace ReaComp as my go to clean compressor for sidechaining

[MeldaProduction]

As for the styles, they will probably wait for V11

[Hanz Meyzer]

Yes, thanks a lot for the sidechain

[Alphacodex]

I also appreciate the sidechain for the compressor, that way the melda compressor can also become my goto basic compressor.

Btw, any chances the waveform view could make it into MAnalyzer. I like it a lot but always need to use MMultiAnalyzer, which introduces the problem that every new instance of MMultiAnalyzer will show up in every other instance, which I dont want often.

Cheers,
Codex

[mcbpete]

As for the styles, they will probably wait for V11

Is V11 gonna have the new-fangled fabled reverb too or is that coming pre-v11 ?

[MeldaProduction]

Alphacodex: the waveform view is available in pretty much all plugins . Just open any, switch the metering section to time-graphs and set it up as you'd like .

mcbpete: It's probably coming with V11, it will take some more time

[Alphacodex]

Oh great! I already found and love it in the other plugins but just not had the odea thet the analyzers have it to :facepalm

[Bobby L'Avenir]

There's a bug in MAutoDynamic EQ in Cubase 9 (win 7), if you use the real-time oversampling modes the cpu doesn't decrease when you disable the plug with the cubase disable button. Only if you totally turn the plugin off completely or deactivate the track does the cpu decrease. You can't disable send or group tracks so it's bit annoying to have to fully turn off each instance instead of just pressing the global disable button after bouncing the tracks before going into a hidden folder. Please fix this asap

Thanks

[MeldaProduction]

That's actually not a bug, but reality - upsampling causes latency. With bypass (which you are probably using, not disable) the plugin needs to continue processing, because it cannot know if you won't automate the bypass, hence it would need to continue immediately (after the short crossfade it uses to smoothen bypassing changes) and since it has latency, it cannot just start, because the start would "happen later" . It doesn't make too much sense to use upsampling in this plugin anyways. Why are you using it?

[alexis1]

That's actually not a bug, but reality - upsampling causes latency. With bypass (which you are probably using, not disable) the plugin needs to continue processing, because it cannot know if you won't automate the bypass, hence it would need to continue immediately (after the short crossfade it uses to smoothen bypassing changes) and since it has latency, it cannot just start, because the start would "happen later" . It doesn't make too much sense to use upsampling in this plugin anyways. Why are you using it?

I thought I remembered VST3 plugs didn't have a CPU hit unless they were processing audio ... incorrect, I guess?

[MeldaProduction]

Well, if the host doesn't send them, then they are not processing audio and they have no CPU hit . Same if you disable them. But if you only bypass them, then they may need to process anyway if there's a latency.

[MirkoVanHauten]

It doesn't make too much sense to use upsampling in this plugin anyways. Why are you using it?

One question out of curiosity: if you think it doesn't make sense, why did you put it in there then? Because you discard other features that doesn't make sense to you too. Why is it in there?

[MeldaProduction]

It may be useful for saturation, some fast modulations, etc. But as I always say - use it only if you hear a difference, not just "because it is supposed to be good", because it's not.