FR: MPowersynth [poll] more multiparameters or a better way to automate the effects section

[pone]

I've followed what Vojtech has said about MYYY. And I don't think that "mostly like mxxx" and "spectral synth" and "wavetables in myyy" etc is concrete enough information...
But I think all of this is strolling off topic. ;p

[dmbaer]

I voted to leave things alone - but not because MPS is complicated enough already. I just don't think there's a huge need for more MPs in MPS. This was *not* the case for MXXX, which really needed more. But a single patch for MPS should not need all that many parameters to tweak (we've already got quite a few, right?). Compare that to MXXX, where a patch/preset could actually be a complex effect in its own right and often will need lots of parameters for the user to dial in desired behavior.

I would rather see Vojtech devote his energies elsewhere.

[vectorwarrior]

I would rather see Vojtech devote his energies elsewhere.

Agreed, every time a FR comes in it detracts time away from other things. I'd rather have the other things

[jmg8]

I would rather see Vojtech devote his energies elsewhere.

Agreed, every time a FR comes in it detracts time away from other things. I'd rather have the other things

Apart from my ideas.

[Gone soft]

I want to keep the automation I've done so voted against changes that would break my projects. Also I like to have parameters show up with meaningful names without needing to do anything to bind a parameter to a Mp ultimately showing up with a meaningless name in my DAW.

[pone]

I want to keep the automation I've done so voted against changes that would break my projects. Also I like to have parameters show up with meaningful names without needing to do anything to bind a parameter to a Mp ultimately showing up with a meaningless name in my DAW.

Just so we're clear, only if you've automated the sub parameters of a multiparameter (like range) and mxxx changes would be implemented then would your projects break.
At the moment a multiparameter's sub parameters do not have a meaningful names and multiparameter names are always 1..8.

[jmg8]

He is talking about normal parameters like filter 1 cutoff for example. These show up with meaningful names at the moment. But if lots of MPs were to be added like in MXXX it would break these automations and the user would have to assign filter 1 cutoff to a MP and then automate that instead. But even then, the daw will still show it with meaningless name.

[pone]

I guess not a lot of people have time to read the post first, hehe

[jmg8]

I don't understand, do you mean you?
To me it looked like he had read the post properly, as what was written made perfect sense.

[pone]

"something similar to the MXXX changes of 9.21 could be done.
Instead of having things like automation of sub parameters of the multiparameter, e.g. the range of the first few targets of the multiparameter, why not simply have more multiparameters?
In the event of wanting to automate that range, you can still just bind a free multiparameter to that sub parameter."

I think that makes it clear that the non-multiparameter automation is not affected.

[jmg8]

Non multiparameter automation WILL be affected. That's what happened in MXXX. ONLY MPs will be automatable after the change.

[pone]

I would think that "something similar" means "not the same but very related". And if I follow up with what would get changed, it would indicate what would be changed and nothing else major. If there is a misunderstanding, I'm sorry, English is my 3rd language.

[ZentralmassivSound]

Why not. A toolbar like in MXXX, but horizontally, to access more multiparams would be useful. However I agree that this is not a top priority feature requests.

[pone]

I've edited the poll, now it should be clearer I think.

[jmg8]

Both option 3 and 4 in your poll read on the last line "non multiparameter automation will not be affected"
I think this is where the misunderstanding is coming from.
You see a DAW has a maximum number of automatable parameters for a plugin. So MPowerSynth already has this at maximum. If more multiparameters were to be added, even just 1. It would mean removing one of the existing automatable parameters. This could break someone's project.