Thing is none of that matters, not a bit of it, if I can do exactly the same thing in Reaper without the CPU hit.pottering wrote: ↑Thu Mar 21, 2019 6:05 pm"Anticipative processing" is just an extra audio buffer, that adds to latency like any buffer and doesn't fit the real-time model of Ableton Live.
Rising Live's audio buffer to a huge size similar to the size of Reaper's anticipative processing's buffer size should get the performance closer.
Other causes of supposed higher CPU usage in Live are processes running that people don't realize are running real-time using CPU, like warped audio and muted plugins.
Point is, people keep talking about "inefficiency", and "good/bad programming", but they are even not comparing the same things in Live and Reaper.
All the various methods DAWs use to control CPU outside of super high over all latency involve raising the buffer on tracks that are not being used. Even Ableton at one point had a low latency setting for armed tracks. Apparently they gave up on it though.
I'm not trying to throw Ableton under the bus here, but it's obvious that certain DAWs are tentative at best code wise when it comes to setting up unarmed tracks for a slightly higher latency as a CPU saver, and Live is one. Again though, I haven't seen much of a performance cut in operations involving real time use in DAWs like Reaper. DP for most things also doesn't suffer from it. DP has an Effect Performance window that allows you to monitor this so you can watch a track switch over and notice if there's a latency, so far I haven't seen it.
I'm not going to bank on it, but I would bet at some point Live gets a rewrite, because using programs like Reaper it's obvious that the days where you need a 35% + overhead reduction to make real time performance seamless are over, or close to over.
In general though it's not a major concern of mine, but if I was in Live only, VEP would come in really handy for sure. Some Cinesamples Kontakt patches barely run on my computer.