MeldaProduction

MeldaProduction · Post by **MeldaProduction** » Sat Mar 04, 2017 5:40 pm

So, automation has been solved using a compatibility mode, but I'm still holding on to changing plugin names. It turns out, interestingly, that hosts actually ARE using the plugin identifiers instead of plugin name, so it was indeed possible to change plugin names and the host successfully switched to the new plugin. I tried all major hosts on Windows:

Cubase, ProTools, Live, Studio one, Reaper, FL studio, Sonar

I assume on OSX it will be similar, I think Logic will work well.

I'd like to do following changes:
- MMultiBandxxx => MxxxMB, for example, MMultiBandAutopan => MAutopanMB
- MLimiter => MSaturator, and perhaps MDynamicsLimiter => MLimiter ?

Are you OK with this or do you see any problems? Any further plugins to rename (only necessary ones please)? Note that we cannot really merge plugins as I was hoping for for instance.

jmg8 · Post by **jmg8** » Sat Mar 04, 2017 5:43 pm

How about renaming MFilter? it feels more like an EQ

MeldaProduction · Post by **MeldaProduction** » Sat Mar 04, 2017 5:52 pm

jmg8 wrote:How about renaming MFilter? it feels more like an EQ

Well, it actually is an EQ, but the point is that it is used with modulators, as opposed to MEqualizer, which doesn't have any.

jmg8 · Post by **jmg8** » Sat Mar 04, 2017 6:00 pm

MeldaProduction wrote:
jmg8 wrote:How about renaming MFilter? it feels more like an EQ
Well, it actually is an EQ, but the point is that it is used with modulators, as opposed to MEqualizer, which doesn't have any.

I know but still, there could be a little confusion. As inside MXXX the FX name always match the plugin version, except this one. In MXXX filter is an actual filter that you would expect, but the plugin is quite unexpected.
MModEQ?

MeldaProduction · Post by **MeldaProduction** » Sat Mar 04, 2017 6:07 pm

Hmmm, I'd really rather keep this one. After all, if you stay on Easy screen, you won't know it's based on an EQ. And btw. filters are technically EQs (or more like the other way around

).

jmg8 · Post by **jmg8** » Sat Mar 04, 2017 6:10 pm

MeldaProduction wrote:Hmmm, I'd really rather keep this one. After all, if you stay on Easy screen, you won't know it's based on an EQ. And btw. filters are technically EQs (or more like the other way around ).

OK.
Love the renaming of the MB stuff though. My hardware controller only shows the first 10 characters of the plugin name, so the whole space is taken up by the word multiband. This will make it a lot clearer for me.

steve2KVR · Post by **steve2KVR** » Sat Mar 04, 2017 6:15 pm

...fwiw...renaming should be fine under osx...long ago I "renamed" everything Melda to "fit" the name slots...I use an abbreviation "code" I made up for quick reference...so this would be for lpx and reaper.../s~

DarkStar · Post by **DarkStar** » Sat Mar 04, 2017 6:50 pm

I think I am OK.

In Reaper, the renamed plug-in shows up as a new entry in the plug-in path list, for example as:
MPhaserMB.dll=8FCF0A1DCD86D201,825308471,MMultiBandPhaser (MeldaProduction)
In the FX browser and Mixer FX slots it is still listed as 'MMultiBandPhaser'.

By 'plug-in identifier' do you mean something like 825308471 (for MMultiBandPhaser, 32-bit)? And will the plug-in file name (and the name 'published' to the host) both change?

PS Tracktion 7 (and energy XT2, both "minor league") seems to look for the file name.

(I wish I hadn't tried that experiment as I ended up de-authorising Tracktion

)

MeldaProduction · Post by **MeldaProduction** » Sat Mar 04, 2017 7:36 pm

Got it. Btw. it's NOT just about renaming the files. The plugins also start reporting different names, which is something very different, but seems working for all hosts I tested. Tracktion & XT2 might or might not work, hard to say, but from my stats they have less than 1% of the market, so we'll just have to skip them. Anyways V11 will use a different kernel name, so people using these problematic hosts will just be able to keep V10 installed and the plugins that are not there anymore will work as V10.

Alphacodex · Post by **Alphacodex** » Sat Mar 04, 2017 7:38 pm

Shorter names are great, and if the major hosts will still load instead of the old ones them I see no reason not to do it!

Whereas in many other companies "multiband" is told us to be something really special and therefore needs to be put in the name prominently of course, multiband in Melda plugins is actually more of a standard feature such as AGC, A-H presets, styles etc.
So I'm perfectly fine with mentioning it only with a small "...MB"

Looking forward to V11

)

vectorwarrior · Post by **vectorwarrior** » Sat Mar 04, 2017 7:42 pm

If everything just 'works' then I'd love to see the name changes so that we dont have to see any more 'MLimiter confusion' threads. Also agree with MDynamicsLimiter being changed. Personally, I was never a fan of MUltraMaximiser as it seems to be just a simplified 3 band limiter, MMultibandLimiter is considerably more 'ultra' and I never use MUltraMaximiser as a result.

While I dont think MFilter should change, I agree with jmg8 that plugin names and modules in MXXX should be identical. In which case, perhaps the modules in MXXX should change name.

Glad you found a solution for this Vojtech, looking forward to V11

steve2KVR · Post by **steve2KVR** » Sat Mar 04, 2017 7:51 pm

+!1 for "plugin names and modules in MXXX should be identical.".../s~

DarkStar · Post by **DarkStar** » Sat Mar 04, 2017 7:57 pm

MeldaProduction wrote:Anyway V11 will use a different kernel name, so people using these problematic hosts will just be able to keep V10 installed and the plugins that are not there anymore will work as V10.

I've started drooling for v11

valsolim · Post by **valsolim** » Sat Mar 04, 2017 9:54 pm

MeldaProduction wrote:It turns out, interestingly, that hosts actually ARE using the plugin identifiers instead of plugin name, so it was indeed possible to change plugin names and the host successfully switched to the new plugin.

So, I was actually right...

Thank you for trying this idea!

vectorwarrior wrote:While I dont think MFilter should change, I agree with jmg8 that plugin names and modules in MXXX should be identical. In which case, perhaps the modules in MXXX should change name.

Totally agree with vectorwarrior: when the function of an MXXX module and a separate plugin is identical then their names should be identical, too.

Looking forward to V11!
--
Miloslav

valsolim · Post by **valsolim** » Sat Mar 04, 2017 10:25 pm

MeldaProduction wrote:Note that we cannot really merge plugins as I was hoping for for instance.

If the GUIDs work, I think you could even manage to merge plugins: just compile exactly the same source code for MAutoDynamicEq but generate actually two files:

MAutoDynamicEq.vst3 - with the GUID for MAutoDynamicEq, it means no change here.
MAutoDynamicEq_substitute.vst3 - with the GUID belonging to the original MDynamicEq.

This way, all occurences of MDynamicEq in the older projects would be replaced with MAutoDynamicEq_substitute.

--
Miloslav

MeldaProduction

KVR Audio

V11 changing plugin names

Ok?