Hey @TORI, welcome to the forum, and please excuse my late reply!
I’m sorry to hear that you’ve been experiencing issues with the AbleSet 3 beta. I’ve recently released a new beta that addresses the performance issues. If you’d like to try it out, you can download it here.
Regarding your questions:
By default, AbleSet tries to automatically detect and connect to other hosts on the same network, but in some setups this can be unreliable.
If your computers both have a static IP address, could you try entering the IP address of your B computer in your A computer’s “Connect to Custom IPs” setting and vice-versa and check if that helps? You can read more about this setting here.
I’m not sure if this is an AbleSet issue per se, but if you experience this again, could you send me a video so I can take a closer look at this behavior?
The sync function can sometimes lag by a few milliseconds as Live needs some time to process incoming commands. Adding the AbleSet Controller to your project file should improve this latency.
Additionally, you could try enabling Automatic Drift Correction which nudges your playback speed slightly to ensure both computers are perfectly synced.
That sounds correct. Since both computers already receive the same command via MIDI, sending it over the network via AbleNet as well can cause the command to be executed twice. AbleSet has a few measures in place that aim to counter this automatically, but disabling AbleNet is the best choice in your setup.
I hope this helps! Let me know if you have any further questions or feedback 