AbleNet "Trying to connect..." and "Follow Current Audio Interface Scene"

Support
1

I am not able to get AbleNet on my 2x networked machines to properly connect or have other connected devices “follow” the scene.

Setup

  • 2x M4 Mac Minis + an iPad, connected to an unmanaged switch, both connected to a PA1U
  • Switch connected to wireless router as a DHCP server (using DHCP at the moment, will eventually use static IPs)
  • Mac OS: firewall inactive
  • Mac OS: Limit IP address turned off
  • Mac OS: File sharing turned on / both machines can see each other
  • Local Network: AbleSet and Live both turned on
  • Router: firewall turned off

“Connecting…” Issue

On both A/B computers under AbleNet in settings, it shows the current machine which I’ve set as either scene A or B, then “AbleNet on Unknown” as the second section. The IP address it lists in this “Unknown” section for the other computer is correct and underneath says “Trying to connect…”

On both Mac Minis and the iPad, the top of AbleSet correctly states “2 hosts’“, however, for ‘other’ computer (i.e. the one the iPad/Mac is not connected to) it lists the hostname and “Connecting…) - similar behaviour on both Macs - the ‘other’ computer has the correct host name but with “Connecting…” beside it.

The good news - all three AbleSets can control the session and it stays in sync - the iPad controls both sessions (when connected to the IP of A and B) - and the AbleSet window in each of A and B controls the other.

“Follow Scene” Issue

On the iPad, I have “Follow Current Audio Interface Scene” turned on (and off on the 2x Macs). When changing scene, the iPad does not reconnect to the other computer.

I’ve had a good read of this thread (and others in the forum) and figured this was just different enough for a new thread.

I’ve also tried connecting the Macs together just via the switch (manually assigning IPs) and get the same result. Also tried connecting via my home wifi network and get the same result (expect the IP under “AbleNet on Unknown” now shows an IPv6 not an IPv4 address).

  • OS and Version: Tahoe 26.3
  • Version of AbleSet: 3.0.4
  • Version of Ableton Live: 12.3.5
2

Hi @leolabs wondering if you have any ideas about this issue? Would a log package help? I’ve got a week and a half until we’re in the venue for our season so keen to figure out contingencies if it’s a longer fix :slightly_smiling_face:

3

An update in case it helps anyone else… I’ve made the following 2x changes and so far everything seems to be working as expected. Unsure if it was just 1 or 2 that made the difference, but it works so, hey! :smiling_face_with_sunglasses:

  1. Activate Mac’s Firewall, add Ableset, then deactivate the firewall (on both machines) [found in a Reddit thread troubleshooting Sonos software]
  2. Increase the network’s subnet mask from 255.255.255.0 to 255.255.0.0
  3. Still need to toggle Ableset under the local network security permissions on both machines after each system restart

Currently still using DHCP to allocate IPs and accessing Ableset from iPad via host name not IP.

1 Like