Yes, With Diskdropouts my Clicktrack is 100% stable.
But All Audiotracks are laggin
What is everyone’s? macOS version they are using?
1 Like
Hey @kbwall, I’m sorry to hear that you’re also experiencing this issue!
I’d recommend reporting this to Ableton via their support page so they can take a look at it. I’ve already reported this issue under case #3054271 so you can mention this as a reference.
I hope that this will be solved soon!
Hi gang! I’m having issues with this as well. M2 Pro, 16 GB. I rarely have issues with a project containing 5 songs or fewer. Somewhere beyond that is when I have disk dropouts. Moving some files to RAM has helped, turning off the HiQ has also helped, but all of this is obnoxious to have to do when it didn’t use to be an issue at all—going to try zooming in after reading this thread. If I need to go to a previous version of Ableton, should I go to 12.1?
What MacOS version are you running?
What is your MacOS version?
Hey Saschpak, what MacOS version are you running?
Hey, I´m using sequoia 15.6.1. Which one are you using?
Same and i guess we all are. Just try in to figure out if its a MacOS or Ableton issue.
Everybody has reported the issue on Macs and not Windows machines?
15.6.1… basically whatever the latest update is to the Apple notification goes away lol
not a 12.2 problem. I’m experiencing everything that everyone is chatting about on this thread and I’m on Live 11.3.xxx. I am in communications with Ableton Support. Hopefully they’ll fix this debilitating issue ASAP.
This is not an Ableset problem. Im having same issue and I don’t have Ableset.
Mine seems to have occurred on two different projects (On several different computers) but both of those projects originated on ableton v11, and am now trying to play these back in ableton 12. going back to 11 doesn’t have the issue.
1 Like
Hey @padams,
Thank you for sharing your experience with this issue!
If you haven’t already, could you contact Ableton using their support page and send them the project you’re experiencing these dropouts with so they can take a look at it?
You can mention the case #3054271 as a reference.
Its been a minute! Following up out of interest to see how others are managing with this issue currently. I was able to seemingly get rid of the issue and finish my tour by downgrading to 12.1 and disabling warp for everything I could in the session (good practice in general). I found a stable version and I’m rocking with it for the foreseeable future. Have others found a fix? I must say its surprising to see others mention having this issue in v11
1 Like
Hey all, just wanted to check back in with my results since my last post…
My current working setup:
- ~85 songs in my project with 6-10 stereo tracks each
- all files consolidated into project folder (~40gb)
- arrangement zoomed into ½-1 song
- warp turned off for the majority of files
- drum rack-based click track
- 48khz, 256 samples (128 also works but I had to do 256 to account for serum 2
) - on that note, i have upwards of 20 instances of serum 2 running in a rack for all my synth patches using inst rack chains to switch, doesn’t seem to impact performance thankfully (shouts out steve duda!)
- midi changes for Quad cortex and boss gt1000, automation changes for serum patches - all working flawlessly
- live 11 worked well for multiple shows, upgraded to 12 before my show last week and had no issues at all!
Happy to answer any questions and will update if I run into anything useful/problematic!
2 Likes
I’ve been dealing with this issue for over two years now and have been in contact with Ableton Support from the very beginning. Initially, they insisted it couldn’t be caused by Live itself and suspected corrupted files or other external factors.
About a year ago, I was finally able to reproduce the bug in a fully controlled environment: completely empty project, various audio files, and an AppleScript that inserts new markers repeatedly. The issue starts to appear as soon as a certain number of markers is exceeded.
Here are my test videos:
Ableton later confirmed—over a year ago—that this is indeed a bug in their software and told me they would work on a fix.
A few additional observations:
-
It makes no difference whether Ableset is running or not; the issue occurs either way.
-
Strangely, if I insert a new marker every 0.5 seconds, everything works smoothly.
-
I just checked again: in version 12.2.6 the bug is still not resolved.
Ableton has also recently confirmed that they still don’t know when — or even if — it will be possible to fix this bug.
3 Likes
Hey @jegomat, welcome to the forum, and thank you for sharing your experience!
I’ve already asked Ableton if it would be possible to add support for jumping to arbitrary positions while Live is playing, which would allow me to remove the reliance on locators and instead work with song/section tracks.
Of course, fixing this bug would be best, but that might be a good workaround if they decide to implement it.
1 Like
Hey thanks for this answer! Would you care to elaborate on this issue? We’re running a super large session and we haven’t experienced even one issue but I’m at a crossroads.
I’d like to keep adding songs but the multi-file format is so much more convenient.
It’s kinda daunting to think about breaking our set down from where it is. Any tips for moving in this direction?
Thanks!
Des
Hey guys! Has anyone got any good news or new news?
No news from my end, unfortunately 
I’ll reach out to Ableton to check in with them.