Post
by Machinesworking » Mon Dec 10, 2018 9:20 pm
I don't have any real answers as to why this is happening for you guys, but in the bigger picture Live has always been a huge resource hog. Live and it's stepchild Bitwig are both heavy CPU users. I used to relate it to the warping, real time polling of pretty much everything etc. that Live does for it's usually smooth operations under task. Compare it to some other older DAWs like Logic or DP that I use and it rarely glitches when adding a soft synth etc. while the tracks are playing. That comes at a price or so it seems, since it's roughly like this, 100 plug ins in DP or Logic before the audio starts crackling become 70 plug ins in Live.
Then there's Reaper, roughly twice the amount of plug ins before cracking as Live, no glitches when adding soft instruments while the sequencer is playing etc. It's obvious by it's footprint it's super tightly coded etc. The downside is also obvious, Reaper is the anti -Live in terms of walking up to it and figuring it out, it's almost open source in terms of extensibility, and the developer obviously never was a GUI or UI person, it's not ergonomic but you can make it ergonomic.
I'm not trying to sell Reaper here, but look at what was added to Live 10, the way it works with Push 2 etc. especially the new built in graphics for Wavetable and other instruments, it's interaction with Max/MSP all that comes at a cost CPU wise. There are probably some bugs related to resource management that will fix some of your woes over time, but there's also the fact that Live 10 is going to use more CPU. The system is set up to be comfortable and quick to learn, Almost everything reacts in real time etc. I think even if you don't use Max/MSP or the embedded instruments and FX it's possible they add to the CPU hit. I know the new delay can kill my 12 core 3.4ghz Xeon in a hot second, Ableton are not making their plug ins multi core capable like U-He that's for sure.
A side note, the only DAW update that used less CPU that I can recall was DP9.51 when MOTU introduced their pre-rendering engine, and some end users had real issues with it, spiking the CPU etc.