Problem after re-analysis in 2.0.2 - PLEASE HELP (updated)

@Glen > Have you Quantize enabled? This will enable the hot cue to jump to the correct beat.

@Gavin - yes it's always on, however I don't think I've explained the problem correctly for you to offer that question.

the issue is not that the program doesn't jump to the first queue point. It does. My problem is very similar to a few months back when a load of us had to revert back to an older version because the update threw all our queue points out by half a beat, remember???

right now the program snaps all my tunes to the first queue point, HOWEVER a vast majority of the queue points are not in the same place following the update. . Most are approx 1/4 beat BEFORE the start of the track. The beat marks themselves are now mostly spot on and in time so looping isn't a problem but nothing is queuing where it should, and this applies to hot ques and preset loops I've programmed previously too. They are all 1/4 beat behind where they should be!

This is a more complex problem than the usual checklist for noobs. I've now tried re-analysing my entire collection three times to no avail.

I have attached a picture depicting an example of the problem below. You can see that quantise is on, I have asked the program to snap to the first beat which IS marked correctly - however the program is obviously registering my PREVIOUS queue point. If this tune contained hot queues previously they would also be out. It definitely has something to do with the re-analysing advised in your recent post IMO!!

If you reanalyse your tracks, you have to redo all your cue points and hot cues.
The advise was just to reanalyse tracks imported between certain dates...

Phil, I have re-analyzed all my files many of times when newer versions come out, this does not erase cue points or hot starts, just re-analyzes the wave, beat grid and bpm

hi brichi - you are correct, it does not erase points you have previously set - however the new analysis may be (it usually is) a bit different to your previously adjusted file meaning you will have to manually redo any cue/hot cues etc

I agree, fortunately when I re-analyze it's been just "fixing" the beat grid which does not move the cues or hot starts being the wave itself is still the same, I set my own cues and such not relying on the grid and quantizing so each analysis has been ok for me, But like you said, That doesn't mean it won't effect everyone, It could definitely cause some shifting

Brichi - in that case yo're a rarity - most of us use the quantise functions. If the definiteive answer to my problem is - "well that's just what happens when you reanalyse your tracks - if you ever do that then you'll have to manually go in and adjust all the cue points the program subsequently throws out, thereby consuming a MASSIVE chunk of your already used time and effort" then fine. BUT I'd appreciate a definiteive reply to that effect so I know never to re-analyse again for fear of throwing 5k + tunes and their hot cues out of sync!!

At the moment it feels like every time an update is released I wait, scared that something's gonna fuck up if I click yes, and then finally bite the bullet and click yes, only to find..... guess what :D

Gav/Pulse - could you please tell me if Phil's statement above about me now having to redo all my cue and hot points is accurate?

I hear ya, A lot of guys I know just shut it off because of this reason, especially when using the mk1's because you never know if the grid is on or off unless you go through EVERY track to confirm first which is a lot of work and a lot of us just don't have the time, I would rather leave it off and do my loops and hot starts manually by ear like I always have done. Maybe once Pioneer gets this all straightened out I will give it all a shot

Glen Gavin -  I just went through this same issue because I was having trouble seeing some of the large waveforms on my new cdj 2000 nexus.  I reanalyzed my tracks and then had to manually go thru and all the grids.  I wish there was some sort of lock on the grid so that It could not be messed up like traktor has.  I only had to do about 900 tracks and what a pain in the butt.  It really sucks that when there are updates it messes up all of your hard work.

re-doing beat grids is such a pain in the backside. i've done a load recently too, it shouldn't be needed and pioneer need to ensure this doesn't happen again.

i find the whole setting beat grid a bit hit & miss anyway. it doesn't feel very accurate, nothing like as good as Traktor and often it's a bit out if you playback with sync on. The whole analysis/beatgrid setting needs a good overhaul in my opinion as it's currently not very good.

Also, try setting a beatgrid on the iPhone app, you can't see anywhere near enough detail to spot the transients. it's useless at the moment.