I have downloaded all of the correct firmware and drivers for my new controller, however when I start rekordbox, even though it recognises that the controller is there, the controller doesn't work.
All of the lights are on for the controller and Rekordbox says that a controller is plugged in, but when I go to select a tune, the controller does nothing.
Before launching rekordbox, try opening the DDJ-1000 Driver Version Display Utility app, then close it. In any circumstance I've had that issue, launching the driver utility seems to "re-connect" the device to the system, even if it's recognized.
Post is closed for comments.
I have exactly the same problem. Opening the Driver Version Display Utility app doesn't help at all with this issue.
In rekordbox, with the selected DDJ-1000 driver in audio preferences, I can't play any selected and loaded track. There's no waveform visible. The level meter top right shows a clipping signal, but it's static and of course "silent".
Driver (1.0.0) and firmware (1.0.5) are up to date. The extension isn't blocked by the system (Mojave, 10.14.2). Security/privacy settings for rekordbox are set to allowed. I even removed and re-installed the driver with many reboots, no success. I even disconnected the other audio interface and all other devices from the computer in order to see, if this would have an effect.
If for example I switch to a Propellerhead Balance audio interface in preferences (class compliant, no drivers needed), the selected track is loaded immediately and can be started. But by using this interface the headphones can't be used for mixing. This is really annoying!
I presume that the more than one year old and since then never updated audio driver (released before Mojave) is the culprit in this situation ...
@phonosuper > The driver is not the issue, there are plenty of Mojave users (myself included) whose DDJ-1000 works without issue.
Here are the troubleshooting steps to check if the device is configured properly...
@Pulse, from your article: "If any / all of these steps do not resolve your issue, or you encounter trouble with any of these steps, please let us know and we'll provide further assistance."
I already did. Now it's your turn :-) ...
I never said that just because it worked on my machine it would work on yours -- clearly that is the case you are currently experiencing, it was more of an empirical statement of "it is compatible" with Mojave.
As you've already followed the steps I've outlined and even have the same problem with a clean install, it could be something to do with the hardware, but I'll direct you to please file an inquiry ticket here and our support team can gather some additional information to assist you in resolving this issue.
@Tom Penney: Does it work for you now?
@Jörg > I see you have a ticket open and have been communicating with our engineering teams; I'm going to close this forum post and direct any others having a similar issue to file an inquiry ticket if none of the standard troubleshooting steps help resolve the issue.