Dear Bubble! My setup: I have three computers, all with static IP addresses, all connected via a network switch. Two computers are connected to an iconnectivity PlayAudio1U and use the same Ableton file (redundantly). The third computer is connected to an RME interface and doesn’t use exactly the same file (different tracks), but of course with the exact same timestamps/locators (all copied or created from an Ableton master file, so 1:1) and the same tempos. An RTP MIDI connection runs from the PlayAudio to a MioXL. On one hand, I send program changes and CC commands to the stage, and on the other hand, I want to control Ableset with a MIDI pedal (Start, Stop, next song, Loop Out, etc.). Additionally, there is a network connection from an iPad on stage to the same network switch (from which I access Ableset via a browser or simply use the tablet as an Ableset screen on stage).
My issues: On the one hand, Ableset always “rejects” one of the three computers. It does not display the other two hosts and cannot be controlled either. Which computer is not authorized seems to depend on the order in which I start the computers or Ableset.
Also: The MIDI commands I send via the MIDI pedal sometimes reach one computer, sometimes two. Never all three. I have, of course, enabled the option to forward the learned MIDI commands to the other computers via Ablenet.
Can anyone help me solve this problem? What am I missing, what am I doing wrong—or is this setup not even possible? Thanks for your help!
Hey @Lukas_Iselin, welcome to the forum!
That’s quite a detailed setup, thank you for going over it!
Regarding one computer always getting rejected: AbleNet automatically tries to detect other instances of AbleSet on the network.
Since you already have static IPs, could you try manually telling each computer where to find the others using the “Connect to Custom IPs” field in AbleSet’s AbleNet settings?
Here’s how to set it up on each machine:
- Computer A → enter the IPs of B and C (comma-separated, e.g.
192.168.1.101, 192.168.1.102)
- Computer B → enter the IPs of A and C
- Computer C → enter the IPs of A and B
This bypasses auto-discovery entirely and makes the connections deterministic regardless of startup order.
As for the MIDI commands only reaching some computers: once AbleNet is properly connected, the MIDI forwarding should work correctly. If your pedal’s MIDI commands are reaching at least one machine, AbleNet takes care of broadcasting them to the rest — so fixing the discovery issue should resolve this as well.
One thing worth flagging: AbleNet is designed assuming all computers are running the same session. If the third computer has a different track layout, jumps and song changes might behave inconsistently on that machine. It’s something to keep in mind if you notice unexpected behavior specific to that computer.
What OS and AbleSet version are you running on each computer?
I’m looking forward to your reply!
Hi Agustin. Thank you so much for your help, and please excuse my late reply. Thanks to your tip about the static IP, that problem is solved. Perfect! However, there’s still the MIDI issue: the signal works on one computer, works perfectly on the second, but doesn’t work at all on the third. It’s the same situation even when I open the exact same Ableton file on all three computers. Do you have any advice? Thanks a lot and best regards, lukas
Hey @Lukas_Iselin,
Great to hear the static IP fix solved the discovery issue!
For the MIDI problem, the key thing to check is the AbleNet toggle in the MIDI Mapping settings.
Go to Settings → MIDI Mapping, OSC & Scripting → Edit MIDI Mapping. In the top-right corner, there’s an AbleNet toggle. This controls whether MIDI commands received on one computer get forwarded to all other AbleNet hosts.
Here’s how it should be configured:
- If your MIDI pedal’s signal reaches only one computer via RTP MIDI → the AbleNet toggle should be ON, so that computer forwards the commands to the other two.
- If your MIDI pedal’s signal reaches all three computers independently via RTP MIDI → the toggle should be OFF to avoid commands being executed twice.
Given that the signal currently works on two computers but not the third, I’d suspect the third computer isn’t receiving the RTP MIDI signal directly from the MioXL. Could you check whether that computer (the one on the RME interface) has an active RTP MIDI session with the MioXL? If it doesn’t, turning the AbleNet toggle ON on one of the computers that does receive MIDI should solve it.
Also, when you scroll down to the Redundancy & AbleNet section in Settings, you should see a settings block for each connected host below the main toggles. Could you confirm all three computers show up there?
Lastly — what OS and AbleSet version are you running on each machine?
You can also see more about MIDI control with AbleNet in the official tutorial.
I’m looking forward to your reply!
Hello! Thank you once again for the quick and helpful response—that’s truly excellent support! You’ve got it exactly right: Two of the computers receive the RTP MIDI signal directly (via Playaudio/MioXL), while the third computer is supposed to receive it via Ablenet. Unfortunately, that’s not working—I had already enabled Ablenet. Interestingly, though, I can only enable or disable Ablenet on all three computers at once (if I change the setting on one computer, it changes on all of them).
I can see all three computers listed under “Redundancy,” so far so good! 
I’m running macOS 15.4 and Ableset 3.0.7.
Thank you very much and best regards!
Hey @Lukas_Iselin,
Just to be sure: did you also set up the “Connect to Custom IPs” field in AbleSet’s AbleNet settings? Even though your computers already have static IPs, AbleSet still needs to be explicitly told where to find the other hosts. Each computer should have the IPs of the other two entered there (comma-separated).
Also, before trying again, please make sure all three computers are running the latest version of AbleSet.
If things still aren’t working after that, could you create a Log Package on the computer that’s not receiving the MIDI commands? You can do that by clicking the gear icon in AbleSet’s menu bar and selecting “Create Log Package”. Please include your .als file as well (no audio needed) and upload everything to AbleSet’s Support Inbox.
I’m looking forward to your reply!