This seems to be isolated to the Windows version; it still does stretch with the Mac version. I've asked our rekordbox team to investigate.
As the title suggests, previously with Rekordbox DJ when I changed the tempo of the song playing it automatically stretched or shrunk the enlarged waveform to correspond to the BPM playing. So for example i have a track at 128 BPM playing in Side A and a track playing at 132 bpm in Side B, the beatgrid's dont match up, however when I changed the BPM of track B to 128 the beat grid stretched and matched the grid of track A.
I've recently reinstalled Rekordbox and now i need to scroll with my mouse wheel to adjust the beatgrid after changing tempo.
Anyone know how I can fix this?
Thanks in advance!
Post is closed for comments.
This seems to be isolated to the Windows version; it still does stretch with the Mac version. I've asked our rekordbox team to investigate.
Thanks mate, I've noticed an update which I've tried however same error occurring. Also tried reinstalling although that didn't work either. Appreciate the help!
Any Update on this one Pulse? Thanks
Basically what I'm trying to achieve is having the wave always completely zoomed out, at this stage i have to use my mouse scroll wheel to re-zoom out after i change the tempo of a track.
That sounds like a different issue -- are you saying the waveform isn't stretching or the zoom level is resetting?
Are you using a controller? Which version of Windows are you running and what is the make of the graphics chipset / driver version?
Using a ddj-wego controller, windows 10, amd dedicated graphics card, same specs as what I was using before. I'm saying when I change the tempo slider on my controller for track b so bpm matches track a, the sizes of the beat grids don't match, whereas previously they were matching when I altered the slider so bpms match
@Adem Try unchecking the "Enable DVS Function". Worked for me!
@Adem > The solution, as @Evan suggests, is to un-check the DVS function within the preferences. Have you tried that?
@Pioneer can we please have this issue/bug fixed when running on DVS? it's quite annoying....