Hey @VocalAdrenaline,
Thanks for the detailed report, that helps a lot.
First, you’re on 3.0.7, so I’d recommend updating to the latest official release, 3.1.6, which came out today: AbleSet 3.1.6. Please check if the spikes still happen there.
If they do, it would be great to figure out whether this comes from AbleSet or from Live itself. Since the spike mostly shows up when playback stops at SONG END (and is much smaller when the song flows straight into the next one), my hunch is that it’s related to how Live handles stopping the transport and relocating the playhead in such a large set (660 tracks is a lot of devices and clips to reset at once).
To test this, could you try the following?
- Quit AbleSet completely (not just the web app, the app itself from the icon tray).
- In Live, play through the end of a song and stop the transport manually at roughly the same spot.
- Then click on the next song’s locator to move the playhead there.
- Keep an eye on the CPU meter during steps 2 and 3.
If you see the same spike without AbleSet running, we’ll know it’s on Live’s side. If it only happens with AbleSet, please let me know and we’ll dig further.
I’m looking forward to your reply!