"Beat Sync Error. The track has no beat grid information" Error message 4.0.8 even though all works fine?
Hi,
Using Version 4.0.8 and everytime I load a track and the following error message shows in the bottom info bar in red "Beat Sync Error. The track has no beat grid information". The message appears everytime I load a track.
Now ALL tracks are beatgridded and have all relevant information. This error message also holds no weight as everything syncs up fine, this message only seems to have appeared when the database was moved to my external USB3 hard drive where all my music tracks reside.
As I say, doesn't cause me any issue or performance problems but is really annoying flashing red each time I load a track. Can I get rid of it Pioneer or at least what may be causing it?
Regards John
Can't find help? Search our Support Site or alternatively, reach out to our Support agents
Official comment
I've just heard from the rekordbox team and this will be fixed with the 4.1 update!
Ok - Got a little futher with my investigation. The message only appears when the track had been gridded and then locked to prevent further changes. If I 'Unlock' the grid the message doesn;t appear / relock the grid and reload the track to a deck and the message is back.... Is this a bug?
I have been having the same issue. It disengaged the sync too when you load the track. But if you re-engage the sync they pay perfectly fine and in sync with each other.
All of my tracks are analysed, gridded and cued then locked.
Very annoying bug!
I'll bring this up to the engineers. I'll post any updates they give me.
Thanks Mark, hopefully they will be able to reproduce it and then fix it... :)
@John > What exactly did you do to move the tracks? And did you properly relocate all of them after the move?
Nice one Mark.
Just something extra, I did a 2 hour radio show like this and all tracks were locked. Most had this error come up and sync was lost until re-enabled, but some didn't and worked as they were supposed to.
@Pulse > The tracks were always stored on the external hard drive, sorry I should have been more clear. All I did was move the database from the internal drive to the external drive - tracks themselves stayed on the external drive. Since this started happening I have moved the database back to the internal drive.
John
@Pulse
That is superb, thanks for the update! :)
Legend! Thanks for the info!
Happy to say this has as advised by Pulse now been fixed in 4.1.0 :) - Very happy RB user...
Awesome - thanks for reporting back!
12 comments