FR: default preset for modules in MXXX/MSF

[Tagirijus]

Hey there!

Background:
On the discord there came up an interesting idea, which I also had from time to time: normally you can set up defaults for plugins in the DAW, whith which you can load a new plugin into the DAW and basically have your very own "Default preset" loaded.

Problem:
Unfortunately this won't be possible for container plugins like MXXX or MSF.

Solution:
So the idea was in the chat to have maybe some mechanism that a plugin / a module can understand to load a preset (maybe in the root folder?) named "Default" as a default preset. That way even modules could have a user set Default state.


I'd personally won't call this an "urgent thing", but still think that the idea is nice. What do you people think at all?

[vectorwarrior]

I've asked for this in the past too. Vojtech's response has been 'create a default preset for the module and just load that'. Personally, I like everything just being at the default settings when I create a module, which is what it already does, so I'm fine with it now.

[noizejoy]

I think there's a conceptual and practical difference between default settings for individual multi-parameters and a default for an entire module or instrument.

The big difference maker for me is distributing things (compared to just using them for myself):

For example, when distributing an MSF (MSoundFactory) instrument, the default preset for the entire instrument should be a really great sounding preset, so the first time user isn't immediately disappointed by a bland and un-inspirational sound. Grandmothers and marketing professionals will tell you, that first impressions matter - a lot.

This preset may have somewhat extreme individual MultiParameter settings, that only work together with specific other MultiParameter settings. A simple example is when a filter cuts out most of the frequency spectrum, and a volume or gain needs to be dialed up rather extremely to bring the overall output to a reasonable volume. -- I generally would not want to make an extreme gain or volume setting the individual default for a multi-parameter.

[Tagirijus]

I think there's a conceptual and practical difference between default settings for individual multi-parameters and a default for an entire module or instrument.

I think you might not get the point here (maybe)? It's not about a default setting for multiparameter. It's about a) an entire plugin (in case the DAW does not allow a default preset) or b) a module you load up int any matrix of MXXX or MSF, for example.

For example, when distributing an MSF (MSoundFactory) instrument, the default preset for the entire instrument should be a really great sounding preset

I am not sure, why you mentioned this, but just in case: you know that you can already make a default preset for an MSF device, by setting up the default values in the respective MP accordingly?

This preset may have somewhat extreme individual MultiParameter settings, that only work together with specific other MultiParameter settings. A simple example is when a filter cuts out most of the frequency spectrum, and a volume or gain needs to be dialed up rather extremely to bring the overall output to a reasonable volume. -- I generally would not want to make an extreme gain or volume setting the individual default for a multi-parameter.

Still I am kind of lost why you mention this at all, since I am totally not sure how this is connected to a thinkable feature to be able to set up individual defaults for e.g. modules in MXXX/MSF.

[noizejoy]

Sorry, I didn't realize you had intended your original request/survey to be scoped tightly just to modules, rather than generally around default presets wherever they are used in the Melda ecosystem (also since there's so much common code in the Melda architecture).

So I elaborated, why I'd like to have an MSF instrument default preset load automatically when an instrument gets loaded.

[Tagirijus]

Sorry, I didn't realize you had intended your original request/survey to be scoped tightly just to modules, rather than generally around default presets wherever they are used in the Melda ecosystem (also since there's so much common code in the Melda architecture).

It's intended to modules and plugins, sinc - at least I guess - it could be a similar thing during plugin initialisation ... I guess. I understood your post to be about multiparameters. That's why I tried to clarify it a bit more.

So I elaborated, why I'd like to have an MSF instrument default preset load automatically when an instrument gets loaded.

I cannot quite follow maybe ...? MSF devices do have default presets. If you create a MSF device you set up the default preset with the multiparameters default values (basically).

On the other hand: would be interesting to have a default-mechanic for MSF devices as well, like my described idea is about plugins and modules. In case users would like to have different default presets for specific MSF devices, while not being forced to dig into the MSF device editing. Maybe that's what you meant as well?


Either way: I am talking about the option to have some preset called "default" or so in the preset managers root and when loading any Melda "thing" it could look into this and load this as the default preset or so. (-;

[MeldaProduction]

Sorry, won't happen. It would significantly slow down loading of just about everything.

[Tagirijus]

Oh I see. Thanks for the feedback. Speed is more important than such a feature, at least to me, hehe.

[Tyrs]

In case you use Reaper it's not an issue. You can save any track with any possible setting and import it anytime in any project by a click from a dropdown menu as if you would start an VSTi.

[Tagirijus]

This is no option for module loading inside any modular plugin of Melda.

[Tyrs]

Yes, true

[Hexspa]

Not sure whether I'm following this thread correctly. Assuming it wouldn't slow things, I'd like to have a way to set my own default values for any given MXXX device. The initialized settings I like to use are different than the Melda defaults.

Thanks.