Bug: deck suddenly not being able to play

c0nsul

I guess it depends on each individual workflow. Personally, I don't use that feature as I prefer quick loading/changing tracks.

But, there is a workaround (someone mentioned in another thread) to achieve the "load only into stopped decks" feature without activating it: Simply map the "load" command with a modifier to only work when deck is not playing.

knetter

Yeah, disabling "Loading into only stopped track" and RELOADING the same track into the stuck deck will unstuck it. You can enable "Loading into only stopped track" again afterwards. So no restart is required. Thanks for the workaround! Still quite a major bug though....

creal

Thank you very much for the workaround.

I'm sure it will be useful.

But yeah, in the end, it is not serious form NI to let this kind of bugs running into the wild...

Hirschie

I have this Bug too again since the latest verions 3.9 and 3.10!!! Two Gigs where i had to sweat.

I think in 3.4 it was fixed. Played a while with this version and cant remember to had this bug.

10 years ago i often had this issue in 2.68. This problem exists since Traktor Pro 2 !

This is going to completely blame NI. Thanks for the workaround.

Miles Hi

Late answer, but after using traktor for many years I had this same issue the other night at a wedding.

Song would play if I pressed and held cue points down, but play button and software button would not work at all, this only affected deck B.

I'm using traktor 3.11.1 and macbook air m3 16gb.

The way around it was to load a track into deck D and then press play and while it's playing (fader turned down) I loaded the same track in deck B so it instantly started playing in the same position.

After this I could use deck B normally again.

As soon as I get time I'll open a ticket with native instruments, but if it's been happening for so long it's not going 5o be an easy fix