Possible issue with state morpher

EDIT: To summarize this whole post, VSTs that have modules that can be added or removed from the plugin create difficulties for the state morpher. For example, Serum FX can be added or removed. Even when updating all states to include the new FX, the morpher will not always work and in some cases, the extra parameters on the added module will not respond to changes in Mnodes. THe workaround that works well is to assign these to a local macro inside the VST and have Mnodes morpher control the macro. END EDIT

I was playing around and ran into some problems. In Serum, when adding an FX, if you want to modulate something like mix you need to right click and select automate, which then presents Mnodes with a parameter (it gives it a generic name, it would be helpful to be able to customize the name!!). Even without selecting parameter, you can save the state no problem. However, while using the state morpher it does not always act as intended. Sometimes it will not change while morphing. I even gave it a knob and it did not work. I changed the paramter value directly in Mnodes and it did not reflect in Serum (the mix knob on the FX, the permanent parameters work perfectly). I did try a new session all from blank, and did get it to work correctly. But it seems you need to do it exactly how you want right from the start. Doing changes and adding other mix knobs do not always work. I think it has to do with adding a parameter (when adding automation in a VST that needs you to specifically ask for an automation parameter, like the mix knob in a Serum FX). The parameter needs to be added before messing with the states.

I would need to go back and do a rigorous test to see exactly.

Another quick note, more to do with the complexity of vst. Using Serum as an example again. When adding a new effect, that introduces a whole new set of parameters which throws off the state morphed. Which is why I think if you start blank and add everything you need before using the states node you are okay with adding states and then state morpher.

Another thought! :grin: since morphing states can get complicated with vst like Serum and other synths you add too (Phaseplant and others), I think the best way to handle it is to assign an native macro to the parameters that are not persistent. For example, the mix knob on an fx inserted in Serum I would assign to an internal serum macro. The macro is persistent and should not cause any problems for the state morpher since it is only talking to that one parameter. I have to try it tomorrow!! Not perfect because serum only has 8 macros but definitely good enough for most uses.