V11 changing plugin names

[goldglob]

Just wondering, with name changes, would this break the way Reaper finds the plugin presets that have been saved in (Windows) AppData/ Roaming/ Reaper/ presets/ MMultibandChorus.ini (for example) ...I don't mean the presets saved within the plugin itself. I remember when changing from VST2 to VST3 I had to go through the VST2 plugins loading those 'Reaper' presets then saving them as Melda presets so that they could be loaded in VST3. I learnt the lesson...save as Melda not Reaper.
If this is an issue (?) I guess everyone needs to be told how to get around it.

[goldglob]

I can see why people like MChorusMB rather than MMultibandChorus (so do I), but what about your advertising..the longer name tells people what it actually is. How about MChorusMultiband...hmm, I dunno...I'll miss the 'Multiband'..sounds impressive....or something.

[pumafred]

I see your point, Goldglob, but Izotope Neutron, FabPro-Q, and so on, seem to manage fine with even less descriptive names, no?

[goldglob]

Sure, 'Neutron', 'FabPro-Q', short, memorable, contemporary, futuristic even..good marketing, but 'MChorusMB' doesn't seem to have that sort of impact.

[Alphacodex]

@valsolim: But what would happen to the settings then?

[MeldaProduction]

Well, I was thinking hard about the "MultiBand", it indeed sounds "big", but the problem is, it is long and doesn't even put autopan next to its multiband version for instance. The advertising and stuff will indeed be a little problematic at first, we'll need to do some changes, but it willl work. A few redirects, a few banners changed and it should hopefully be fine. It will be a gradual process.

goldglob: It entirely depends on Reaper, my guess is that it won't work. But these are rare cases and don't matter much really.

valsolim: It actually wouldn't work, because there would be 2 exact same plugins with different names, which is just wrong.

[Alphacodex]

For advertisement and marketing your could still use MWhateverMultiband, just in the plugin name use MWhateverMB, I think most people should be smart enough to grasp that they are the same thing.

Cheers,
Codex

[goldglob]

Vojtech, but MAutopan would be next to MAutopanMultiband...?
And MAutopanMultiband solves the problem of the name not being visible enough in some small fields.
Or what about just MAutopanMulti
Just thoughts..no drama here.

[DarkStar]

Just wondering, with name changes, would this break the way Reaper finds the plugin presets that have been saved in (Windows) AppData/ Roaming/ Reaper/ presets/ MMultibandChorus.ini (for example) ...
If this is an issue (?) I guess everyone needs to be told how to get around it.

Good point - just rename the reaper preset .ini files (I've often done it for JS FX).

[valsolim]

Regarding the merging of plugins...

@valsolim: But what would happen to the settings then?

Assuming that MAutoDynamicEq includes all the parameters of MDynamicEq, I think that the settings should be fine as well...

valsolim: It actually wouldn't work, because there would be 2 exact same plugins with different names, which is just wrong.

I thought that the "substitute" plugin would be needed only for a limited time - just for the transition from V10 to V11. But, of course, if you don't like this idea, I'm not going to push it any further...

--
Miloslav

[mike_the_ranger]

Just wondering, with name changes, would this break the way Reaper finds the plugin presets that have been saved in (Windows) AppData/ Roaming/ Reaper/ presets/ MMultibandChorus.ini (for example) ...
If this is an issue (?) I guess everyone needs to be told how to get around it.

Good point - just rename the reaper preset .ini files (I've often done it for JS FX).

Tbh I think this should be part of the devs problem/solution. I remember when there was some issue/renaming/whatsoever with an u-he plugin. The dev provided a tool which even converted project files so that the new plugin & presets could be loaded without any hassle. This would be appropriate here too.

[Grunwaldt]

How about old or current projects using the original names in Cubase? How would it load them? Can't believe I'm the only guy voting "no"... I'm happy with current naming

[valsolim]

How about old or current projects using the original names in Cubase? How would it load them? Can't believe I'm the only guy voting "no"... I'm happy with current naming

Please, read this thread first. Most DAWs should switch to the new names without any problems.

Best regards
--
Miloslav

[Grunwaldt]

Hi valsolim, excuse my ignorance, but i've read the thread.

And it becomes unclear about the naming. Will the DLL files for Windows change? because i think that's what Cubase uses to organize the VST's

regards,

Sergi

[valsolim]

Hi valsolim, excuse my ignorance, but i've read the thread.

And it becomes unclear about the naming. Will the DLL files for Windows change? because i think that's what Cubase uses to organize the VST's

regards,

Sergi

Yes, the DLL file names would change and the plugin names would change as well. However, Cubase uses primarily GUIDs for plugins identification, not their names. GUID (Globally Unique Identifier) is a long, internal number assigned to each plugin and this number would stay the same. Therefore, Cubase will recognize the plugins correctly. Vojtech has tested it already.
--
Miloslav