hello!
Having latency issues with Ableset (Setlist View)
We are running a minimal Ableton single file project, with no audio jitter and only 3% max CPU load. All good.
We are also running a wifi network onstage. But the Ableset Setlist View display when in Chrome has latency issues - maybe as much as 200ms or more.
guitar macbook - Version 136.0.7103.93 (Official Build) (arm64)
drums macbook - Version 135.0.7049.115 (Official Build) (arm64)
bass macbook - Version 136.0.7103.93 (Official Build) (x86_64)
If we use Safari things get much sharper, timing-wise.
Any recommendations for the best browser that is super solid, reliable and quick would be much appreciated
This might not be related (let me know if I should post this separately or in another thread), but for me the “built in” browser (when clicking “Open AbleSet”) is very laggy and unresponsive.
Other browsers on the same computer (Arc, Chrome, Safari) works fine. When opening the built in one everything feels laggy, from the first loading animation, to changing views, toggling settings etc. Most things take a few seconds to respond after clicking.
I’m on an 2023 M2 MacBook Pro with 16BG of memory and running beta 7 (but I think it has been like this on previous betas aswell, I haven’t used it very actively lately)
hi All
Update here
Yesterday we managed to get everything working smoothly and are beginning to think that the sequence of turning stuff on - devices, launching Ableton, the Ableset app, which browser etc. - is at the root of this problem.
Anyone have any best practices?
If we figure it out we’ll post it here
:Lu
路)
The latency is back - 500ms and up, impossible to use live
The latency happens on 3 different macbooks - over WiFi, Ethernet (into the wifi router LAN port) or a direct usbC monitor connection
As nobody here has this problem I can only guess we have some setup issue?
fwiw - the Ableset bar-counter is bang on. It is just display latency
Anyway, why are we using wifi or ethernet? Surely, to transmit Ableset Performance, Setlist or Lyrics to each member of a band, all we need is multiple displays, no?
Both Chrome and Safari should work well, and I test the web app on both browsers. For on-stage use, I personally prefer Safari as it feels more simple and less resource-intensive compared to Chrome.
The issue with the floating window being laggy is a bit harder to debug because it’s not happening on any of my machines. Under the hood, the floating window is just a minimal Chromium window, so it should behave the same way as Chrome, but I’ve gotten multiple reports of this happening so I’ll keep looking into it.
