MSF Feature Request: Replacing Module with "equivalent" module - How to transfere Multiparameter Routings?

[] Peter:H []

I'm still working on my Recreation of the Octave Cat classic analog mono Synth of the 70ties.

Problem Description / Context:
Will doing a lot of detail optimizations I wanted to try out different filter modules and replace the current filter module by another one.

Now the setup of the Filters Frequency modulation in my synth is quite complicated, inlcuding Multiparamters.
And replacing the filter module would mean to change a lot of multiparameters routings to the new module. And this has to be done for each change, say I want to try out FastFilter, then Turbofilter...
Each and every time I need to change a lot of Multiparameters and reroute them.
This is quite tedious.

I take my "Filter problem" here only as an example. The FR is meant to work for different modules as well.

Feature-Request:
1.) In the Filter Frequency Modulation Page there's a new menu "Identify Multiparameters that route here" which shows all Multi-Parameters with Connections to the Modulator Page. This works a bit similar to the "Map" but with a focuse on the specific module / context and adds info about the Multiparameter.
Could be extended to show all Modulation Routes as well. Could be interesting to just see whats "going on" in a single module on one page.
2.) In the Filter Frequency Modulation Page there's a menu "Move Multiparameter routes to..." which allows me to select a Module where all routes now should be rerouted to. It migh show a "routing preview" which displays which old route is replaced by a new route in order to avoid misroutings to different names etc.

[MeldaProduction]

Such a feature would be very complex and to be honest I don't even know where would that start. BUT You can trick the engine probably. What I was doing recently a lot with bigger projects was renaming the modules. So if I had a compressor there I renamed it to "Comp" for example. The engine then uses these identifiers. So if you for example have a module "Equalizer 1", you map some MPs (mods etc.) to it, it would map to say

Equalizer 1 - Frequency 1

Now if you decide to go for some similar module, e.g. DynamicEq, it will be named DynamicEq 1 by default, but there's nothing stopping you from renaming it to Equalizer 1 . There would be 2 of these then, but I think it shouldn't matter, I hope . And then you just delete the first one.

Btw. the engine has heuristics which tries to map missing parameters to similar ones, so if there's just one EQ like this for example, it may work even if you don't rename it, simply because the "Frequency 1" would be the most likely candidate.

[werzel]

When I read Peter's request, I imagined a Modular plugin for the modulators where the Modulators (M1 for example) would show up in the header and the module spaces (boxes?) would be labeled with plugin/ parameter that M1 is routed to. You could then use the empty boxes to select ne/ different plugins/ parameters to add to that M1 Modulator.

As Vojtek said (only more so!) I would have no idea how to create or implement it.
The trick sounds interesting! I'm going to try it and see how difficult it is to stump the engine!

[] Peter:H []

Such a feature would be very complex and to be honest I don't even know where would that start. BUT You can trick the engine probably. What I was doing recently a lot with bigger projects was renaming the modules. So if I had a compressor there I renamed it to "Comp" for example. The engine then uses these identifiers. So if you for example have a module "Equalizer 1", you map some MPs (mods etc.) to it, it would map to say

Equalizer 1 - Frequency 1

Now if you decide to go for some similar module, e.g. DynamicEq, it will be named DynamicEq 1 by default, but there's nothing stopping you from renaming it to Equalizer 1 . There would be 2 of these then, but I think it shouldn't matter, I hope . And then you just delete the first one.

Btw. the engine has heuristics which tries to map missing parameters to similar ones, so if there's just one EQ like this for example, it may work even if you don't rename it, simply because the "Frequency 1" would be the most likely candidate.

Renaming didn't work - because "Filter" module has a Structure like
Filter
-- AMP
-- Filter
---- FrequencyMod

whereas
FilterFast
-- Global
---- FrequencyMod

The Name matching might have worked when renaming modules on top level, but actually the "matcher" looked up another filter which is structurally equal, i.e. has a "Filter" substructure not a "Global" substructure.

[MeldaProduction]

Well, in that case nothing would work I'm afraid. If you need to switch between modules, you'll have to remap manually.