Have a feature request or suggestion? Post your idea here!

Post

2 followers Follow
0
Avatar

wrong beatgrid and cue points

I recently upgraded from rekordbox1.4.1 to version 2.0.3.

 

When I open my songs, the beatgrid and cue points seem to be a little bit off. The beatgrid is 30 ms too early (most of the time). When I re-analyse the track, the beatgrid is perfect, but I have to save all my cue points again (since they are all 30ms too early). I already did this for 20 songs but since I have more than 1000 songs this seems to be a waste of time.

 

What to do?

s_decoster

Post is closed for comments.

9 comments

0
Avatar

Sorry I can't answer this with accurate wording being I'm away and don't have rb with me but there is a setting in the preference that if you have your cues and such set from an earlier version you should select that option so it knows and and compensates for the cues being off I believe. It's somewhere in the first window when you open prefs

BriChi 0 votes
Comment actions Permalink
0
Avatar

I found this quick on their site.

 Regarding the issue where beat grid information analyzed with rekordbox older than 1.5.4 will not be correctly displayed on later versions

From version 1.5.4, rekordbox disables gapless playback for MP3 files encoded with the LAME encoder on players such as the CDJ-2000. This modification will shift existing beat grids, loops or cue points of mp3 files encoded with the LAME encoder.To solve this problem, the version 1.6.2 includes auto-adjustment function of BeatGrid and Cues for LAME encoded mp3 files which imported and analyzed/adjusted with an old version(except 1.5.4 & 1.6.0).You will find a new option at the bottom of the tab "General" in Preferences.If you use mp3 files, please tick "BeatGrid". In addition, if you set loops and cue points usually on rekordbox(not on CDJ), please tick also "CUE points".

BriChi 0 votes
Comment actions Permalink
0
Avatar

Thank you for the feedback. I selected both both nothing happened. Then I re-analysed one song but the same happened as before, after re-analysing the beatgrid shifted 30 ms but the cue points I made stayed in place, which means I have to adapt 10 cue points per song, which takes a lot of time!! Or is there something else I can do??

s_decoster 0 votes
Comment actions Permalink
0
Avatar

When I first installed 2.0.3 I did not select those 2 options in the general section. Rekordbox had to analyse all songs (because it needed the key and other information e.g. to zoom the beatgrid on the cdj 2000 nexus). Maybe now Rekordbox "forgot" that these cue points were made with 1.4.1 and thinks they are made in 2.0.3?

I checked this again for an other song: in 1.4.1 everything seems normal, however in 2.0.3 cue points and beatgrid are too early...This suggests that they are still in the 1.4.1 format, even when opened in 2.0.3.This is very strange since 2.0.3 analysed all songs the first day I downloaded it !!!!!

Next I re-analysed the song in 2.0.3 (both options for misalignment are selected in the preference menu): the beatgrid jumps into the right place but the cue points DON'T.

I would like to know what I have to do...I can try to keep track which songs I manually changed (+- 30, they are all ok now) and which are still wrong...because I hope with a next fix all the songs I manually changed won't be fucked up again (I now have a library where most songs are analyzed with the 1.4.1 system and a couple of 100 with the 2.0.3 system).

 

Maybe the option "BEAT GRID and CUE POINTS" in the general tab don't work properly??? It seems so with me since all beatgrid and cue points are wrong (and only the beatgrid changes when i manually re-analyse...)

s_decoster 0 votes
Comment actions Permalink
0
Avatar

Pulse? Gavin? Any news on this? At the moment I am just waiting because working with rekordbox when all my cue points are off (the one's i made with the old version, which is 95% of my collection) is quite pointless...

s_decoster 0 votes
Comment actions Permalink
0
Avatar

No answer after 12 days? Come on!! I cannot believe I am the only one with this problem. I even don't know if I should update to the new rekordbox or not...

s_decoster 0 votes
Comment actions Permalink
0
Avatar

I'm sure this isn't what you'd like to hear (and Bri correct me if i'm wrong) but there was a 2.0 generation update where track analysis was amended and part of the install instruction was to re-analyze your collection.  I experienced the same issue @s_decoster re: cues and the like being off a few ms and had to go back and adjust them all manually.  I read and participate in the forums pretty regularly and never heard of a quick fix for this unfortunately.    

Fox 0 votes
Comment actions Permalink
0
Avatar

Hey Fox, thank you for the reply!! I appreciate your reaction.

 

I think I will adjust everything manually then (or rip my cd's again to aiff to avoid such problems in the future).

 

Do you guys think it would make a difference if i Update to the latest rekordbox version from my 1.4.1 version or the 2.0.3 version? I guess I have 2 databases now (1 for each version). I can try to delete the 2.0.3 version from my pc and upgrade from 1.4.1 to 2.1.1 while selecting "BeatGrid"and  "CUE points" in the general tab and see what happens. The only problem then would be that I have to adapt all songs cued and analysed in 2.1.1 since rekordbox will think they are made in version 1.4.1 since I selected the auto-adjustment function of BeatGrid and Cues function.

What a pain in the ass :-)

s_decoster 0 votes
Comment actions Permalink
0
Avatar

I first analyzed my collection in 2.0.1 so can't speak to issues updating from 1.4.1. I looked back into the change log and it was 2.0.2 where the beat grid analysis was changed and we were all required to re-analyze our collections. It seems to reason that you will experience identical issues going from 1.4.1 to 2.1.1 as you did going to 2.0.3. I would say go straight to 2.1.1 choosing the options Bri recommended and whatever's off after that, you're stuck dealing with manually (unfortunately). Unless something has come to light off-line from the forums that I'm not aware of.

Fox 0 votes
Comment actions Permalink