Duggle Posted April 24, 2013 Report Share Posted April 24, 2013 This applies most to synth editor NG applications. The idea is inspired by the "section locking" feature of this editor:http://ctrlr.org/access-virus-ti-snow/ Put simply it allows to "lock" a section, or group of parameters so that they retain their settings when a new sound is dumped to the editor. E.g you want to keep the effects setting of a particular patch, and hear them on a different patch. For this to work I imagine it would be necessary to optionally define a "lock_group" property to each control. Then by assigning a lock group to a toggle function pushbutton it would be possible to determine if the group of controls "hear" incoming dumps. toggle lock group(s) to lock existing settings initiate control dump edit and save, etc Perhaps have an "invert" function which reverses the toggle state of all locks. This way one could browse effects of different patches on the same patch (to continue the previous example). Quote Link to comment Share on other sites More sharing options...
TK. Posted April 24, 2013 Report Share Posted April 24, 2013 I don't really want to waste memory for definable "lock groups"... Would it help to provide a .NGR based "lock_value <id>" and "unlock_value <id>" command, which then has to be executed for each controller which should be locked/unlocked? Then you could set the lock state in different ^section s, which are triggered by a button (or multiple buttons) This gives you much more flexibility. E.g. you would be able to set different colours for the corresponding RGB LEDs. Best Regards, Thorsten. Quote Link to comment Share on other sites More sharing options...
Duggle Posted April 24, 2013 Author Report Share Posted April 24, 2013 Sounds like a great idea! I hadn't though of it being implemented in .NGR, more flexibility and no downside of memory usage, as you state. Great idea with the RGB LEDs, as well, I'd definitely use this. Quote Link to comment Share on other sites More sharing options...
TK. Posted May 24, 2013 Report Share Posted May 24, 2013 set_lock is finally available in V1.025 Best Regards, Thorsten. Quote Link to comment Share on other sites More sharing options...
Duggle Posted May 24, 2013 Author Report Share Posted May 24, 2013 set_lock is finally available in V1.025Great, is there an unlock command? Quote Link to comment Share on other sites More sharing options...
TK. Posted May 24, 2013 Report Share Posted May 24, 2013 set_lock <id> 0 Best Regards, Thorsten. Quote Link to comment Share on other sites More sharing options...
Duggle Posted May 25, 2013 Author Report Share Posted May 25, 2013 Ahh, documented in the manual already, thanks TK! :smile: Quote Link to comment Share on other sites More sharing options...
Recommended Posts
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.