Hi Leo! Wondering if you can help me with something.
I’m running a redundancy playback setup with:
- PlayAudio1U
- Oaktone controller
- AbleSet with AbleNet enabled
- various iPads across the stage (1 hardwired, the others connected over wireless)
Both my playback computers are hardwired to AbleNet over Ethernet.
There’s certain instances where I want to cue the next song while the current song is still rolling. However, when I do this with my Oaktone, the timeline will skip the next song, and jump to the song after it.
I can work around it using two methods:
-
disconnect the hardwire from B computer, but I lose the ability to “Sync Playback Now”
-
manually click the “Jump To Next Song” button / shortcut within the AbleSet floating window, but ideally I’d rather not touch the keyboard while a show is running.
I’m curious if this is happening within AbleSet, or if iConnectivity’s Auracle is the culprit.
Thanks in advance for your insight, Leo.
- MacOS Sequoia 15.5
- AbleSet 2.7.5
- Ableton Live 12.2.1
Hey @elvisghareik, welcome to the forum!
I’m sorry to hear about this issue! It sounds like AbleSet is receiving the skip command twice, which makes it jump to the song after the next one. AbleSet has some measures in place to detect duplicate MIDI commands, but they don’t always work depending on the setup.
Since your PlayAUDIO1U already sends the MIDI command to both computers, they don’t need to be forwarded to the other computer respectively via AbleNet. If you’re using AbleSet’s MIDI mapping feature, you can simply open the MIDI Mapping preferences and disable the “AbleNet” toggle next to the name of your Oaktone controller. This way, MIDI commands aren’t forwarded to the other computer.
I hope this helps! 
Thank you Leo! I will be giving this a shot at the show tomorrow. Appreciate your prompt response. I’ll follow up with the results asap.
Also, I am loving AbleSet. It’s a really unique solution to playback needs. Well done!
I checked my Edit MIDI Mapping settings, and AbleNet was already disabled. Not only from the Oaktone, but it’s completely disabled on all ports.
Are there any other suggestions / settings I can try?
Hey @elvisghareik, that might be a bug then. When this happens again, could you send me a log package from both computers so I can take a closer look at it? 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 can also include a video of your setup and the issue if you like, that often helps with troubleshooting.
If the files are too large to send via email, you can upload them to my support inbox instead.
I’m looking forward to your reply!
Hi @leolabs, I just sent the log package from both computers, plus a screen recording. Feel free to let me know what else I can provide to help troubleshoot this. Thanks again!
Hey @elvisghareik, thanks for the log packages and the video!
It seems that the MIDI controller is mapped twice – once in your Live project and once in AbleSet on one of your computers.
Could you try removing the mappings in one of the two places and check if that helps? If you’d like to keep the mappings in your Live project, could you try turning off the AbleNet toggle in the AbleSet Controller on your Main track on both machines and check if that helps?
I’m looking forward to your reply!
Ahhhhhh okay, I understand now.
I was using Ableton’s MIDI Mapping, not AbleSet’s. There was an instance of my Oaktone listed in AbleSet’s MIDI Mapping settings separate from my HST port on the PlayAudio1U. Even though that was disabled from AbleNet, I removed it entirely. Then I re-mapped within AbleSet to the correct HST port, instead of using Ableton’s MIDI mapping. This appears to be working correctly now!
Really appreciate your help and prompt responses Leo!