Also, it only works if you delete ALL locators? What if you only kept the song start and end locator & use midi sections?
1 Like
The song’s start and end markers are not deleted. The MIDI sections still work, but I can’t jump between sections during playback. I also tested the issue in Live 11 – same result.
1 Like
thanks for sharing, hope to see this resolved soon, I’ll change our playback method using midi sections for the next few shows until this is resolved.
2 Likes
Noticing here you have each section being registered by Ableset as a song instead of a section?
I’ve nothing useful to add but I experienced this for the first time on a project the other week (not one I’d made). Hasn’t happened since - quickly changing the affected files to be RAM-loaded fixed it temporarily, but that’s not something you can feasibly do on the fly during a show.
1 Like
Yeah. Because this is one Medley with a lot of Songs in it.
Hi,
I’m experiencing exactly the same issue running Ableton 12 Live with ableset on two Mac Mini M4.
The disk warning occurs randomly and often quickly results in no audio tracks being played.
Click and alert is midi tracks. When the disk error occurs both click, and lifesine is coming through without any issues.
Sessions are set up with markers which Ableset is referring to.
I’ve tried disabling all tracks on the A computer in a specific song, and then gradually enabling the track again to see if the disc error occurs because of the numbers of tracks being played at once. After all the tracks on A, on the specific song were activated again, this solved the issue temporarily on A.
Also activating RAM on all tracks also seems to fix the issue temporarily.
Interesting thing is that the issue mostly starts on both computers simultaneously.
Has anyone had any luck troubleshooting?
1 Like
Are your files .mp3 or .wav? If it’s anything other than .wav Ableton takes up more resources processing the files.
Also hope maybe these 2 videos from Will helps
It may be something to do with M4 being so powerful its switching to its efficiency cores instead of performance? and messing with other hardware
Maybe try 64 samples buffer and see if it happens?
I’ve been trying to recreate this my side but not luck even with hundreds of locators and using live plugins for keys and running lighting and video from my macbook.
I Have an M3 Macbook Air but my rule of thumb when setting up sets is
- Make sure all your files are .wav either by source or ‘Consolidating’ them into 16bit WAV
- Collect All &Save
- Keep buffer size below 256 samples. I have mine at 64 samples.
- Avoid Warping unless you really need it
- Once you have tempo set from tracks or warping, set ‘unfollow tempo automation’
Hope some of these help!
1 Like
Did anyone found a solution? 
I’d be happy to take a look at your show file if you’d like to see if it’s happening on my M3 MacBook 
1 Like
A small point of reassurance is that this is not an AbleSet issue - happened on a recent Live set I had running and AbleSet was not open. I’m going to be making a support ticket for Ableton to see what they say.
1 Like
Sent you a direct message!
Been doing some investigating with this and from what I have seen the disk drop out happens inbetween the locators and then plays when its just eitherside of the locator. This is consitently happening. How/why disk dropout triggers is still a mystery
It appears to be Stem/audio file related since instruments like click and cues play with no problems.
Testing on Ableton 12.2
2 Likes
Glad I’m not the only one, been having this issue for the last few shows with my band. We have about 4hrs of material split up into stems (around 50GB of wavs). Same thing: MIDI (click) and OSC all works just fine, but audio samples just don’t load, stopping and retriggering the song fixes it, but it causes a severe hiccup in the show. Will try the zoom in trick at our next show, but I really hope we can get to the bottom of this.
EDIT: for reference I’m on an M3 MBP, Ableton is running to a PA1U, REAPER is running synths into my Apollo, but overall CPU usage is quite low
Hey @pupdad, welcome to the forum!
I’m sorry to hear that you’re experiencing the same issue as well. Can you pinpoint around the time you started to get these dropouts? Did you make any changes to your project file before this started happening?
I wonder if a recent update of Live introduced this kind of bug, or if it might have to do with something in the project file.
I’m looking forward to your reply!
That’s a relief to hear it’s not caused by AbleSet!
Reporting this issue to Ableton sounds like a good idea. If everyone who experiences this issue reports it to Ableton, they might have more data to work with in order to fix these dropouts
Hey guys,
I’m pretty sure the problem has nothing to do with Ableset.
I bought a completely new Mac without Ableset installed.
The same error still occurred there.
Only deleting the locator for the sections has usually solved the problem.
At the moment, I simply play my projects without section locators.
I think we’ve found a place here to exchange ideas, though.
Unfortunately, Ableton support is no help and they have no idea what can be done.
Maybe we can keep using this thread for discussion?
Or should we move everything elsewhere?
1 Like
Thank you for your insights, @Saschpak!
If this is happening with the latest version of Live on a new Mac, could you try downloading an older version of Live, e.g. Live 12.1 or Live 12.0 and check if these work better?
If you’d like me to give this a try as well, you could upload a zip archive of your project folder including all audio files to my support inbox.
That’s a good idea! Let’s keep everything related to this issue in this thread to exchange ideas, and hopefully find a solution
Hey Leo!
There haven’t been any major changes to the project, just replacing files with newer bounces. I’m still running Live 11 (I can update this post with the exact version later), so I assume it’s not update related. Furthermore as far as locators, I only have markers for song starts and ends, song sections are all MIDI clips without markers (we only need them for reference not jumping).
Will report back if any of the mentioned fixes are effective after the next show
1 Like
Thank you for elaborating on your case, @pupdad!
I’ve just submitted a ticket with Ableton’s support team and linked to this thread. Hopefully this will give them enough information to pinpoint this issue and look for a fix.