Traktor load track freeze?

DJ Software & Apps Traktor
1

Traktor load track freeze?

Hello all recently I have noticed after a couple hours of play When I load a track from my s4 to traktor , only the cue points load visibly on screen but not the wave form and it freezes for about 30 seconds…

It has always after 30 seconds resumed to normal but I had a gig about 2 weeks ago where it froze for about 1 minute and it was pretty freaky since the party was fully hype at peak time..

I have noticed it does it more when I plug my laptop charger back in since my laptop is dying, any one have this happen? any suggestions ?

2

Are you loading the tracks from the collection or from the explorer or iTunes node? Do you mean the battery is dying in your laptop?

3

mine does it too when I load tracks from traktor with the load button on the S4. The screen freezes but music keeps playing which is alright. I found that all I need to do is move the mouse a little or touchpad and everything is cool again. Give it a try

4

Happens to me all the time , waveform freezes when loading tracks but audio remains constant so after awhile I’m kinda used to it

I really hope this gets fixed in the close future though because i always worry that when the waveform freezes eventually so will the audio!

5

@photojojo I play 3 sometimes 4 hour gigs so my laptop is dying by the end / also yes I am loading them from the explorer

I have never really though of not using the load button on the s4 since I don’t like to touch my laptop but I’ll give it a go see if anything changes , also is there a keyboard short cut instead?

and yes that is exactly what is happening to me it freezes but audio is still playing perfectly but The fact that it freezes is the part that freaks me out , I def don’t want it too freeze and the track run out.. lol

6

Honestly that sounds different…The load track button freeze issue seems to have been resolved with the latest version of traktor 2.0.3, or at least it has been for me.

7

Yea my fault I meant 2.1.1 . I havent gotten an issue since I switched from 2.0.3 to 2.1.1.