Live 11.3.3 visual lag & high cpu usage

[RHLN]

I'm on a MBP with a M1 Pro (10 core) processor from 2021, running Live at 64 samples of buffer. It's been working fine, but after updating I'm sometimes getting crackles and distortion when playing VST's and pulling up the CPU simulator on an empty project and pushing it to 80% produces distortion and crackling as well. This did not use to be the case, and it would be bizarre for this computer not to be able to handle Live seeing how it flies through whatever I can throw at it. This behaviour is exclusive to Live and does not occur in Logic for instance, even on 32 samples of buffer. It also does not happen in Luna, but Luna handles things a little different from a "normal" DAW from what I understand. I'm using an Apollo Twin Duo X with thunderbolt 3 connection. Has anyone else started to experience the same issues?

[chris harbin]

What would someone do to see this in action? I'm not getting anything different in CPU use with what I use with the stable or the public beta. Those are (but not limited to):

-Amp Sims, mostly Neural DSP but some Nembrini I can run many many instances with no issue. Some of these can be a little hungry on their own.
-Some hungry VI's like Arturia's "Pigments" w/o issue. Plenty of stuff with multiple instances.
-Hungry verbs like Arturia's "LX24", sometime more than one instance, no issues.
-Tons of loops (considering the new warp "feature" ) and again, nothing.

And of course, many many times running all of this together.

One thing I always do when "testing" is to load that one demo song Live comes with as well as all the pack songs, as well as my own stuff (probably more moderate compared to you peeps) and there is nothing that sets up a red flag in any way shape or form.

So I'm not sure why (see my specs below)

[Julia123]

Holy cow, I am about to buy a new computer over this. I was pretty sure it was just my iMac not handling my plugins on a couple of large projects, but yes, the screen drawing is weird and glitchy with these projects. Any difference going back to 11.2.11?

I downgraded from 11.3.3 to 11.2.11. Now everything is fine . I can make music again.

But caution:

Sets saved with 11.3.x can no longer be opened with 11.2.x.

Thanks for the warning!

[su]

Not exactly the same symptoms as the OP but similar. I'm experiencing much longer boot up with 11.3.3. I assume this is related to the analysis of audio files. I also have a couple of projects that won't open up.

[GrooveBarrio]

I have the same issue with 13.3.3. Good to know I'm not crazy and hope that a next version will have fixed it. Let us pressure Ableton to work on it!

[robdrums]

11.3.3 is excruciating. Hope Ableton update this CPU Usage issue soon.

[GrooveBarrio]

I had the same issue after I got 13.3.3. Tried to downgrade but still have the problem. Even in Live 9! (Which I kept for my tracks with soft synth ANA1).

So could it be that it has to do with wear and tear of the computer? (I can't really test properly, because my other programs are not cpu demanding)

- Jerome.

[GrooveBarrio]

I had the same issue after I got 13.3.3. Tried to downgrade but still have the problem. Even in Live 9! (Which I kept for my tracks with soft synth ANA1).
So could it be that it has to do with wear and tear of the computer? (I can't really test properly, because my other programs are not cpu demanding)

- Jerome.

[grrrz]

https://help.ableton.com/hc/en-us/artic ... ion-11-3-2

Can anyone tell how long it takes to parse the .asd files? Does it have to be done individually for each project?

I didn't have the Create Analysis File enabled, so it seems to have been done every time, resulting in an unusable GUI. I will now enable that and see how it behaves.

-the audio analysis will take as long as it needs depending of the quantity and length of audio files you have in your project. The waveform will not be drawn for an individual clip until it's done; so if you go through every clip and the waveform is drawn then it's done.

-you have to do this once for every session you created before the update; once it's done you just save and it won't do it again.

I don't even understand why there's an option for analysis files; I thought this was essential to have it to store warp information and waveform. so yeah I'd turn this on.

[grrrz]

11.3.3 is excruciating. Hope Ableton update this CPU Usage issue soon.

It would be nice if they explained clearly the .asd change of format and that it takes time to recalculate; maybe add a progress bar; so then we could know if there is an actual CPU usage issue or if all people saying they have CPU issue in fact have problems only while it recalculates the audio files. Also I wasn't aware that you could deactivate the asd so I wonder how live can even work well without them.

[Tarekith]

If you turn off ASD creation, Live will just reanalyze the files each time you load a project with them, versus always having an ASD file on your HD with that info. For some people having a ton of ASD files can be a pain if you’re trying to do things like batch process files in a folder or what not.

[Angstrom]

Has anyone explained why this change has been forced on users. This enforced rewarding of our existing material seems very unnecessary and the justification has been presented to my knowledge as "it's better when you drag a long track in to get warped". Well I pretty much never ever do that, so the single supposed plus point here is lost on me. Meanwhile I'm supposed to celebrate the mystery auto- rewarping of all my existing tracks and the regeneration of all my asd files ... why?
What exactly was it for? What is / are the benefits which requires all this pain.

And btw I'm not updating to 11.3.3 no matter what support tell me because this key point has not been addressed. WHY? And additionally... why?

[yur2die4]

I agree with Angstrom. There is no reason it should re-analyze clips with existing warp info. It should be able to convert the already existing data, but not try to re-warp them. Live can’t guess why we would’ve done some things deliberately, or maybe it doesn’t know that we already know what we are doing when we warp.

I am guessing their hope is to try to address peoples past clips where they auto-warped and they might’ve been dodgy. But it’s too late for that. They should only be thinking forward, and simply let people know that if they’re not happy with the result of an old warped clip, to the re-warping it again.

[chapelier fou]

I don’t get it. If re-warping leads to the same result, then it’s useless to re-warp.
But if the result is different, why would you do that ??
New warping algorithm should be applied only for new stuff. Period.

[ozark2001]

It certainly looks like there is a specific reason(s), we just dont know them.