I’m seeing CPU spikes on the Ableton Meter at SONG END and at the jump to next song. These spikes are topping 500%. I only noticed as I was setting up a live guitar rig in my set and played a continuous chord through the end of a song and noticed a couple of light pops. I then switched to a copy of the same set that didn’t have the guitar plugin and saw the same spike. It doesn’t spike when the song automatically moves into the next song without stopping (well it does, but only to about 80% or so). Normally operates at around 18% CPU on the Ableton meter. Is this a known issue? There are 660 tracks in this set, about 60 songs.
Please fill out these values to make it easier to troubleshoot:
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.
Looks like it’s on Live’s side. It happens if I move the playhead anywhere with my mouse. Which is baffling. All of the tracks are audio tracks, and the only plug-in or device I have in the set is Ableset. Well, I guess that’s not entirely true. I’m using the pro template from Will Dogget’s From Studio to Stage site. So have have “Foundations for Live” on the click track. And the AI Cue Player for cues on the +GUIDE and +LOOPGUIDE tracks…
Hey @VocalAdrenaline, sometimes these CPU spikes can be caused by warped audio clips. Can you check if any clips in your timeline are warped and if so, try disabling warping?
If that doesn’t help, please feel free to send me a log package so I can take a closer look at the project file and check if I can reproduce the issue on my machine.
I think I figured it out. There is some warping, but only to ensure the tracks follow the tempo tracks. It’s a really big set, and I had the buffer set at 64 samples, which was fine for the most part because I didn’t have any audio playing over the locators. I only noticed when I tried to add my live guitar over it. I bumped it up to 256 and the spike only hits 80% or so. I’ll run with that for now unless it’s a problem. Then I’ll just have to break up the set into a couple of different sets.