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!