Log in
Register
Home
Forums
New posts
Search forums
What's new
Featured content
New posts
New profile posts
Latest activity
News
Members
Current visitors
New profile posts
Search profile posts
Features
Log in
Register
What's new
Search
Search titles only
By:
Search titles only
By:
New posts
Search forums
Menu
Install the app
Install
Reply to thread
Home
Forums
Pro Audio
Junior Varsity
X32 Discussion
JavaScript is disabled. For a better experience, please enable JavaScript in your browser before proceeding.
You are using an out of date browser. It may not display this or other websites correctly.
You should upgrade or use an
alternative browser
.
Message
<blockquote data-quote="Per Søvik" data-source="post: 74246" data-attributes="member: 1285"><p>Re: Scene protection</p><p></p><p></p><p></p><p>I don't get the "almost opposite". While "protected" in the physical sense might imply some kind of "barrier" or "shield" protecting something, and "safe" can mean that something is just out of harm's way while not necessarily being guarded by any "protection", I can't see how they are in any way "opposite".</p><p></p><p>I do however agree that there is very little in the form of what I would call flexible protection, and I'm still struggling to get a good grip on the working method needed to utilize the scene managment in the best way (a way that keeps me from screwing up, basically).</p><p></p><p>I do understand the usefullness of read-only scenes, or write protected scenes, I get the concept of locked parameters, at least to me a locked parameter would be a parameter that couldn't be changed neither by scene change or by adjustment on the console (without a password).</p><p></p><p>If we end up with a 88 channel x 36 parameter x 100 scene tri-state matrix to manage it all, will we be able to?</p></blockquote><p></p>
[QUOTE="Per Søvik, post: 74246, member: 1285"] Re: Scene protection I don't get the "almost opposite". While "protected" in the physical sense might imply some kind of "barrier" or "shield" protecting something, and "safe" can mean that something is just out of harm's way while not necessarily being guarded by any "protection", I can't see how they are in any way "opposite". I do however agree that there is very little in the form of what I would call flexible protection, and I'm still struggling to get a good grip on the working method needed to utilize the scene managment in the best way (a way that keeps me from screwing up, basically). I do understand the usefullness of read-only scenes, or write protected scenes, I get the concept of locked parameters, at least to me a locked parameter would be a parameter that couldn't be changed neither by scene change or by adjustment on the console (without a password). If we end up with a 88 channel x 36 parameter x 100 scene tri-state matrix to manage it all, will we be able to? [/QUOTE]
Insert quotes…
Verification
Post reply
Home
Forums
Pro Audio
Junior Varsity
X32 Discussion
Top
Bottom
Sign-up
or
log in
to join the discussion today!