I just save a Mix Scene with what I want to preserve.  Then I can recall whatever I want if I move things around.  That doesn't "lock" controls, but will allow me to set things back to a "known" state.
 
Paul

K so I move fader   "right-click on the fader and choose Value > Set Snap-To = Current"  move fader,  double click and returns to 0.0 level, not to where I Set Snap-To = Current?
It does display a revert to when I right click though.
 

Anderton
I don't see how you could simultaneously lock a parameter to a value and have it respond to automation.

Rather than locking to a static value I think "prevent editing" is a better description, like a "read only" mode for the track, so whatever automation is already there still happens but can't be changed

A Parameter lock would be brilliant. Mixing 80+ tracks at speed can cause all kinds of issues - many of them not that easily fixed. I have accidentally grabbed an entire mix and changed the gain... only to realise it five moves later. Or grabbing all the Low Shelfs by accident.. it happens, esp in big projects under pressure...

Anderton

chuckebaby

Anderton
I don't see how you could simultaneously lock a parameter to a value and have it respond to automation. Minimizing (not hiding) still seems simplest...if the fader isn't available, you can't mess with it.

if your referring to my post, what I meant was I hide most of the controls.

 
No, I was referring to the OP saying he didn't want to hide the track. The widget concept works too, and as you know has applications beyond what the OP wants. But I think the "as far as faders, knob, exc... don't touch them" is probably the prime directive , and if you do "save current," you can at least get back to where you started if you get toooooo far off course.

+1
 
I agree Mr. A
 
accidents do happen but as you said with a good "Save current" there is no possible way I could ever get to the point of "What did I do".
 
I wish the same could be said for when I try to bake dinner for my family.
 
 

LJB
I have accidentally grabbed an entire mix and changed the gain... only to realise it five moves later.

yes but may I submit,
how many times have you done that ?
enough to warrant a new feature ?
my theory is cake would be better of using their resources on implementing other features. 
don't get me wrong, you have a point. but I have too run in to this situation and found a quick way out of it.
sometimes leading me to a better sound because of experimentation.

Anderton
I don't see how you could simultaneously lock a parameter to a value and have it respond to automation. Minimizing (not hiding) still seems simplest...if the fader isn't available, you can't mess with it.

Craig,
  I have used Lock Track Controls in another DAW.  It works by disabling "user" changes to the track controls that could be made by mouse movements and keyboard shortcuts.  Automation continues to modify parameters, since it is the DAW that is modifying the parameters, not the user.  Automation in Read mode in any DAW essentially "locks" parameters unless the user is in override mode, since any user changes are overridden by the automation during playback.
 
Hope this helps,
-- Ron

SquireBum
Hope this helps,

 
Yes, I understand the clarification from you and others that the goal is not really to lock controls, but to lock editing of the controls.
 
For this to happen there needs to be a clear proposal presented to Cakewalk of how they would do this. I think the simplest option would be variation on what already exists, e.g., ctrl+click on the Archive button to lock out editing. Doing this would basically "disconnect" all track controls, including things like bypass the effects bin, from any editing. The Archive button could have a specific color to indicate the locked state. 
 
However, I do question how necessary this is in the grand scheme of things, per Chuck's "yes but may I submit,
how many times have you done that? enough to warrant a new feature? my theory is cake would be better of using their resources on implementing other features. don't get me wrong, you have a point. but I have too run in to this situation and found a quick way out of it. sometimes leading me to a better sound because of experimentation." 
 
I still don't see why not simply minimize the track? In Track view, it's just one click to disable editing, in the sense that you can't access the controls. I can't think of any workflow that's easier than one click. Where this doesn't work is Console View, which would need a dedicated control. So if the majority of the people want this feature for Console View, then it makes sense. But again, there's still the question of which is more important: being able to lock editing, or being able to get back to a known state. The former doesn't allow for experimentation, the latter does and can be done with Mix Recall or recall current.
 
 
 

To: "LJB",  Somewhat comforting to know I'm not the only one who's experienced moving some parameter, and noticed perhaps only after many undo levels, mix scene and/or project saves have been done.
Ideally if one could selectively undo something in undo history, without affecting anything in else after would also be a great feature. (albeit parameter/level changes aren't logged in undo history). Perhaps if moved only once parameter right click, "value" "revert" may show last level change at least.
 
cheers

I was looking in X3 for such a feature. In console, if you right-click the volume in a MIDI track, there is an option to Lock Control. No such option in audio tracks.
But Lock Control doesn't seem to do anything; as soon as you move the slider, it moves.
Unless I'm misunderstanding what Control is in this case.

Thanks Craig, while I hadn't intended this to go this far, and thought there may be simple way to lock track controls I wasn't aware of, obviously there are many ways to adapt to an environment, foremost being be careful, "and don't text while mixing" (and probably shouldn't drink and smoke, excessively at least, LOL) 
That said, it would be more so in the console view that this may happen, say when scrolling console view, but mouse was over a parameter you hadn't noticed, mix scene is great when intentionally changing mixes around.