Last night I took rekordbox DJ for a spin at a venue with low end gear, I normally only use CDJ's but don't want to carry all my equipment (read take my bike) to these places. I instantly discovered a few quite major bugs in the software, not show stopping but annoying. My library consists of 99% AIFF's, all with memory cue points / loops, no hot cues. Rekordbox DJ set to load first cue point, sync on.
During my six hour set I experienced the following cue point / loop and sync bugs:
80% of the time a memory loop would not sync with the master track when played. The tempo would set alright but not snap to the grid. Even though sync was on the jog wheel worked to nudge the track in phase.
10% of the memory cue points would not sync, like above.
5% of the songs would auto play, even though it's turned off, and ignore to load the first cue point.
Another 5% would load the first cue point / loop and auto play it. Auto play is still off.
Has this setup even been tested? I mean, within 5 minutes I found these very obvious bugs and they kept on appearing randomly throughout the set. Please Pioneer, give some feedback here, some bug patching needs to be done.
Otherwise I must say rekordbox DJ was a pleasant experience, even though the 350's are very limited, I almost didn't have to touch the computer all. And performance wise there were no problems, my two year old Macbook Pro didn't even get hot. Taking my bike tonight :)
Post is closed for comments.
@Henrik > When you say that the memory loop and memory cue points were not in sync, do you mean "quantized"?
If a song would auto-play, is it possible that you loaded a track to a deck that hadn't been stopped -- rather, the track finished, the player looked stopped, and you loaded a new song, then it started playing?
These are due to the function / design of the application, and things that are being looked into for future improvement.
I mean that the tempo would match but the beat grid wouldn't snap. Very frequently as described.
Hm, not sure about the second one. But I very rarely let a track finish. Even though, it should load the first memory point, just not start playing automaticly from zero with "load first memory ponit" on?
If not, poor design in my point of view.