All MeldaProduction effects and MPowerSynth have been updated to 9.02

[MeldaProduction]

Hi folks,

next update is here . 9.02 comes with several minority fixes, performance improvements, and some new features as usual. It is highly 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/?id=MTotalBundle
http://www.meldaproduction.com/changes/?id=MPowerSynth

[lachrimae]

Thanks for the update Vojtěch. The sonogram/super-res response is noticeably better!

Is there any chance you'd consider adding a Static button to MMultiAnalyzer like you have in MAnalyzer? I often compare waveforms between different tracks and the moving waveform makes me dizzy .

I find the static version to be much more useful for analysis:
http://i.imgur.com/PMRDZ5G.gif

Thanks!

[Tagirijus]

You are so incredible! I asked about this "velocity affects ADSR immediately" and what was implemented? (the "interpolate" option in the MIDI section) ... just incredible ... thank you sooo much for this customer-oriented philosophy, seriously!

[MeldaProduction]

My pleasure and thank you folks!

lachrimae: The "static" analysis is I'm afraid not possible. I actually like it more as well, but there are some serious problems with synchronization between the tracks. Simply put, the plugin never knows if the host doesn't give it more/less samples than the other tracks due to bypassing for example. In that case it immediately gets out of sync and there seems to be no way to get it back in sync... complicated world

[Lesha]

Could you explain "Equalizer band settings slightly reduced"?

Thanks

[MeldaProduction]

I think he meant MAutoDynamicEq with negative band dynamic gain (vertical node).

[Lesha]

So, MAutoDynamicEq is the only plugin which is affected by EQ band settings reduction?

[MeldaProduction]

And MDynamicEq

[Lesha]

Thanks

[geronimo]

Hello _

I discovered your label and decides to install your application just to try MPowerSynth: loading the Application (maudioplugins_9_02_setupmac) while following his instructions.
I'm on with a Mac under Mac OS X 10.7. LION and wishes to use MPowerSynth with Digital Performer 8.07: at the launch of DP8, MPowerSynth is not recognized and not scanned by MOTU Application. I turn off my machine and on again but no improvements .

Finally, I reinstall MPowerSynth by changing his installation location :
HD / Library / Application Support / Audio / Plugins / Components _

Then I run D.P. 8 and MPowerSynth actually recognizes and allows me to try it .

[elassi]

Perfect service. Thx Vojtech!

[MeldaProduction]

My pleasure elassi!

geronimo: Interesting, what is your AU components path? What you wrote doesn't seem correct.

[geronimo]

I think I was lucky during my installation in two stages.

A first time, the installer has everything arranged in HD / Library / Application Support and nothing in the Components folder. So normal that Digital Performer or another audio application don't find MPowerSynth.

Installing a second time when I change the installation location by stating my Components folder.

And then Digital Performer 8 find your MPowerSynth !

[MeldaProduction]

That's odd, because the paths to components can NOT be configured on OSX, they are predefined. The installation destination only contains uninstaller. My guess would be that you forgot to check MPowerSynth the first time, or disabled AU, who knows... Anyway I'm glad it is ok .

[geronimo]

My guess would be that you forgot to check MPowerSynth the first time, or disabled AU, who knows... Anyway I'm glad it is ok .

Ah, OK I understand: during the fist installation, I have fine checked the MPowerSynth choice but there is a detail that seemed odd: you can select the AU version by clicking on it and checking the small blue square.
That certainly small blue square that I forgot the first time .