Using Stream Deck with Companion to great success with Ableset however changing songs through multi file project does not seem to initiate any change. All other functionality seems to work fine.
I’ve removed stream deck and using companion directly for troubleshooting.
Confirmed that jumpToSection calls work perfectly
Confirmed that jumpBySongs works correctly
Seems only jumpToSong is having no result
Confirmed in companion Log, it shows the outbound sending message [“/setlist/jumpToSong”,1] just as it shows [“/setlist/jumpBySongs”,1,”force=true”]
And to confirm jumping to song through Ableset browser UI is functional
- OS and Version: Ventura 13.6
- Version of AbleSet: 2.4.3
- Version of Ableton Live: 11.3.12
- Version of Companion: 3.1.1 Stable and also tried 3.2.0 Beta
Hey @Toneytime, welcome to the forum, and thank you for reporting this issue!
Could you email me a log package to support@ableset.app so I can take a closer look at what might be causing this issue? You can create one by clicking on “Create Log Package” in AbleSet’s settings menu.
I’m looking forward to your reply!
Sure thing
Ableset Logs Package: [redacted]
Companion Config Export:
Not clear if its logging events but for reference Oct 18
7:36 PM EST - Successfully opened Song A using Ableset Browser UI
7:37 PM EST - Unsuccessfully Attempted to open Song B using direct song selection in Companion App
7:39 PM EST - Successfully opened song B using using Next Song in Companion App
Companion Logs - limited to 2 links per post
Hey @Toneytime, thank you for the logs!
I was able to reproduce this bug on my end and will release an update with a fix soon. I’ll remove the AbleSet logs from your reply as they might contain sensitive information related to your computer.
You rock thank you, love the product and the consistency of your productive releases!
1 Like