Whooooooa Nelly! track starts going double speed

This strange behaivior just started happening:
I play a few tracks and then out of no where the Focused deck starts going double time. Haven't found a pattern yet as to what triggers this so a bug report is forthcoming. I say trigger because my initial guess is that it is midi signal related. :S
Anyone else witness this strangeness?

-dan

EDIT: I meant to say that when this happens Traktor still shows up on my Processes tab (Task Manager) even after closing the program.

 

Yep seen this. I get this on some tracks wth no beat marker set. Its not new unfortunately, Seen this since on occasion since 1.0.

 

Hi PhilL, thanks for the heads up. Just to be clear, all of my tracks are gridded and locked with at least one marker (grid type) stored for an easy Sync. Sorry if I misunderstand you as i'm very new to the digital realm. I've never experienced this until now though.
-dan

 

So I am the only person experiencing this? Just happened in two straight sessions after about 10-15 min of use.
Track state:
-Analysed
-Gridded with marker(s), refined and locked
Gear:
-Xone4d w/default Asio driver @ normal setting
Transport:
HiQ - Normal (non scratch)
Progressive unchecked

Maybe there is an errant midi signal "jogging" the tracks forward? Nothing in the UI indicates the program receives input via midi while this occurs though
Happened while one track was playing and another was cue'd and again while two tracks were playing. Also, I cannot get the double time to stop once it starts and must exit the program.

Is there an off chance it is CPU related? I'm using an Athlon Opteron @2.21Gh and perhaps there's some wierd "hyperthreading" (forget what AMD calls it) thing going on.

-dan

 

i had this happen to me once yesterday. i loaded the track, auto analysed itself for a beatgrid, i pressed play and the track started playing really fast. i reloaded traktor and all was fine, no idea what caused this.

 

HI. Read PhilL's response please. This should not be happening, in reference to the old bug, in my case.
I'll try to figure our what may be the problem later on tonight and bring out the old VCI for a while to see if it's a controller issue.

-dan

 

I'm also getting this happening at random. I logged a call and the reponse wsas that it must be something in the TSI settings, scrap that file and start the setup again. i think it must be some off combination of midi commands triggering something, but no idea what the function would be that sends all decks off at that speed. if it was 1 deck I could imagine it was a double or half beat grid type function.

 

I think this has happened to me before, and it was on tracks that had no grid.

 

Thanks tubby,
I had suspected a midi issue even though the tsi is the default provided by A&H - which isn't really saying much. On that note, I really wish the UI for midi setup was a little more robust.

 

Just a note that this happened to me on the version before 1.2 also, so it is not a 1.2 issue only.