Hidden Plugins in Plugins

[Lotus9]

I had a couple Waves Denoiser plugins in my cart, and I was about to buy them when I decided to search and see what Melda had to offer. I found a noise reduction tutorial on YouTube that mentioned MSpectralDynamics, so I opened it up, since I already owned it, and selected the denoiser, and with essentially no changes, it perfectly removed the noise I wanted to remove.

Why do you have hidden plugins in other plugins? Every plugin company in the world has separate plugins for denoising, gating, de-essing, etc. Why don't you put each of these in their own plugin, i.e. MDynamicGate, MDynamicDesser, MDynamicDenoiser etc.?

Why should you do this? Firstly, it makes it clear that you offer plugins that are designed for each of these particular tasks. Secondly, it makes it much clearer which plugins you are using on your tracks.

For instance, right now, if I see MSpectralDynamics on a track, I know that I have a denoiser on that track. I mean a de-esser. I mean a gate. I mean a dynamic compressor. Actually, I don't know what I have until I click and open the plugin and see what option I have selected. Do you see why this is a problem and impedes your workflow?

Now imagine I have multiple MSpectralDynamics plugins on the same track. Which one is which? I might not necessarily know until I click and open each one to see which is which.

[Lotus9]

Here's another example. I've been using HorNet plugins to do auto-gain staging on all my tracks, but apparently your MLoudnessAnalyzer can do the exact same thing. Why not make an MAutoGain that can be used specifically for auto gain staging and make it so you can group the plugins together like you can with HorNet's, so that you only need to hit the auto gain button once and it will adjust the output gain on every track to match the target level? This makes gain staging very simple. Then I use the MAGC plugin after all my FX on each track so the levels never change. It's amazing.

[Frankie.T]

Because they respect their customers, and they sell capable plugins with lots of feature instead to reskin everything and call it "a new revolutionary plugin" as other companies do. So to sell 10 plugins instead of a good 1.

The secret is to spend some time to learn what you have. I know at the beginning it's kind of disorienting, but with time it's something i appreciated a lot.

Then there is internet with youtube and forums where we can search and ask for help when needed.

I think when someone spend some money should also take care about their investment and so know better their tools, this is a lesson i learned by myself, that gave me back way more than i was thinking before

As MCompleteBundle owner i also value that decision, cause there already are lots of plugins, if they would split everything, i would be flooded by too much stuff and would make a search more hard to make.

If you need to work with dynamics, just load MDynamic, then decide if you need a compressor and expander a limiter and so on. Instead of MExpander, MLimiter, MPeakSmasher, MCompressor, MBusCompressor... and so on.

MTurboComp it's a great example, instead to make and sell every analog emulations they just sell one plugin with all of them inside, and when a new model is added instead to buy another plugin, you find the new one inside that plugin, free of charge.

This is a great value and one of the reasons i felt in love with Melda

[Lotus9]

Because they respect their customers, and they sell capable plugins with lots of feature instead to reskin everything and call it "a new revolutionary plugin" as other companies do. So to sell 10 plugins instead of a good 1.

The secret is to spend some time to learn what you have. I know at the beginning it's kind of disorienting, but with time it's something i appreciated a lot.

Then there is internet with youtube and forums where we can search and ask for help when needed.

I think when someone spend some money should also take care about their investment and so know better their tools, this is a lesson i learned by myself, that gave me back way more than i was thinking before

As MCompleteBundle owner i also value that decision, cause there already are lots of plugins, if they would split everything, i would be flooded by too much stuff and would make a search more hard to make.

If you need to work with dynamics, just load MDynamic, then decide if you need a compressor and expander a limiter and so on. Instead of MExpander, MLimiter, MPeakSmasher, MCompressor, MBusCompressor... and so on.

MTurboComp it's a great example, instead to make and sell every analog emulations they just sell one plugin with all of them inside, and when a new model is added instead to buy another plugin, you find the new one inside that plugin, free of charge.

This is a great value and one of the reasons i felt in love with Melda

I think you might actually be right. But they should take it a step further and just have the MPlugin, which contains everything in one plugin, so your FX chain looks like: MPlugin, MPlugin, MPlugin etc and you don't know which plugin is which. I think it's good for sales and workflow optimization.

What's funny is that I think they actually do split up their plugins into too many versions in some cases. For instance, you have MDynamics, MDynamicsMB, and MDynamicsLarge. Put them all in one plugin, really. You are just adding clutter and making it harder for users to find what they want.

This is the exact opposite of what you need to do. You need to consolidate all of these similar plugins in one plugin and create separate plugins for the ones that are combined in plugins like MSpectralDynamics, because those are very popular distinct plugins, like de-essing, gate, denoiser etc. that normally have their own plugins.

[Held]

I think you might actually be right. But they should take it a step further and just have the MPlugin, which contains everything in one plugin, so your FX chain looks like: MPlugin, MPlugin, MPlugin etc and you don't know which plugin is which. I think it's good for sales and workflow optimization.

I guess you haven't discovered MXXX yet. It's already there for you to enjoy.

Also, it seems what you really need is to learn how to rename plugin instances in your DAW.

[Lotus9]

I think you might actually be right. But they should take it a step further and just have the MPlugin, which contains everything in one plugin, so your FX chain looks like: MPlugin, MPlugin, MPlugin etc and you don't know which plugin is which. I think it's good for sales and workflow optimization.

I guess you haven't discovered MXXX yet. It's already there for you to enjoy.

Also, it seems what you really need is to learn how to rename plugin instances in your DAW.

Renaming FX instances isn't an optimized workflow. And also, think about the other point I made in my last post about how Melda actually creates too many versions of some plugins, which adds clutter and makes it harder to search through plugins to find which one you want to use.

[Held]

I think you might actually be right. But they should take it a step further and just have the MPlugin, which contains everything in one plugin, so your FX chain looks like: MPlugin, MPlugin, MPlugin etc and you don't know which plugin is which. I think it's good for sales and workflow optimization.

I guess you haven't discovered MXXX yet. It's already there for you to enjoy.

Also, it seems what you really need is to learn how to rename plugin instances in your DAW.

Renaming FX instances isn't an optimized workflow.

It is if you save them as presets in your DAW, so you get an instance with your preferred settings and correct name.

And also, think about the other point I made in my last post about how Melda actually creates too many versions of some plugins, which adds clutter and makes it harder to search through plugins to find which one you want to use.

You hadn't edited your post yet, when I wrote my reply, but I'm not going to argue with you here. If some of the plugins got consolidated would be great. Having so many similar plugins can be a hassle.

However, your idea is going to make it even worse. Besides, there are so many ways to achieve the same things. If you have a de-esser plugin, is it supposed to be based on a dynamic eq, a single band compressor, a multi band compressor, a spectral plugin?

I like having options. That's why I use Melda plugins instead of plugins from "every plugin company in the world".

[Lotus9]

I literally have 8 different Melda EQ plugins. This is crackhead-world type stuff. You should have ONE EQ plugin. Look at Fabfilter. How many EQ plugins do they have? Having eight makes your product line confusing and cluttered. It doesn't increase your sales. It makes people not want to use your plugins because they don't want to search through eight EQ plugins to figure out which one to use. You could consolidate all of them into one plugin easily, except maybe for the Freeform EQ, but it might be possible to integrate that as well.

You should have ONE EQ plugin. ONE compressor plugin. ONE limiter plugin. ONE desser plugin. ONE denoiser plugin. That's it. And then make the GUI so that you can switch between layouts like you already have in some plugins, where you click EDIT and the GUI layout changes. That's how you fit all the features into one plugin.

Right now, you have literally combined multiple plugins into one, which should be separate plugins and you have done the opposite by making multiple versions of the same plugins.

Hire someone who knows how to market products. It's just a mess and one of the worst aspects of your plugins.

[MirkoVanHauten]

OP is right, It deviates from the usual treatment. Now we only need MDenoiser, MDenoiserMB, MSpectralDenoiser, MTurboDenoiser, MDenoiserX, MDenoiserLE, MDenoiserLP, and MAnalogDenoiser

[Held]

OP is right, It deviates from the usual treatment. Now we only need MDenoiser, MDenoiserMB, MSpectralDenoiser, MTurboDenoiser, MDenoiserX, MDenoiserLE, MDenoiserLP, and MAnalogDenoiser

And then price all the tiny plugins at $299 and sell them at a whopping 90% discount. Then we all get a great deal.

You should have ONE EQ plugin. ONE compressor plugin. ONE limiter plugin. ONE desser plugin. ONE denoiser plugin. That's it. And then make the GUI so that you can switch between layouts like you already have in some plugins, where you click EDIT and the GUI layout changes. That's how you fit all the features into one plugin.

Weren't you about to buy multiple denoiser plugins from Waves? It would be foolish to only sell one denoiser when you can sell more.

[Lotus9]

OP is right, It deviates from the usual treatment. Now we only need MDenoiser, MDenoiserMB, MSpectralDenoiser, MTurboDenoiser, MDenoiserX, MDenoiserLE, MDenoiserLP, and MAnalogDenoiser

Do you get it? Melda literally combines plugins (denoiser, desser, gate etc) into one that should be separate, and then separates plugins (MEqualizer) into many (MEqualizer, MEqualizerLP, MAutoEqualizer, MAutoEqualizerLP, MAutoDynamicEq, MDynamicEq, MTurboEQ) that should all be one. It's crazy.

[Held]

People are already using them in their projects, so it's impossible to get rid of them, even if they wanted to. Unlike some other plugin companies, Melda cares about their customers and doesn't just discontinue products.

[MirkoVanHauten]

OP is right, It deviates from the usual treatment. Now we only need MDenoiser, MDenoiserMB, MSpectralDenoiser, MTurboDenoiser, MDenoiserX, MDenoiserLE, MDenoiserLP, and MAnalogDenoiser

Do you get it? Melda literally combines plugins (denoiser, desser, gate etc) into one that should be separate, and then separates plugins (MEqualizer) into many (MEqualizer, MEqualizerLP, MAutoEqualizer, MAutoEqualizerLP, MAutoDynamicEq, MDynamicEq, MTurboEQ) that should all be one. It's crazy.

Absolutely! Though melda doing things different only to make things different is their trademark. Would have hoped their aquisition by Imageline would change something for the better.

[Lotus9]

People are already using them in their projects, so it's impossible to get rid of them, even if they wanted to. Unlike some other plugin companies, Melda cares about their customers and doesn't just discontinue products.

You just make it so the new consolidated plugins or separate plugins are compatible with the settings of the older plugins. Then, when you delete the old plugins and install the new ones, your DAW will say you are missing plugins, but then you just find those plugins and replace them with the newer, separated or consolidated plugins, and all settings will apply.

[Held]

Could you please link to the relevant parts in the VST2/3, AU, and AAX spec that describe the required functionality? I didn't know that was possible.