Ableton 10 - Sound stops, tracks keep running (and appear to be sending audio)

[Reinout78]

Hi,

I've put together a Live set to perform a 60 min. gig. The set is composed of 4 stereo channels playing prerecorded stems, a track sending TimeCode and a bunch of midi tracks containing V-Synths for me to perform live with. It's a pretty heavy set, but my CPU-load meter never exceeds 25%. Everything runs extremely smoothly, with a buffer size set to 64 samples. But during our first rehearsal yesterday the sound cut out twice, in two different songs. And only those 2 times, because we rehearsed all the songs several times and it only happened twice. And what happens is: all the sound cuts out, but my tracks keep playing: I see the playhead moving on and the tracks are sending audio. But it appears Ableton just stops sending them to the appropriate channels on the MOTU 1248. So when I restart Ableton, all is back to normal and all plays as before. We have our first gig with this set-up in 3 weeks, and I really can't risk having to restart Ableton during the show. So any tips or pointers would be much appreciated.

Thanks!

My Setup:
MacBook Pro (15-inch, 2018)
2,9 GHz Intel Core i9
32 GB 2400 MHz DDR4
Intel UHD Graphics 630 1536 MB
2TB internal flash drive
Ableton 10
2 x midi in via M-Audio Midisport 2x2
MOTU 1248 (sending 5 Stereo Channels + 2 Mono to MOTU 16A)

[fishmonkey]

is your audio interface indicating that it is receiving audio when this happens?

your Console logs may have some clues, check the logs using the timestamps (you could also search for "audio" in the Console.

my guess would be an audio interface or audio interface driver issue. are you running the latest MOTU driver? i suggest contacting MOTU tech support as well.

[Reinout78]

Yes, strangely enough the MOTU was receiving audio, but on different channels... But thanks voor the tips, I'll check the logs and also contact MOTU tech support.

[Reinout78]

I think I might know what the problem is. The issue might be related to the Apple T2 chip on the 2018 Mac Book Pro's. According to this link: https://appleinsider.com/articles/19/02 ... onnections the problem occurs whenever the T2 tries to sync time and location. Toggling off "set date and time automatically" in System Preferences will reduce incidents, as will disabling location sync in the Time Zone tab, but neither setting will fix the glitch completely...
I will test this out, but it's not very reassuring information...

[fishmonkey]

I think I might know what the problem is. The issue might be related to the Apple T2 chip on the 2018 Mac Book Pro's. According to this link: https://appleinsider.com/articles/19/02 ... onnections the problem occurs whenever the T2 tries to sync time and location. Toggling off "set date and time automatically" in System Preferences will reduce incidents, as will disabling location sync in the Time Zone tab, but neither setting will fix the glitch completely...
I will test this out, but it's not very reassuring information...

i think that issue was addressed in the macOS 10.14.4 update. what version of macOS are you running?