Betaversion of update for all MeldaProduction effects to 3.00 including VST3 support released!

[MeldaProduction]

Hey folks,

so here is hopefully one of the last updates for some time. The version number is now set to 3.00 for all effects and bundles to minimize confusion. There have been many kernel changes, bug fixes, performance optimizations as well as several new features, such as smart-learn for modulators and multiparameters.

It seems stable, however I'd be glad if you could update and let me know ASAP if everything seems fine. I don't want to rush it this time, however I'd like to release alpha version within a week or so.

See http://www.meldaproduction.com/mtotalbundle/ for info about changes.

Thanks in advance!

[AL321]

Everything seems to be ok here in FL Studio, though i noticed that my cpu is spiking an extra 4 or 5% compared to the previous version. That was with Multidynamics, Multidelay, reverb, flanger and a couple of EQs.
But that said, you seem to have done something to fix multiparameter automation for me in FL. That wasn't working for me in other versions, but it's working now. So could that maybe be what's causing the extra cpu?

Well, either way, i'm happy i can use multiparameter now, and the copy/paste modulation is a great addition. Helps a lot.
And i really hope this is the last update for a long time! I think you need to start building a DAW or something.

Btw, i don't use VST3, but i noticed that the reverb (not multiband) didn't install a VST3 version, and during the install, the reverb was the only plugin to have that area blanked out.
Just thought i'd let you know, in case you forgot something.
And is there a reason VST3 is defaulted to Common Files instead of Steinberg/Cakewalk whatever? I changed it to Cakewalk. Hope it doesn't mess things up.

[MeldaProduction]

Everything seems to be ok here in FL Studio, though i noticed that my cpu is spiking an extra 4 or 5% compared to the previous version. That was with Multidynamics, Multidelay, reverb, flanger and a couple of EQs.
But that said, you seem to have done something to fix multiparameter automation for me in FL. That wasn't working for me in other versions, but it's working now. So could that maybe be what's causing the extra cpu?

Ha! It takes 4-5% for every plugin?? Or together?

Well, either way, i'm happy i can use multiparameter now, and the copy/paste modulation is a great addition. Helps a lot.
And i really hope this is the last update for a long time! I think you need to start building a DAW or something.

Hehe, DAW not, but there are some unique ideas waiting to be done for a long time, so I hope when this gets alpha it really will be for a long time .

Btw, i don't use VST3, but i noticed that the reverb (not multiband) didn't install a VST3 version, and during the install, the reverb was the only plugin to have that area blanked out.
Just thought i'd let you know, in case you forgot something.
And is there a reason VST3 is defaulted to Common Files instead of Steinberg/Cakewalk whatever? I changed it to Cakewalk. Hope it doesn't mess things up.

So MReverb hasn't been installed as VST3? I'll check it out. Generally I don't like VST3 either. Steinberg did it just to mask Cubase easier to develop I believe and the only advantage I know is side-chaining & GUI resizing. And there are also several flaws compared to 2.4.
Anyway according to Steinberg, Common Files is THE folder for the plugins, though if you use to with specific host, you can install it anywhere basically .

[MeldaProduction]

I checked the CPU usage and honestly I found nothing really suspicious. With linear-phase crossover everything is much faster now (5x indeed). With analog crossover the differences were usually about 0.01%. Though with MMultiBandDynamics I measured 0.18% worse with 6 bands and 0.04% better with single band. Anyway none of this is really a significant difference IMHO. I used Reaper (because it has percentual meters) on AMD Phenom x4 2.5GHz, 32-bit versions.

Could you please recheck? The previous versions are still available at
http://www.meldaproduction.com/download ... _setup.exe
(I'm not sure if you are using MTotalBundle though, so if not just change the name )

I mean 4% degradation per plugin, that would be way too much unless you are using 600Mhz pentium .

[AL321]

Not at my computer right now, but it's a 2.66ghz dual core, if i remember right. And don't worry, it wasn't 5% per plug. It was overall. My post would not have been a happy one if that was per plug! I don't think i can test again for you, because i bounced some things down to audio, to stop the occassional glitching that started, but to be honest, it might not be worth worrying about. I restarted windows after installing, so it might be that some windows processes were starting up and taking cpu (just a thought).

[MeldaProduction]

Aaaha, ok, well, if you are happy, then I'm happy . And if you'd become unhappy, please just let me know .

[valsolim]

Hello, Vojtech,

I have just tested the beta version of MCreativeBundle and here are my comments:

1. Preset Change via MIDI Program Change does not work for the VST3 version of the plugins. However, it works okay for the VST2 version.

2. MMultiBandHarmonizer - MIDI Control for the harmony section works flawlessly (thanks a lot!), however, it would be nice if the plugin responded to "All Notes Off" message (MIDI CC #123). This enhancement would be very useful for me since I need to control the harmony via a MIDI foot controller and it is a bit awkward to send individual Note Off messages from this device.

3. A minor bug in the installer (Windows 32bit): In the Start/Programs/MeldaProduction/MCreativeBundle menu the links to the PDF documentation are missing for the following two plugins: MMultiBandFlanger and MMultiBandHarmonizer.

Anyway, once again I thank you a lot for all the new features!

Best regards
--
Miloslav

[Pat2070]

As always, flawless victory from Vojtech!

Would we be able to have the option to switch off the default modulator/multiparameter assignment which is currently set to Dry/Wet?

It's frustratinging every time I go to assign a control, I have to switch off the dry/wet assignment. It kind of gets in the way of the fast learn control you've just implemented too, as we need to unassign the dry/wet once we've assigned a different control.

Thanks!

Pat

[MeldaProduction]

Hello, Vojtech,

I have just tested the beta version of MCreativeBundle and here are my comments:

1. Preset Change via MIDI Program Change does not work for the VST3 version of the plugins. However, it works okay for the VST2 version.

Well, there is the problem with VST3 standard... Steinberg really made MIDI crazy ugly piece of s***, many things are even impossible. I'll see what I can do.

2. MMultiBandHarmonizer - MIDI Control for the harmony section works flawlessly (thanks a lot!), however, it would be nice if the plugin responded to "All Notes Off" message (MIDI CC #123). This enhancement would be very useful for me since I need to control the harmony via a MIDI foot controller and it is a bit awkward to send individual Note Off messages from this device.

Ok . Though again I'm not sure if VST3 could do it, I hope so.

3. A minor bug in the installer (Windows 32bit): In the Start/Programs/MeldaProduction/MCreativeBundle menu the links to the PDF documentation are missing for the following two plugins: MMultiBandFlanger and MMultiBandHarmonizer.

Anyway, once again I thank you a lot for all the new features!

Best regards
--
Miloslav

Oukey doukey . And my pleasure

[MeldaProduction]

As always, flawless victory from Vojtech!

Would we be able to have the option to switch off the default modulator/multiparameter assignment which is currently set to Dry/Wet?

It's frustratinging every time I go to assign a control, I have to switch off the dry/wet assignment. It kind of gets in the way of the fast learn control you've just implemented too, as we need to unassign the dry/wet once we've assigned a different control.

Thanks!

Pat

Thanks Pat .
About the default assignment - well, what is so wrong about it? If you use "clear and learn" it destroys the parameter. Are if you are editing it saves the time you would need to enable it.

Anyway it cannot be removed. It can potentially be disabled by default, but obviously there are disadvantages and I don't see any advantages here.?

[Pat2070]

Doh!

Clear and learn does the trick nicely.

[valsolim]

1. Preset Change via MIDI Program Change does not work for the VST3 version of the plugins. However, it works okay for the VST2 version.

Well, there is the problem with VST3 standard... Steinberg really made MIDI crazy ugly piece of s***, many things are even impossible. I'll see what I can do.

Yes, VST3 has some unexpected limitations as to which MIDI messages can be recognized by the plugin. However, I think there should be a possibility to make use of the new VST3 "Program Lists" concept to facilitate this functionality. I suppose that in VST3 it should not be done directly via MIDI but via some automation parameters instead. Maybe it is implemented already now in your VST3 plugins, however, I forgot to see which automation parameters do your VST3 plugins expose to the host. And I believe that the host can transform the incoming Program Change messages to the corresponding automation parameters responsible for switching the "Program Lists". So, this should be a workaround, I think

--
Miloslav

[MeldaProduction]

Yup, you are right. Honestly I don't know why Steinberg messed things up this way. Program change is coded from 128 values to 0..1 and I believe 99% plugins will have to decode it back to 128 values simply because every other interface does it that way. And I really don't understand aftertouch for example - the value should be assigned to a key being played, but there is none... Well, Steinberg, this wasn't really the greatest concept. But otherwise VST3 is pretty nice, finally (especially compared to Apple's crazy AU, which cannot be even considered SDK IMHO...)

[valsolim]

And I really don't understand aftertouch for example - the value should be assigned to a key being played, but there is none...

Well, according to the MIDI specification, there are two versions of "Aftertouch": 1. Key Pressure which is, indeed, assigned to a key, and 2. Channel Pressure which has no particular key assigned.

--
Miloslav

[MeldaProduction]

Well, then there is a question how to transfer the key aftertouch...