Re: Major Problems With Live 11
Posted: Thu Mar 11, 2021 5:07 pm
Nothing wrong with the CPU meter, you just need to know what it's doing, and the changes in the L11 one.
that’s fair, but it doesn’t really explain why 4 tracks with a couple of effects on each might take ~35% of CPU to calculate a sample in Ableton, yet adding another 10 tracks, each with a similar number/type of effects may only add another 5% to that load.[jur] wrote: ↑Thu Mar 11, 2021 5:07 pmNothing wrong with the CPU meter, you just need to know what it's doing, and the changes in the L11 one.
It does, actuallyslow.robot wrote: ↑Thu Mar 11, 2021 8:54 pmthat’s fair, but it doesn’t really explain why 4 tracks with a couple of effects on each might take ~35% of CPU to calculate a sample in Ableton, yet adding another 10 tracks, each with a similar number/type of effects may only add another 5% to that load.[jur] wrote: ↑Thu Mar 11, 2021 5:07 pmNothing wrong with the CPU meter, you just need to know what it's doing, and the changes in the L11 one.
Thanks Mark. Will give it a look. Appreciate you.Mark Williams wrote: ↑Wed Mar 10, 2021 9:15 pmTry Xhun Audio Little One, its fab, and a hidden treasure.
https://www.xhun-audio.com/site/xhun.php?page=littleone
Agreed. I have lost weeks of production time trying to make Live 11 usable. I have had to teach myself under the good tech intricacies, invested in a desktop because my expensive laptop wasn't powerful enough & had very little explanation for this from Ableton. If it was a free product like Vital, fair enough. But with the high price, there needs to be support. Mat Zo even said on twitter that Ableton's code is awful causing these issues. I had issues with Serum (it was probably Ableton) but what I like is that Steve Duda replies quick. Why? Because he gives a shit about a product he created & wants it to enable you as a producer.papawise wrote: ↑Wed Mar 10, 2021 10:41 pmguys, excuse me but I wouldn't like to hijack this thread because it's something that should be fixed ASAP!
Ableton isn't giving any reasons nor updating info/schedule for people paying a fortune for the new version isn't getting real answers about the OVERLOAD UNUSABLE WEIRD STUFF going on!
Let's move this thread and make it serious for them to pay attention.
I'm upgrading to a similar config to you so finger crossed this works out better than current (recommend by producers). I have read a lot of pros like Mat Zo say how badly Ableton is coded which could explain the incompatibility with very popular VSTs & frequent crashes. I also encounter the 'Places' loading thing. Weird & inexplicable.slow.robot wrote: ↑Thu Mar 11, 2021 2:54 pmas someone new to Live, I have found it weird that it says I’m using so much processing power, HOWEVER, I’ve had almost no issues actually running anything (i7, 32 GB RAM from a few years ago). I transferred an all-audio project from Reason, with ~22 tracks and a bunch of effects on most, automation, yadda yadda, and it still plays back fine with the buffer at 128.
the weird thing for me is that the CPU load indicator seems to jump up to 20, 30, even 40% with only a couple of tracks and some processing—but even with the project above, I haven’t yet gotten it past the 50% mark. it ramps up quickly, but at a certain point, adding new instruments and effects stops hitting the CPU as hard (or at least that’s what Ableton is telling me). I notice that sometimes the CPU and/or disk overload indicators have gone off, yet I haven’t experienced any actual dropouts. I wonder if there might be something wrong with the load indicators.
the one performance-related thing that concerns me (and has me scratching my head) is that “Places” thing where it just looks like it’s constantly trying to find stuff. sometimes it goes away, and I think it’s all good, but then later I look, and it’s there again.
interesting—good to know. still not very intuitive, but good to know.[jur] wrote: ↑Thu Mar 11, 2021 10:57 pmIt does, actuallyslow.robot wrote: ↑Thu Mar 11, 2021 8:54 pmthat’s fair, but it doesn’t really explain why 4 tracks with a couple of effects on each might take ~35% of CPU to calculate a sample in Ableton, yet adding another 10 tracks, each with a similar number/type of effects may only add another 5% to that load.[jur] wrote: ↑Thu Mar 11, 2021 5:07 pmNothing wrong with the CPU meter, you just need to know what it's doing, and the changes in the L11 one.![]()
hint: 1 track = 1 CPU core
so...![]()
slow.robot wrote: ↑Sat Mar 13, 2021 1:30 pminteresting—good to know. still not very intuitive, but good to know.[jur] wrote: ↑Thu Mar 11, 2021 10:57 pmIt does, actuallyslow.robot wrote: ↑Thu Mar 11, 2021 8:54 pm
that’s fair, but it doesn’t really explain why 4 tracks with a couple of effects on each might take ~35% of CPU to calculate a sample in Ableton, yet adding another 10 tracks, each with a similar number/type of effects may only add another 5% to that load.![]()
hint: 1 track = 1 CPU core
so...![]()
hint (for anyone involved in writing Ableton’s manuals): if hints are needed to explain something that’s in the documentation, then the documentation could be more clear.![]()
![]()
This is fixed for me after doing Waves v12 updates (I also reinstalled Ableton exe and Reason Suite but Im thinking the waves update did it. I dont even use the v12 plugins its a couple of freebies).Andrew Hill wrote: ↑Sat Mar 13, 2021 11:48 amThere's an issue with Live 11 reading the VST3 system folder.
I keep doing alt scan (win10) and it either misses the Reason Rack Plugin or the Waves H comp compressor. Have tried deleting the preferences file and the plugin txt, but it will only read one or the other after a fresh scan.
Think this is why the first track I made in Live 11 would lead to a crash and would not load and ive ended up deleting it. Aside from this Ive had no problems but I use the RRP a lot so this is an issue for me.
Want to avoid reinstalling Waves but considering re-installing Ableton then Reason, not sure what else to do
Sure, that's different things, but it's still worth mentioning the updated metering.