Hi there, I have been using my DDJ-SX2 for a couple of weeks, its my first all in one controller.
The issue I have is when I baby scratch a beat and use the channel fader to fade the audio up (or down for that matter), which is a common technique when mixing hiphop etc, the audio freezes then speeds up to catch up and just sounds glitchy.
This happens with both Serato DJ and Traktor Scratch Pro, so I'm fairly sure its not directly a software issue. I can adjust anything else in the channel when scratching, trim, hi, mid, low etc with no issue, its only when the channel fader is moved. The crossfader works as expected also.
I'm coming from a modular set up using either TTs or CDJ800s with timecode and a DJM900Nexus, so this is a completely new and unexpected issue
Post is closed for comments.
@ChrisW > There is always some latency when dealing with a controller / software / audio-interface, what do you have the audio buffer (latency) settings at within the software and what is the spec of your computer (CPU / RAM) on which OS?
Hi Pulse, yeah I understand that, but it's only happening when I use the channel faders. I've tested it with the buffer all the way up to 20ms and it's still an issue.
I'm running a mid 2010 MBP 2.5ghz, 8gb ram and OS X 10.9
2.4ghz sorry.
@ChrisW > I've been informed that this is an issue that will be addressed in a firmware update coming out tomorrow! When it is released, please update and try again to see if this problem still exists.
Thanks for that, I've just installed the 1.05 firmware update...it has improved the issue a great deal, but its by no means perfect
@ChrisW > Have you also updated to Serato DJ 1.7.3?
Yes, I updated on the day of release. Still not perfect, but thats my only gripe, I'm still happy with the functionality of the controller as you can see in my latest youtube video https://www.youtube.com/watch?v=pwpTsrzxpu8
I just know that there is a limitation
I'm sure the issue rests somewhere between Pioneer and Serato but it would be the kind of glitch they both chase in circles for a while and may not come up with a better fix than is already in place. I'll put it back to the engineers that it's still not perfect and hopefully it's something that can be addressed in a future update. For the time being, I'll mark things as "Solved."
Any further update on this issue Pulse?
Sorry @Juwan, unless it has improved with Serato 1.7.4, I'm not sure there's much more that can be done to address the issue. The engineers haven't provided any further firmware updates for this either.