Streamdeck via Companion Pi

Hey!

I have a redundant system with 2 Mac mini M4 going in to a PlayAudio12.

I control the M4’s with 2 RaspberryPi’s connected to 2 streamdeck’s.

All one the same local network, hardwired. All good.

Sometimes when booting up, the Raspberry Pi’s don’t get the correct loop status. and I have to manually toggle loop on/off on the playback machines for the streamdecks to be in sync with each other and the playback session.

Is there someway to make sure they get the right loop status at boot up. This often happens if the session is playing a loop, while I boot up the Pi’s.

I usually press play on a midi-linecheck song, right before changeover, so that I can plug everything in on the stage, and see that all my gear gets the right commands.

Thank you in advance!

  • OS and Version: Mac mini M4. Tahoe
  • Version of AbleSet: 3.1.x
  • Version of Ableton Live: 12.x.x

Hey @Peter_Moller, welcome to the forum!

Thanks for the detailed description! To narrow this down, could you tell me a bit more about your setup?

  1. Are the Pis running Companion with the AbleSet module, or a custom integration?
  2. Which variable or feedback is your loop button using to show its state? Is it loopEnabled or isInActiveLoop?
  3. When this happens, is it only the loop status that’s out of sync, or do other buttons show the wrong state too?

I’m looking forward to your reply!

Hey! Thank you for a fast reply!

The Pis are running Companion with the Ableset module.

I’ll com back to you with an answer on what the variable is next week when I see the production again.

When it happens it is only the loop function that’s in the wrong state. and when that happens it’s not possible to push the button either.

Hey @Peter_Moller, could you try updating to the latest version of AbleSet and check if the issue persists? If it does, does that also affect the loop button in AbleSet’s own Web App?

Pi’s running companion 4.2.5

Ableset 1.7.3

Feedback is InActiveLoop. Directly from the preset menu. Action is google loop.

The only way to get the Companion in the right state, is to toggle loop off/on on one of the host’s.

Currently on your, therefore I can’t upgrade :slight_smile:

Hey @Peter_Moller, I’m assuming you meant AbleSet 2.7.3 which is a rather old version of the app. When the feedback shows the wrong state in Companion, does the AbleSet also show the wrong state or does the loop button in the web app look correct?

There have been a bunch of fixes for the Companion integration in the latest versions of AbleSet, so I’d recommend updating after the tour :slight_smile:

Pi’s running companion 4.2.5

Ableset 1.7.3 on the raspberry pi :slight_smile:

Running Ableset 3.x.x on host computers

Would it be possible for you to update to version 1.9.1 of the AbleSet Companion module? This might mean updating Companion as well, though I’m not sure if that’s the case.