FR - Better Multiparameter Defaults

[dmbaer]

For normal MPs, I suspect that almost everybody has to do what I do - change the display format from percent to use the units of first target in almost all cases. For bank MPs, it's to use the bank item name. This is true of well over 90% of all the MPs I create (probably over 98% actually).

I suspect everyone else has a similar experience. Can we get an option to apply a different default - the option we choose most of the time?

Also (and maybe on this one it's just me), I almost always need to switch bank targets to have interpolation turned off. I'd love an option that would allow the user to default this to what is most frequently used.

[ZentralmassivSound]

+1 as to default on target units.

Not so sure about interpolation. I had lots of cases where I needed interpolation between banks, I guess that is 50 / 50.

[Chandlerhimself]

Interpolation I don’t care about so much. Half the time I need to switch it and the other half I don’t. I agree with the percent thing though. I almost always have to change that to target units.

[Whywhy]

+1 for target units

[elassi]

100% pro target units.

[MeldaProduction]

I'm afraid no can do - backwards compatibility thing, sorry. (there would be a solution, but it would make the plugin states unnecessarily bigger, not worth it)

[dmbaer]

I'm afraid no can do - backwards compatibility thing

Really? I mean, I believe anything you would say about what's possible and what's not.

However, we are talking about something that happens only when creating new MPs. I cannot see how the initial default state of an MP parameter would have an effect an existing preset. Whether an MP starts out at percent and you change it to use-first or it starts out as use-first, the next time you instantiate the MP, the MP doesn't know how it began life.

So, I'm just wondering if it's possible that you simply misunderstood what it was I was proposing.

[MeldaProduction]

Nope, I understand that, but the problem here is that existing settings are stored only if not default. That's part of the optimization, if the plugins would store everything, it would take a long time whenever you'd save anything, and the settings would be gigantic, so only needed stuff is saved... And then if you change the defaults... I'm sure you get the ugly results

[dmbaer]

the problem here is that existing settings are stored only if not default. That's part of the optimization, if the plugins would store everything, it would take a long time whenever you'd save anything, and the settings would be gigantic, so only needed stuff is saved... And then if you change the defaults... I'm sure you get the ugly results

Aha ... I see. In that case, just leave the defaults as they are.

Instead, in the processing that creates a new target, if this is the first MP target, and if the MP is a normal MP (not switch, etc.) then you could introduce an automated agent that will change the display type from the default to use-first. I won't tell if you don't.

Likewise, if the MP is a bank and it's the first target assignment, have the agent change the display type to use-bank-name.

In either case, if the user doesn't like the value supplied by the automated agent, the user can change the setting back to the default. A considerable majority of the time, they will not want to do so.

[jmg8]

Just to let you know that if you learn a parameter with "Quick learn" then it will automatically be "By first parameter" for the display value.

[dmbaer]

Just to let you know that if you learn a parameter with "Quick learn" then it will automatically be "By first parameter" for the display value.

I did not know that. Thanks.

[jmg8]

Yea, it's pretty cool it also sets the current value as the default value.

[DarkStar]

Well, as "Quick Learn" does that then perhaps "Clear & Learn" and "Learn" (for an empty MP) could do that too?

[jmg8]

Well, as "Quick Learn" does that then perhaps "Clear & Learn" and "Learn" (for an empty MP) could do that too?

Good thinking.