Traktor Pro 3 "Flushing Background Tasks" Freeze

Right, let's apply a process of elimination.

1. Happens on PC
2. Happens on Mac
3. Not the audio subsystem then
4. Not the filesystem either
5. Must be crap software

I work in software (games), how can such an old bug still be persistent from a company as big as NI?

It's almost like they don't care.

 

Well. for the first time in years I may have an insight on what is the source problem.

Whenever you add or do many operations on new files (tag writing, track analyzing and importing) traktor may somehow keep trying to write tags on files, and somehow failing (error 'writing ID3 Tags on XXX .WAV failed). This happens once per second (you can see the status bar flicker the 'ready message'.

Perhaps this 'flusing background tasks' is waiting for traktor to finish writing tags to files or whatever tasks related to file maintenance....


I hope to be of help.

and I agree with Triff, its absolutely unacceptable that a company such as NI maintains this flaw for so many years.

 

I've actually removed all music from my collection that's not a .mp3 or a .m4a and I've scanned the remaining files with mp3val/a bunch of other audio file checkers and they're all clean.

 

This bug pissed me off so many times, and now again , Traktor is dead

 

WHY WHY!!!! I have just lost yet another playlist. For a piece of software used by so many this is utterly ridiculous. NI what are you going to do!!Q!

 

I have just got this flushing tasks message on Traktor. it wont let me click anything, not even force quit. Does anyone know what to do in this situation?

 

Well normally force quit (alt-command-esc) or (ctrl-alt-del) should work. If all fails just hold the powerswitch.

And for next remap the command-q command to "save - collection" then at least you won't loose any work. Then to quit the software use the mouse to select quit from the menu.

 

just got slapped by this again tonight after 3 hours of prepping tracks and forgot to save.

 

Yeah, this one kinda sucks... I have to keep reminding myself to save my collection before I quit Traktor :/

 

Had this happen quite a couple of times aswell... mostly when recording. As previously stated in this thread Traktor seems to have some kind of Issue releasing/tagging (new recorded) .wav files & ends in a lockup when trying just that when ending the program. Does this make sense?

Last week after coming to that conclusion I disabled ALL tag-writing within Traktor, so far no further crashing (~5h of recording)... fingers crossed!

 

It's really disturbing to see that this extremely annoying bug has been around for 3 years, on multiple platforms. For me it started last few months, and it might be what pushes me over to RekordBox, Serato or something else. Mapping my controller will be time consuming, but it wont take as much time as this bug has stolen from me the last months.

 

i was never recording when it happened to me, so thats probably not it.

 

There goes my theory down the drain...well, was worth a shot.
Thanks for your feedback

 

What in the f*? I just lost FOUR hours of gridding, cueing, labeling, and organizing to this and it's a reported issue?

AND there's no default key-binding or top bar (mac) action to save collection before quitting?!? (This, apparently vital function, is basically hidden. I didn't even know that it was a right click dropdown action on the browser "Track Collection" because I only use playlists, never the "Track Collection".)

AND there's no preference to auto-save the collection?!? (how about if all decks are stopped? ...or after an interval of totally idle time? ...or how about on every change?)

AND it doesn't even "save" grid information for a single track when you hit the lock button?

I think this is a moment where Traktor is showing the age of its roots. 20 years ago computers were weaker, had limited RAM, and all had spinning HDs. There was a reason to prioritize output over writing to the file system - danger of audio drop. That is so far in the past now! Laptops have fast CPUs, tons of RAM, and commonly SSDs. It's time to balance this output priority with the need for collection changes to actually persist. At least have some "preparation" mode which includes prioritizing persistence over audio output!

Since people are discussing details: I did no recording in my in my preparation session, I did drag one loop into a new remix deck because I had never tried that before (had no intention to save the remix deck) - maybe that's what killed me?

Froze when trying to quit
OSX 10.15.7
Traktor 3.4.0 237
No error message or details, just hung with the "flushing background tasks" dialog.

 

Very disappointing to hear.
Did you get the "Flushing Background Tasks" message or did it just crash?

I spotted this in the 3.4.0 release notes.. was hoping it might have cured it..

• Robust media file tag access: increased robustness, fewer unexpected behaviors and fewer crashes in dealing with audio files metadata.

guess not.

 

UGH poor guy.... been there. Yes this is an extremely ANNOYING bug and can be heartbreaking when you lose so much work.

 

welcome to the team. the temporary fix is VERY... VERY easy on Traktor part: all they have to do is: when you trigger a QUIT command, first traktor SAVES all the work
that way, even if it freezes, you never loose your work.
But no.... we have this for sooooooo many years...

I'm not bothered by this bug anymore, as I added a CMD+S shortcut that I press once in a while.

THE NUMBER ONE TRAKTOR BUG THAT GETS ME REALLY REALLY MADDDDDD....
Is the "can't load track, desck is playing"...and its not.
That one can ruin you live set.
And there is no fix but to restart.

 

I got myself used to save my collection every couple of minutes during work...
Ontop of that I disabled all tag-writing options in Traktor.

Didn't have any crashes since then...

 

The bug still not fixed. Years! Better to save the collection always before shut down the app. This shouldn't been happening this times NI...

 

I can confirm the bug is still present in 3.4.1 -