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

Publicação

3 seguidores Seguir
0
Avatar

Error msg: BPM sync on. Turn off and on again to beat sync

I keep getting this message and I am not sure why or what exactly is triggering it. It often leads to quantize not working and the beats being un-synced even though sync is still on. It happens when I drop another track from a cue point or hot cue to another part of the tracks. Having a hard time replicating the error exactly, sometimes it happens and sometimes it doesnt.

Also tried messing around with quantize beat value setting it anwhere from 1/16 to 1 but I am not sure what this setting does or if it affecting my error.

Any help would be appreciated.

Ian Lippert

Publicação fechada para comentários.

6 comentários

0
Avatar

Do you have the tracks locked for beatgrid manipulation, because I had some similiar issues when the tracks where locked.

DJ Straight 0 votos
Ações de comentário Permalink
0
Avatar

Try updating to 4.1.0 and see if this is still an issue.

Pulse 0 votos
Ações de comentário Permalink
0
Avatar

Tracks arent locked for beatgrid manipulation and I just upgraded to 4.1.0. Still have problems, I think it happens most when I got into a loop.

For example I am playing my outro for track A where I drop the start of track B. Everything here is synced fine. At the end of the outro for track A I want to loop 4 bars into the breakdown of track B. When I hit my loop hotcue I get the above error and the tracks become slightly de-synced over time even if I hit the flashing sync button on track A's deck to turn it off and back on. It doesnt re-sync the tracks unless I stop both of them and start over.

I really have no idea why rekordbox is having such a hard time with such an simple function.

Ian Lippert 0 votos
Ações de comentário Permalink
0
Avatar

If I start with track B and then just drop the loop from track A I do not get the error message but the loop slowly de-syncs from track B. Is there a problem with loops syncing in RB?

Ian Lippert 0 votos
Ações de comentário Permalink
1
Avatar

I set the quantize beat value to 1 and this seems to have solved my problem. Not sure why though.

Ian Lippert 1 voto
Ações de comentário Permalink