Every time a patch is saved or copy/pasted, all unassigned controllers are completely reset. I can't post an example, because it would be blank by the time you pasted it. Unassigned, however, doesn't mean useless. I've had this happen to me several times when I had worked out quite a few other details for the controller, but was in the process of reassigning it, and hit save just in case something went wrong during all the assignments. It also gets rid of controllers that are currently being used, but in other ways.
For instance, if an MP is being used as an enable button for a group, it's function IS that button. It freezes the controls, which is exactly what I want it to do, so there is no need to assign it to a parameter. Unfortunately, the second the patch is saved, the MP is reset, and the enable button disappears.
MXXX: Controllers with no assigned parameterd deleted upon save or copy/paste
-
- KVRAF
- 2703 posts since 9 Jul, 2015 from UK
2 things:
You're correct about this behaviour. Just simply assign a parameter that is not being used to have the MP save.
However, I should point out to you that the enable button example you gave, is wrong. If you don't assign a parameter for the enable button it will not disable anything. Sure the easy screen will show the controls in that group getting dimmed and disabled. But behind the scenes nothing will actually be disabled. You need to assign it to a modules bypass or enable state.
You're correct about this behaviour. Just simply assign a parameter that is not being used to have the MP save.
However, I should point out to you that the enable button example you gave, is wrong. If you don't assign a parameter for the enable button it will not disable anything. Sure the easy screen will show the controls in that group getting dimmed and disabled. But behind the scenes nothing will actually be disabled. You need to assign it to a modules bypass or enable state.
Jason @ Melda Production
-
- KVRist
- Topic Starter
- 452 posts since 21 Jul, 2018
If I have the ability to be wrong about things I didn't say, then my mom was right... I am special.jmg8 wrote:2 things:
You're correct about this behaviour. Just simply assign a parameter that is not being used to have the MP save.
However, I should point out to you that the enable button example you gave, is wrong. If you don't assign a parameter for the enable button it will not disable anything. Sure the easy screen will show the controls in that group getting dimmed and disabled. But behind the scenes nothing will actually be disabled. You need to assign it to a modules bypass or enable state.
What I actually said is that it freezes the controls. I made that distinction specifically because I DON'T want to disable the underlying control structure in this case... so I would be attaching a parameter for no other purpose but to stop it from resetting upon save.
Not a big deal... just making sure I'm not missing something.
-
MeldaProduction MeldaProduction https://www.kvraudio.com/forum/memberlist.php?mode=viewprofile&u=176122 - KVRAF
- 14339 posts since 15 Mar, 2008 from Czech republic
There is unbelievable amount of stuff to store in these plugins. So there's lots of optimizations going on and as a part of that, only stuff that actually is useful is stored. If you have say a modulator that doesn't have any parameters attached, it won't be saved, because there's no reason to. If there is a parameter attached, it will be save even if it is disabled, because it is possible that you will automate/control the enabled state. Lots of complex logic in there...