I am having a malfunction when trying to simulate a failover from the A computer to the B computer.
When I disengage Lifesine on A, my Interface will switch to B.
However, the B computer stops playing the track and there is no output. It’s as if there’s a setting somewhere that is telling the B computer not to play when Lifesine is disengaged on A.
This does not happen when I close Ableset and just run the session without it. Any idea what is happening here?
I’m not sure if this is an AbleSet-related issue, but just to make sure, could you try quitting AbleSet on both machines and then disengaging LifeSine?
If this fixes the issue and your PlayAUDIO switches to your B machine without Live pausing, could you send me a log package of both computers so I can take a closer look at what causes AbleSet to pause the B machine? You can create one by opening AbleSet’s status window, clicking the settings icon on the top right, and then selecting “Create Log Package”.
You could also try disabling AbleNet temporarily to see if that causes issues.
If it doesn’t, there might be an issue with a MIDI mapping in Live that triggers when the scene changes. In this case, you could try creating an empty session with just LifeSine on both machines and check if that works.
I just went to midi monitor and saw hundreds of sysex files flooding in… That only happens when ableset is engaged. Could this be an issue for failover to B computer?
The flood of SysEx messages is normal – AbleSet polls the PlayAUDIO’s status every 100ms. You should see the same behavior when you open Auracle for X and open the audio page for your PlayAUDIO.
Based on your log files, I see that you’ve MIDI-mapped a CC message (CC 64, value 0) from the PlayAUDIO1U’s Control port to Play/Stop in AbleSet on your B computer. Could you try removing this mapping in AbleSet’s MIDI mapping settings and check if that helps?