Re: CPU usage in Live 10
Posted: Tue Mar 12, 2019 1:32 pm
That's weird but worth noticing!
That's weird but worth noticing!
Agreed.[jur] wrote: ↑Tue Mar 12, 2019 1:32 pm
You also have to understand that virtually every user is a unique case with his/her unique computer setup/specs/uses. Even with mac computers which are somehow "standardized" it's impossible to make sure everyone will have the same experience. So it's getting even more complicated with windows machines which are so differents from user to user.
How many customers using Live 10 are active users on this forum? The forum isn't mentioned anywhere on the ableton.com main site, even in the "Community" links section. Under the Community headline, there's only "Find Ableton User Groups", "Find Certified Training" and "Become a Certified Trainer" -- this forum isn't linked anywhere and not mentioned even in the Live manual. Even if there was a sizable number of Live 10 users active here, note that in normal customer forum conditions [of any product that has customer forums available] the users who air their problems on the forums are in the minority (vs. the size of the whole group experiencing any given problem). However, in this case I would hazard a guess the percentage is even lower as the forum is treated as a "relic" of sorts, and new customers aren't encouraged to join as they aren't even informed about its existence.
I actually wrote my post after I checked that figure
This I didn't know, and kudos for bringing the forum a bit more out in the open! It's very nice that it's mentioned somewhere, and now it's at least "hidden in plain sight", so to speak
Personally, I use both of the ones I mentioned, and wouldn't give up either of them for anything
Reaper is the most CPU efficient DAW out there, and Live is in the bottom category.Nokatus wrote: ↑Fri Mar 15, 2019 2:37 amI know it's a cheap shot mentioning other DAWs and comparing to them, as not all measures are equal there, but personally I find it amazing how something like Reaper can be so much more performant than Live 10, compared head to head in similar tasks where applicable.
Agreed. These really are real-time oriented software.
Lol, I bought a Macbook Pro so I wouldn't have to freeze anymore. Looks like Apple/Ableton not a good combo right now for some users.
There are some painful realities there though. Reaper is ridiculously well coded compared to Logic, DP or Live, Bitwig. It doesn't really glitch if instantiating a plug in while the sequence is running, even a quantized launching of parts of a song can be done. Logic or DP will glitch if adding a VST sometimes, which of course Live doesn't do. Some of the CPU inefficiency of Live, Bitwig, MPC, Maschine etc. to me seems to me to be about the way they address multi core machines more than how they respond to live performance tweaking etc. Jur mentioned Logic being wonky with solo and mute, I've never had DP show any difference from Live that way, it will glitch with instantiating a plug in, and it's CPU hit is significantly larger if tracks are record armed. I haven't tested it yet, but probably in the region CPU wise of Live if you force all operations in real time instead of DP's pre rendering. Then the question becomes why is it even necessary then? I get the impression that roughly 20 years ago when Live first came out it was the best solution at the time, and at this point the rewrite isn't anywhere near worth it.Nokatus wrote: ↑Sat Mar 16, 2019 6:54 pmYep, we are definitely on the same page here. Machiensworking, I gather that you are similarly a "best of both worlds" user like me, choosing the environment you wish to work in based on the task at hand
It's just like you and jur said, the design goals and the priorities of an efficient "traditional" linear recording/mixing/production environment enable something like Reaper to use many performance enhancing strategies that don't quite work in a live oriented DAW that needs to stay responsive in all of its constituent parts. Anticipative processing of effects/plugins is one biggie.
For the record, though, as Live has matured into a DAW that is very often used in studio/production contexts (and there it doesn't need to stay responsive in every way for actual live use in mind), I think it would be a good idea to consider a separate "production mode" that the user can enable in the options, with a clearly visible sign on the GUI that you have this mode enabled etc. In that mode, the top priority would be the production side of things, where you could implement things like anticipative processing under the hood, include options for dynamically switching off processing in select unused elements without having to fear that it potentially compromises a live situation, and so on; more lenient buffering in elements that aren't specifically armed for realtime playing at any particular moment, etc etc... In this sense, Ableton Live with a separate "production mode" alongside the main "live mode" would be great. Having worked in software projects myself, I do understand the type of workload we are talking about here, as it deals with such core functionality of everything that has made Live live... Still, it's nice to dream, hehe.