But so useful when you know you’re in editing mode. It comes with risks, and we’ve all been there.
A lock would be a great comfort.
As long as we have a hotkey to turn the lock on/off.
1 Like
I’ve just finished implementing this. I think I like it - feels more controlled.
A couple of notes:
- Locking linked clones locks all the clones.
- You can manually Update State without unlocking if you like.
- If you switch to an unlocked state, make a change and then lock it, the change won’t be included in the locked state. Seems counter-intuitive, still considering…
- If you load an unlocked state, makes some changes and then insert a new state - the originally loaded state won’t get the changes - only the new state will capture the changes (this is as per before)
- I’m probably not going to create a default short cut key to lock/unlock but you’ll be able to set one up yourself if you like (Options | Hot Keys)
- You can multiple select or Ctrl+A select all to lock/unlock multiple states.
- If you load an old file with auto update states turned off, all states will be initialized to locked.
4 Likes
Maybe 3 needs a “changes made, save?” kind of prompt?
Maybe though not keen on a prompt. I think I’ll just make it update the state at the time it’s locked.
2 Likes
I’m going to try out the latest experimental build again. These features would be really helpful.
1 Like
In my case I’d suggest the “Locked” function automatically active for new States or let the user decide what’s the default lock-state.
Interesting idea. Logged it for consideration. Perhaps instead of an option it could just lock new states if the current state you’re saving from is locked.
1 Like
@brad
Did the hot key ever get in there for Lock State? I can’t seem to locate it.,
Just a note to say that Locked States is definitely a much more helpful option than Automatically Update was.
Hi Ade,
Just checked, yep it’s there but not in the default hot key bindings. Go to Options → Hot Keys → Add, and then:
Brad
@brad
Thanks for that! I followed your exact suggestion only to find that ctrl+alt +L does Lock only - won’t unlock 
Tried with Shift key too.
Hi @Ade,
Hrm. Works fine here for lock and unlock. What build of Cantabile are you running? Does the menu command in the State menu work for lock and unlock?
Brad
Running 3535 here, Brad
I wasn’t clear - single states are fine. It’s all on/off where unlock fails on my system.
The menu works.
Hi Ade,
Ah! The lock all and unlock all commands are separate so at the moment, you’ll need to create two hot keys - one for lock and one for unlock.
eg:
I’ll add a command to toggle all for next build.
Brad
Next build will let you do this:
2 Likes
Still trying to wrap my head around the state lock thing. What types of things are locked? What does locked really mean? I have the states locked, I have also set them to “also reset this state when loading”. Each state has a lock icon and the circular arrow. I have also put a tick mark in every singe state behavior box that is related to the plugin’s parameter. Still, as I am playing, every plugin’s parameter change (via bindings) is remembered and reloaded in this now-altered state next time I play a song using same rack state. Nothing resets or reloads unless I close the entire program, remember NOT to save changes (otherwise I completely lose numerous hours of set up work), and restart the program. This is not ideal to do between each song we perform.
I don’t understand what the state behavior check boxes really do. It does not matter if a parameter’s state behavior check box is marked or unmarked, it still saves these parameter’s value in the rack state (most do anyways, so far I’ve only come across one parameter that did not save in the state changes until I checked the box for it). Even if I can figure out the purpose of these state behavior boxes I don’t think they are related to the states self updating or not.
All I need is that every time I click on a song (which is linked to a state within a linkable rack), I need it to load that in the state that I set up, and not the state that I left it in the last time it was played in the current gig. I can understand that if I clicked on the song that I was already on that it would not reload, although this would work great for me as a way to reset to the original values, that’s at least a behavior I would expect. I’m sure someone has a use for it, but I can not find the value in clicking on a new song (one not yet played in the set) and having it not sound how you set it up and instead sound like the end of a completely different that was played maybe a half hour earlier. I don’t need to understand the value in it, but I do need to understand how to completely avoid this behavior in every single instance. I never ever ever want it to do that. I don’t care if I have to change one master setting or multiple settings per every single state in every single rack in every single song. I just need a song to sound the way I programmed it to sound when I click on said song. If I were designing a program that was to be used to save the sounds I wanted to use on a per song basis, having these sounds load exactly as I set them when I click on the song would be priorities 1 through 100. Every single other function would be secondary, by a long shot. This is why I am still trying out the program and not yet asking for a refund. I simply cannot believe that this most elementary function and obvious greatest need is not obtainable. Why it is not by default befuddles me, but I have to believe it is doable or I have lost all faith in humanity!
Hi @electricfuzz , cory
There are some things to check in options first regarding automatic song saving but if they are set already then they shouldn’t cause overwriting of your rack settings. I set mine so that I only save when I go and do it from the file menu. But you can set them to prompt to save as well if you want.
When working with link-able racks in 32XX you can achieve what you want I think by using “Entire Bank” settings and locking the rack states when finished editing. First you create the rack and open it and then load a vsti. Then make sure the ‘States’ Pane on the left is open and the ‘States Behavior’ panel is open below it. In this example I am using Air Xpand!2 as the vsti and have the check box for the “Entire Bank” selected along with a few essentials for the plugin.
Then I edit the state from the plugin GUI selecting a starting patch and tweaking it
I open the state menu and select "Update ‘xxxx’ " for the state I am in
I then lock the state by right clicking on it and choosing ‘Locked’
When done the lock will appear beside the name of the state.
At this point you can stretch the parameters of the plugin during songs but always have it return to the state when is is again selelcted. This is only one of the ways to do this but works for most plugins. Since some plugins are different in the way they apply the VST2 standard Cantabile is built to be flexible and unassuming in many ways so it can cover all the complexities of this Virtual world. That might be why it is frustrating at first, If this method doesn’t do it for you post the problems and possibly the plugin names you are using in case they are not liking this method. I use 3 methods to cover my stuff. This one usually gets the job done. We’ll see if it does it. 
Dave
4 Likes
Thank you! I will check all these things right now.
God bless you, saved the day!!
1 Like
Hopefully it is not too late to reintroduce myself as the friendly and amicable guy that I actually am instead of the slightly disturbed and cantankerous old fool I have portrayed myself as thusfar! LOL!
1 Like
No worries Cory, they have put up with my crazy curmudgeon ass for nearly 3 years now. 
1 Like