Log in
Register
Home
Forums
New posts
Search forums
What's new
New posts
New profile posts
Latest activity
News
Members
Current visitors
New profile posts
Search profile posts
Features
Log in
Register
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="brian maddox" data-source="post: 76259" data-attributes="member: 158"><p>Re: X32 Discussion</p><p></p><p></p><p></p><p>The way it works now when working online is that as you move one linked fader on the app, it moves The corresponding fader on the console. This in turn moves the adjacent fader on the console and that move is reflected back on the iPad app. When working offline, that echo back for the second channel doesn't happen so the adjacent channel doesn't move. I know you know all this, I'm just reviewing. <img src="data:image/gif;base64,R0lGODlhAQABAIAAAAAAAP///yH5BAEAAAAALAAAAAABAAEAAAIBRAA7" class="smilie smilie--sprite smilie--sprite1" alt=":)" title="Smile :)" loading="lazy" data-shortname=":)" /></p><p></p><p>Now, if the app moved both faders when the channels were linked, it would be the functional equivalent of pushing both faders at the same time on the console. Anyone who has used digital desks knows that when you do that on the desk, the faders tend to 'fight' one another. I suspect the same would happen on the iPad app as it tried to show the feedback from the second channel while it was being controlled by the app and the linked fader at the same time. I hope this makes sense.</p><p></p><p>anyway, I can see why they chose to do it the way that they did. Inconvenient when working offline. But you're usually not dealing with fader levels offline anyway. Thats my take on it....</p></blockquote><p></p>
[QUOTE="brian maddox, post: 76259, member: 158"] Re: X32 Discussion The way it works now when working online is that as you move one linked fader on the app, it moves The corresponding fader on the console. This in turn moves the adjacent fader on the console and that move is reflected back on the iPad app. When working offline, that echo back for the second channel doesn't happen so the adjacent channel doesn't move. I know you know all this, I'm just reviewing. :) Now, if the app moved both faders when the channels were linked, it would be the functional equivalent of pushing both faders at the same time on the console. Anyone who has used digital desks knows that when you do that on the desk, the faders tend to 'fight' one another. I suspect the same would happen on the iPad app as it tried to show the feedback from the second channel while it was being controlled by the app and the linked fader at the same time. I hope this makes sense. anyway, I can see why they chose to do it the way that they did. Inconvenient when working offline. But you're usually not dealing with fader levels offline anyway. Thats my take on it.... [/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!