Lock - Locking Controls Used By Multiparameters
- KVRian
- 1094 posts since 23 Sep, 2006
It looks like the new 'lock' functionality only works to lock controls that are changed via preset loading. However, here is another use case that would be nice to build into the lock system.
Desired use case example:
-A multiparameter controls 2 parameters (e.g. input and output gains)
-The lock is set to lock the 'input' control
-Moving the multiparameter only effects output, as input is locked
Unfortunately, locking the 'input' in the above example currently does not lock it when it's controlled by the multiparameter. So really, the 'lock' is more of a 'preset loading lock' rather than an actual 'lock'.
Desired use case example:
-A multiparameter controls 2 parameters (e.g. input and output gains)
-The lock is set to lock the 'input' control
-Moving the multiparameter only effects output, as input is locked
Unfortunately, locking the 'input' in the above example currently does not lock it when it's controlled by the multiparameter. So really, the 'lock' is more of a 'preset loading lock' rather than an actual 'lock'.
- KVRAF
- 2696 posts since 9 Jul, 2015 from UK
Not just preset lock. It locks any parameter and that parameter will not move, it is immune to randomization too. I wasn't aware that the multiparameter overrides the the lock, but thinking about it, if you don't want the "input" to move why are you assigning it to a multiparameter anyway?
Jason @ Melda Production
- KVRian
- Topic Starter
- 1094 posts since 23 Sep, 2006
Yeah and you can disable that particular parameter from the multiparameter... but my point is that it's not actually 'locking' it.
The issue is that I've built a bunch of presets that contain multiparameters that move a bunch of stuff, and using the lock functionality doesn't lock the parameter in this case.
Like you said, it's not a huge deal, just sort of inconsistent with the concept of locking a parameter.
The issue is that I've built a bunch of presets that contain multiparameters that move a bunch of stuff, and using the lock functionality doesn't lock the parameter in this case.
Like you said, it's not a huge deal, just sort of inconsistent with the concept of locking a parameter.
-
MeldaProduction MeldaProduction https://www.kvraudio.com/forum/memberlist.php?mode=viewprofile&u=176122
- KVRAF
- 14339 posts since 15 Mar, 2008 from Czech republic
But that's not really the idea here
. The idea is that you can use randomizer & presets while keeping a set of parameters intact. E.g. reverb with constant dry/wet. But at the same time you can access these parameters manually. Your idea kinda contradicts the purpose then
.
- KVRian
- 923 posts since 8 Aug, 2011
Thank you for the lock and the collapsable tree btw ! A nice addition to Melda and my workflow !
Win11, 16 Gig RAM, Intel i7 Quad 3.9, Reaper 7.16, RME Hamerfall HDSP9652, Steinberg MR816x
