When using a matrix to feed a very hot near 0dbfs signal out of the console via a dante output, it can be easy to accidentally bump the matrix and potentially clip the output. If we could lock faders similar to how a DCA fader is locked to 0, that would be very helpful.
This is especially helpful for me because use two identical matrix with one delayed and side chained to do “look ahead” style compression for broadcast and if the matrix faders get bumped it can mess up the effect.
Not to hijack your thread, but you can lock DCA faders to 0? How is that done?
The matrix faders can’t get bumped if they aren’t currently displayed on the surface. Therefore the easiest solution would be to have them on a layer that isn’t normally displayed until you actually want to change/use those faders.
PS - I also have never heard of “locking” DCAs.
+1!
Groups, too… there’s one I use when what I really want to do is insert an NEQ on a channel, and there’s essentially never a reason for it to not be at 0dB (or muted).
Interesting. I assume this setting prevents the fader from being moved at all, and it’s not just a “reset” to zero which then allows the DCA fader to be adjusted after that, correct?
If so, I definitely see where this could be helpful (ie I need to set some DCAs up like this in my system).
I also can understand why this would be helpful for Matrixes too.
Thanks for the information! I learn something new about these systems everyday.
Though I have not tried this out, the way the manual reads I would have thought that forcing the DCA to 0 would set the DCA to 0 and also adjust the faders to compensate. A way to get a DCA back to 0 but not lose your balances.
I’ll have to try it out and see.
+1 also for Matrix, Grp & LR also for SQ!
I use it on dlive to create additional “layers” (with dca spill) for unimportant channels (communication, …)
Tried it and, contrary to what i had thought, it does “lock” the DCA to 0. I guess the result is pretty much a mute group that you can put onto a surface strip.
Or if you are using the DCA primarily for it’s “spill” functionality, you can ensure that the DCA never gets moved off of unity. This is one scenario where I could see the lock being beneficial - preventing anyone from unintentionally changing the DCA.
