Traktor 3.9 is -almost- "crashing" (no sound, blurry waveforms)

SpirosG · 2023-08-17T13:28:14+00:00

There was an error rendering this rich post.

So, I have faced this bug three times the last two months already.

During my sets, somewhere in the middle, the music stops, the waveform becomes blurry, the app remains functional, but for some reason, Traktor is not able to read any track from my collection. Although I can load tracks on the decks, their waveform is blurry and of course there is no sound. And this is happening with all of my (3) Music Drives, Traktor is not able to read any track from any drive.

I'm trying to reproduce the issue using the same track, but it's impossible. It seems completely random. I also tried to check the tracks for errors using mp3diags and mp3test, but there is no problem with the tracks according to these apps.

Find more posts tagged with

Comments

Kubrak

If you think, the problem is in 3.9 version... What about rolling back to earlier version? Doing that, you could verify, that the problems relate to 3.9.

Your problems may be caused by many reasons. Generally it is not advisable to connect audiointerface using the USB hub.

Also, you do not write, what external discs you use. But generally, they may go to sleep mode after some time, if not used. And because of some reason, they do not wake up, when needed.

Do you have Mac or Win? And if Win what CPU and GPU? TP 3.9 exhibits problems on systems that have AMD GPU. But different problems to what you describe.

Also, why do you use several external disc at the same time?

It is difficult to find the source of problems, if they show up only here and there and after long time...

I would make the setup as simple as possible, just one external disc, no USB hub (if possible), and used the same USB socket for for each device. And write down exact setup that made problem.

Later change just one element, like try different USB socket for the disc, and use it on in this configuration. And so on.

Your problem is not widespread as it would be reported by numerous users.... So, it is caused by something in your setup. Hard to say what...

DJDL

My latest crash was yesterday at an important event. I am sad to say that Traktor is crashing in about 1/3 (or more) of events I use it in. I opened the ticket with NI and even though they were kind and eager to help, nothing was solved. That ticket has now been closed, issue still remains. Last night's crash was while previewing a track, 20 mins into the gig. Ironically, the decks froze, music stopped, and I was seemingly able to quit the program until it further stuck at the Flushing Background Tasks step. That dreaded ghost from days past. Gladly it is no longer but a faint shadow of itself, as it has not happened in a long time. I attribute yesterdays appearance to being circumstantial in light of the greater issue. The previous crash happened while deleting a playlist during the gig just before last night's event.

I am sad to say that because of the state the program is in (3.9), at least for my particular setup (Mac M1, Monterey, S4MK), it is not fit or dependable for professional use. A roughly 30% or more estimate of application failure during a live performance is unacceptable. 3.8 was pretty stable in spite of some sound quirks, and variables have remained the same in my setup except for updating to 3.9. I have unsuccessfully tried to work out any culprits other than the application itself. I have done massive library organization and optimization in 3.9., (a few months worth of prep work), so rolling back is not an option.

Traktor is by far my preferred platform for djing, has been for many many years, and I am far from considering leaving it. But as of now, I have no choice but to resort to other ecosystems for important gigs until a new stable version of Traktor is released. Im aware that 3.10 is out, but there are reports all over claiming that this issue is still not addressed, plus release notes do not mention fixes. Is there a remote possibility that the simple act of updating to 3.10 might help? Just might try that, as things cannot be worse than they are now.

This rant is in no way intended for any reason other than putting a bit of pressure on the team to make stability a priority for next release.

Cheers!

Gully B

after having this happen almost every gig on TP4 on a MacBook Pro M3, I’ve come up with a plan B emergency plan to help.
it is in NO WAY a solution to the problem though!

I save an offline playlist that’s relevant to the gig ahead of time on Spotify, then route my MacBook audio to the S4MK3 - when I see the initial signs before the crash where the tracks won’t load into the deck or the waveform goes blurry etc, then I know I have <10 seconds before the music will cut out.

In that 10 seconds I fade out the song playing and start a song on Spotify. Then you have to Force quit Traktor because if you quit normally it gets stuck at flushing background tasks.
reboot Traktor and usually I don’t run into any other problems for the rest of the gig.

Weirdly enough, the crash usually happens in the first 30 mins of a set (I usually play 6 hours). Once rebooting after a crash, I haven’t had any issues for the further 5 and a half hours.

ChrisMadem

I met the same problem in April when I bought a new m2 MacBook and native allow me to install only 3.8… this phenomenon happened to me many times with controller and cdjs 3000 with nxs2 too…,change cables ..change hub but in 3.8 this happened almost every time … when upgrade to 3.9 played 40 times without problem and I said that unfortunately this problem solved and suddenly blurry waveform appears again with no sound … playing from may till now every day and this phenomeno appears 3 times till now … before three days I searched one old track from my finder (all the tracks is supported format ) and after 3 seconds the program closed suddenly…is this serious???? after some tests i think that this phenomenon with blurry waveform appears when i load tracks from spotlight without analyze and check consistency... can this maybe happen?

Native Instruments can you try to help us and solved all these problems ?

@Ryan_NI , @Mark_NI ,

tac0cat

FINALLY I don't feel so alone. I'm on m1 and was having troubles with s8 freezing so I moved to my s4 mk3 and now I'm having the exact same problem. There's no way I can recreate the issue. I'll have a waveform freeze and audio completely drop out. I have to force close and pray it doesn't happen again during a set.

SpirosG

https://community.native-instruments.com/discussion/comment/90911#Comment_90911

This problem appeared after the 3.9. Unfortunately i didn't try to use previous versions cause the problem appears randomly and there is no pattern to reproduce it.

The audio interface is directly connected to the laptop. USB -powered- is only used to connect the HDDs.

HDD's are 3 WD Black D10 12TB. I've made sure that they don't go to sleep through a script that reads or write a small file in the HDD every specific interval.

My system is running Windows 11, CPU is thei7-6700HQ and the GPU is the Nvidia GTX 1060.

Cause am an open format DJ and my music collection is, let's call it big, 30TB.

Your problem is not widespread as it would be reported by numerous users.... So, it is caused by something in your setup. Hard to say what...

A simple search for "Traktor audio loss and blurry waveforms" shows that its a bit widespread, reddit or the forum here, are full of people complaining about the same issue.

OliverGross

Hey,

do you have „Loading only into stopped deck“ enabled?

Since I have disabled it, I didn‘t experience a crash anymore.

I have a MacBook Pro with M2 and Ventura, using Traktor Pro 3.10.0, now 3.10.1

Maybe it helps you too.

Sûlherokhh

https://community.native-instruments.com/discussion/comment/124111#Comment_124111

If you use a controller, it's possible to re-map the load button with the condition 'deck play = off'. This works all the time, irrespective of the setting in preferences.

OliverGross

Hey,

yes disabling ‚Loading only into stopped Deck‘ is definitely helping.

I‘m on a MacBook Pro M2 and Ventura. Since I disabled this months ago I never experienced such a crash anymore. And I‘m playing every weekend about 6 Hours in a row.

I can really really recommend to disable this Option while this Bug isn‘t solved.

OliverGross

Hi,

This happens in my case with loading with a Controller and also with trackpad.

It happens while loading a track in a stopped deck.

I have posted it in the bugs section, hope it could help the developers. There they will see it for sure.

TwoFour

https://community.native-instruments.com/discussion/comment/124122#Comment_124122

Surprisingly, disabling '"Load only to stopped deck" seems to have helped? I've not experienced the issue for the past few days now.

Icekenga

I have this problem very often. The music just stops and the waveform becomes blurred! Only the traktor reboot helps! This problem occurs on version 3.11.1. And even on the old version 3.7

NI PLEASE FIX THIS

DjKrankyFranky

Quick comment on this issue here,

I had the exact same problem on 3.11.1 on Windows 11, Kontrol S2 MK1. So this is not exclusive to Mac. Lucky for me it happened during preparation. It started with some sound issues, then I noticed waveform was blurred. The song I was working on had a loop in it. That's the only noticeable thing I can think of.

I haven't played live since february last year, so my last use of Traktor was on 3.7.0 (prep and live) and I had zero issues like this.

I have the Load Only Into Stopped Deck activated.

I'm quite worried with this instability because I have a gig coming in 2 weeks. I will probably rollback to 3.7 just to put the chance on my side. What can be worse than a reboot during a live session?

How can we get more attention from NI on this?

HAYDNversusALIEN

This has been happening to me as well since 3.7. I'm still having to use 3.5. And now I have the same issue with TP4. Using a PC laptop\Windows 11\i5. This was happening on my last PC too (win10). Sucks that I paid 75 for the upgrade and can't really use it out on gigs. If I have to walk on eggshells every time I use TP4, I might as well stay with the version that just works. And NI isn't helping to solve this issue.

DJDL

I believe those who've experienced the issue on Mac computers don't have ASIO4ALL.

Quick links

Unanswered questions