High CPU

Lukas Brestansky

Hi, please advise. I am using HW S4 mk3 with Traktor 4 with the latest update. Due to the complexity of the SW I use I have purchased a MacBook Air with M3, 16gb RAM and 1tb SSD. I have a USB hub to connect the S4 to the Mac. My sampling is set to 128. During 4 hours of playing music, the CPU didn't even move. Then the CPU started ramping up to max almost in time with the music :) even increasing the sampling to 1024 didn't help. After 6 hours of playing music, I loaded a track that was 1,5 hours long and Traktor including S4 completely froze. On S4 only VU worked otherwise nothing. I had rainbow death on the Mac. But the sound still worked. Through S4 I could play the loaded long track but the app was frozen. 45 minutes I watched with fear in my eyes what was going to happen, luckily the music didn't stop playing. But of course I couldn't control and load the next track. Only a restart of Trator 4 helped, then everything worked again. I had the same problem on my original Macbook Air 2017 with M1, where I had the music in external storage. I thought the external storage might be a high CPU problem. so I bought a Mac with a 1tb SSD and 16gb RAM to eliminate this problem. Unfortunately it didn't help :) I load music in Traktor from folders that I have sorted by music genres but I don't have them imported in Track Collection. Do you think importing all folders into Track Collection could solve this problem? If not, do you have any other tips and tricks for playing music more than 4 hours seamlessly through Traktor and S4 to avoid these problems? Thank you for your reply, Lukas

PK The DJ

You should certainly add all the tracks to the Traktor database where they can be analysed before playing, because if they're having to be scanned when they load, then that could potentially be causing the overhead.

PK The DJ

I can see a potential problem with trying to load a "track" that's 90 minutes long….

That's not a track, that's two or three full albums! 😮

Were the other "tracks" of a similar size, or just regular length?

Lukas Brestansky

Thank you for your reply. They were classic tracks with a length of 4 - 6 minutes. But I play these long tracks of around 90 minutes at the beginning of the event and possibly at the end of the event. Rather what I'm dealing with is that after 4 or 5 hours of standard play on only two decks, the CPU starts to show maximum load. Junk sounds are being created in the music due to the high CPU.

PK The DJ

You should certainly add all the tracks to the Traktor database where they can be analysed before playing, because if they're having to be scanned when they load, then that could potentially be causing the overhead.

Lukas Brestansky

I thought that might be the main problem. Thank you very much for your advice, I appreciate it.