I had a replacement Mac Mini M4 sorted out for me. Got everything all loaded up and Ableton is running super smooth, when on previous 2019 MacBook it didn’t.
However the floating window for AbleSet is being super laggy and sometimes not even registering my midi inputs from the controller. I believe this is a problem specific to that because when I open AbleSet in the browser on the same computer it’s super snappy (snappiest I’ve ever seen it)
I uploaded a video which has the browser window on the left and floating window on the right side by side.
Even with playback paused the floating window is laggy - you can really notice a huge difference when I trigger the Performance View change
macOS Sequoia 15.3.1
AbleSet beta 3.0.7
Ableton Live (e.g. 11.3.42)
I just released a new beta of AbleSet that uses a newer version of the underlying framework which might fix this issue. Could you try updating and check if it’s smoother now?
Unfortunately, I haven’t been able to reproduce the issue on my end yet, so I’m looking forward to your feedback!
I missed this post and have now installed the beta on my MBP(m3pro) and will test it in soundcheck today and let you all know how it went.
Onstage, all we need is 3 screens serving out Ableset “Setlist” to show us where we are (in Arrangement View). Each of us also has a MIDI controller to triggers <next.section>, <prev.section> and so we can catch up with our singer who tends to improvise.
On our last gig under Ableset version 2.7.5, the laggy latency was a massive 1 second which made it nigh impossible to play along with. Funny thing is, the beat counter at the bottom left of the Setlist screen is way more accurate. So it’s basically a display problem
Maybe we have some settings wrong?
This laggy latency happens on my MBP(m3pro) connected over wifi to our onstage wifi router, on another MBP when connected over ethernet to the router’s LAN port so the problem isn’t WiFi itself, maybe?
The Host - a 2020 intelMBP - had a better experience with a direct usbC monitor connected as a dual display. As an experiment, we tried that MBP running Ableton and Ableset solo, without WiFi on, and it all seems to work fine.
So we are now thinking of using the MBP(m3pro) as the host and hanging 3 external monitors off it so we bypass WiFi or ethernet altogether.
Will that approach work better? Any comments or ideas welcome, as we are on tour…
hi @leolabs
last night the beta worked great
we are going to be installing it on all our macbooks
2.7.5 had intermittently laggy / jittery displays, impossible to use
Thanks for the rebuild!
:Lu
I’ve only had time to test it briefly but it seems like the issue is the same for me, it works great in a browser but really slow in the floating window. Let me know if I can help provide more details or do some more thorough testing to help narrow it down.
If you notice the floating window being sluggish again, could you open the inspector by pressing ⌘+⌥+I inside of the floating window, then click the Performance tab and start a recording for a few seconds while you’re using the app?
Here’s a video of the process:
This will help me figure out if there’s any part of the code in particular that causes the UI to become sluggish.
I never tested the Intel version of AbleSet on my M1 Macs which would explain why I never managed to reproduce the issue.
I’ll try to add a warning popup that shows when the Intel version is running on an M-Series Mac with a quick way to download the correct version.
It’s interesting that there’s such a big difference in performance between the two versions though! Not sure what’s causing this yet, but I’ll continue to look into it.
I just released a new beta that warns you when you’re running the Intel version on an Apple Silicon computer and lets you download the correct version instead: AbleSet 3.0.0-beta.10
Beta downloads are now labeled as “Mac (Intel)” and “Mac (Apple Silicon)” instead of “Mac” and “Mac (ARM)” which should be more clear.
Random fact: I just figured out why the new version of Dante Controller was so sluggish on my machine. They use the same framework as AbleSet under the hood and I had also downloaded the Intel version by accident.
I reinstalled the latest beta (ARM) and now it seems to run way smoother.