With the wonderful support within AbleSet of PlayADUIO 1U and DirectOut Exbox.MD redundant interfaces - and the ability to switch which ‘scene’ (or playback computer) is active from within AbleSet, there is a little problem that has come along with that. AbleNet allows some degree of Redundant switching of remote tablet displays between the two Playback computers, but only if the entire A computer (or at least the Ableset app or Ableton app) crashes. Especially with the Exbox.MD interface that uses proper running pilot tone played back off a track, It is quite possible for the Interface to change over due to a playback drop-out, but not in a way that AbleNet detects as a ‘crash’. In that case, the instance of Ableton that remote device web browsers are linking to will not be the one that the Interface ‘Scene’ is playing audio from. Likewise if you manually switch scenes in the Interface control panel in AbleSet. Many reasons you might do this - maybe so you can keep rehearsing on the ‘B’ computer while editing on the ‘A’ computer. You want the remote displays on stage to follow the active computer that’s feeding FOH and Monitors - not show everyone on stage where you are editing another song. It would be great if there were an option where AbleNet could force a web browser re-connection to follow the active Interface Scene as shown by the green or red indicator circle (whatever has caused it to change over).
Hey @njrsound,
That’s a great idea and makes perfect sense!
For this to work, you’d have to define which computer is connected to scene A and which is connected to scene B. I’ll check if this can be done automatically based on the port of the audio interface each computer is connected to. Alternatively, this could also be a setting on AbleSet’s settings page for each computer.
I’ve added this to my todo list