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....
They link fine for me. What firmware &XiControl version are you running? Do you have wifi connection problems in general?
Oops! Sorry Josh... I just noticed you said you were in offline mode. You're right... It does the same to me in offline mode. I noticed that the adjacent fader shows as linked, but no actual fader movement linking. I'd guess you found a bug? Good luck...
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....