Beatshift Fixer Functionality Question

Question about the beatshift fixer function. Last Week … I pulled my rekordbox collection into lexicon to use some of the features like “remove duplicates” … and when i brought the library back to RBDJ7 it shifted all my grids and hot cues slightly to the right. This is the second time this has happened to me with just simply pulling my Database from RBDJ7 into Lexicon and back to RBDJ7. I didnt not move the database into serato or any other software package.

It also destroyed my grids on many songs which forced me to analyze entire performance playlists on the fly during a performance just so the grids would do their job again in the software.

The first time this happened was about a year ago… I fixed about 4000 of my 20,000 songs manually over the course of about 6 months. Then completely forgot about the pain and suffering it caused me and why it happened… until i accidently did it again last week.

Here is my question… during that 8 hour DJ set where i was surprised by the shifted grids and hot cues… I had to manually move my hot cues back on to the grids for about 400 of my most played songs. leaving about 19600 tracks with the hot cues still shifted slightly to the right.

If i do this beatshift fixer function on my collection… it is going to fix the remaining 19.600+ songs? more importantly… is it going to take the 400+ songs i fixed live during my gig… and shift those to the left as well?

forcing these corrected tracks to the left will force me to go in and recorrect these tracks manually a second time.

Also… reading the details about this beatshift fixer function… it says the function is going to “re-encode” all my music again. doesnt this mean its going to resample all my already sampled lossy MP3 files? thats going to resample a sampled file already and downgrade the quality of all my tracks right?

Using the beatshift fixer makes the grid you have in Lexicon leading, so if that is correct then after using the fixer it should also be correct in RB after a sync. The sync is important or RB will have the old grids.

It is simply going to re-encode the file back into 320kbps (or whatever you were using) so it should not degrade quality. But you can always check with a single file.

As for grids shifting when all you did was import and sync back… That is strange, it should not happen normally.