Sure, although this has been discussed in other threads, which were closed as “solved”.
First of all, DVS is very unprecise with small speed changes.
Try changing pitch on one turntable slightly and you will notice that
a. the BPM value doesn’t change at all, and
b. despite this having been put off as more or less a GUI issue in the past, the actual BPM doesn’t change as well. Which makes beatmatching a lot more difficult than on competing systems like Traktor, Serato or even Mixxx, as the input needed is much more brutal (for the lack of a better word).
The other problem is that you can’t really circumvent that issue by using sync, because when you activate sync, all speed manipulations on one deck are automatically transferred to the other deck. This behaviour does not change depending on the BPM only or BPM and beats setting. Also, it takes far too much speed change for the option to disable sync when scratching or jumping to cue point to kick in, which makes this option useless for beatmatching with files where the grid does not match absolutely perfectly.
All of these problems do not occur in other software I use or have used.
The sync issue described above also didn’t occur in earlier versions of DJay (I think the change came with the same version that introduced flexible beatgrids).
I am using the ios and macos versions, most current ios version on a 10th gen iPad, and sonoma 14.7 on a m3 pro macbook pro, so it’s not a cpu issue either.
Djay is on version 5.25 currently, but the problem is present at least since 5.0.
On the iPad the version of Djay is the most current one as well.
My main audio interface is a traktor audio 10, which I have tried with the built-in phono preamp, with line input and the turntable’s preamp, two adjustable external preamps, fresh styli and different pickups (Shure m447 and concorde pros), so it can’t really be that, especially since that combo works perfectly in traktor. I have also tried rekordbox, serato and djay timecode. Makes no difference.
Hi @jimbobatzke, thanks for sharing these details. I’ve moved this to it’s own topic so that we don’t lose the conversation and can keep this all organized. I’ve also reformatted your paragraph a bit so it’s a little more easy to digest.
I will be passing this onto the engineering team directly, but I think it would be super helpful if you could record a short video highlighting the issues you have described above. This will really help to communicate things to our engineers so they can try to replicate your specific issues. Once recorded, please upload it to your Google Drive/Dropbox, enable sharing permissions, then share a link to the video here. Thanks!
Here it is. I have also compared the 5.x behaviour to the behaviour in Pro AI 4.1.10, where everything behaves more as I’d expect it.
I hope that helps.
Edit: for some reason dropbox doesn’t seem to play ball, so I also uploaded the video to youtube as unlisted (so not indexed for youtube search, but playable with link)
Hi @jimbobatzke, thanks for sharing this, unfortunately, DVS feature has a lot of issues, I have posted several ones, but doesn’t fixed at end of team of Algoriddim. It’s seem they are too young for that, they focusing controllers, not oldschool guys like you and me, and those whose use DVS we are not in the spot
please check this video, have you experienced something like this? As I watched your video, I’ve discovered some similarities as mine.
Thanks for the quick turn around on the videos @jimbobatzke. I will share this with our engineering team to see if they can replicate the issues and offer any suggestions. Thanks again!
