preset manager question - 1 to all

[tester]

I thought, that if there are two modules with the same preset name, then the preset manager will load the same value to both units. Unfortunately it looks that it is not so, or am I missing something?

I'm attaching small example of what I mean. In my project I have multiple units, all are the same (and all have a dozens of parameters...), and I'd like to load a "reference profile" to all of them (while the profile is saved only from one of them). Is this doable in some simple way without overloading the schematic?

[MyCo]

The Preset loading process searches for the first matching preset name, and then it thinks it is done. You should never use preset parameters with same name. That's a bad practice, and won't work in several hosts.

[tester]

Thanks for explaining. So the preset manager behavior is host-dependent in that area? I thought it has it's own routine for doing this thing.

[MyCo]

The preset names and values are passed to the host, and the host passes them back eg. on automation or load/save. If the host is confused by several preset names that are the same, it can't handle that in all of its features or the user can't handle that. eg. when you have several parameters with the same name, in FL-Studio, you couldn't use the browser to select a parameter, because you could send automation to the wrong parameter.

[tester]

Okay, thanks.

Somewhere behind my head I start to hear a tingling wired picture, on which this could be done probably by trigger order and reloading preset to units one after another and not at the same time. Something like this: rename 1st unit --> send values to 1st unit --> unrename 1st unit // rename 2nd unit --> send values to 2nd unit --> and so on.

Units are clones (the same), but it's also in exe version, plus there are some sync's between them. On the host side - I decided to make it as "Reaper dedicated", so even if other hosts are not supported correctly - I don't really care; producers should do their apps more carefully, not - we our plugins.

Btw, by using the same name =- I did not meant permanently, just a switch for loading the "special preset" (preset manager modified to handle it), and switch back to original names (so normal presets and program changes are handled in a normal, usual way).

[MyCo]

I don't know if you can change the preset name at runtime... at least the VST-Spec has no option for plugins to notify the host that it should re-read the parameter list. So don't know if FS has implemented that even if it isn't usefull.

[tester]

This one:
viewtopic.php?f=2&t=1242#p4128
works in exe, haven't tested yet in vst (thanks for reminding).

But I bet Reaper will work even with that type of phenomenon.

My guess is, that creating a specific order of loading the presets - could be used to achieve "1 to all" in similar way.