Traktor 2.5 grid markers ?
What happened to beat grid markers in Traktor 2.5.x ? The metronome clicks at the correct beats but the grid is.. not a grid any more. Is there a way to revert to pre 2.5 behavior aka a grid marker on every metronome hit? The beat never drifts on this track but somehow traktor is confused. This used to happen in older versions but I would be able to “unconfuse” traktor and set the grid manually with either tap or the grid controls which now seem to do nothing.
Am I missing something? Because that’s how the grid looks before you’ve placed any beat markers. as soon you mark a beat it reverts to normal.
Not missing anything. I never bothered to do it before. I woul just roll with whatever Traktor put in and adjust the phase. Seems 2.5 is a bit different. Thanks
+1 ^ set a grid marker.
check around in the settings if that’s what its defaulting to, because I use 2.5.1 and the only time it looks like that for me is when I’ve intentionally cleared the beat grid.
Damn, I’m too anal about my grids to let Traktor just set them itself. Maybe check your options to see if you have grid auto set disabled?
I could be wrong, but I think that’s the “grid” you get when you don’t have a grid present.
Coming from vinyl, beat grids are more of a luxury than a necessity. If it doesnt work out I just fall back on matching by ear. Thing is I’m starting to get into remix decks and having the markers in the right place is big help there.
Anyhow dropping the 1st grid marker sorts everything out so I’m good. Probably coulda figured that out by RTFM
Also any effect that relies on the beat needs the beatgrid set right. If the grid is of you delay beathmasser slicer and such are also going to be of
As was said before, make sure you have auto-set beatgrid ticked in preferences.
I never bother using them … I have mine turned to invisible … I cant even be arse to set them… oh and I beatmatch the oldskool way… 
it never sounds like a coconut shell horse on gallop. 
!
I also ran into this problem with 2.5. It was more of an isolated incident that would only happen if I was playing a track that I was also analyzing at the SAME time. I would re-analyze the track and then it would set a beatgrid. If I were to analyze the song immediately with out playing the the track it would work as its supposed to. After switching to 2.5.1 I haven’t noticed it, but I also haven’t had to analyze new tracks.