Nah I'm just stupid. Just closed RekordBox and re-opened it, and it's working fine now. I don't know why I didn't try that before posting here.
is this happening to anyone else? My first thought was to check the CFX selections towards the top of RekordBox, but it's either been removed or I am very stupid and not seeing it.
thanks!
Post is closed for comments.
Nah I'm just stupid. Just closed RekordBox and re-opened it, and it's working fine now. I don't know why I didn't try that before posting here.
Glad you got it resolved! Let us know if you need any other help.
This has happened twice to me since the update, too. I don't think it's an acceptable workaround to turn RB on and off - that would mean I have to check the filter every single time I use RB and the DDJ-RR before a gig. This is a fault with the software and/or hardware and it needs to be fixed. Is there a plan to fix this ASAP?
@Stu > Twice or every time? If it's not every time, it's hard to troubleshoot.
Yep, I take your point, however it's happened to me two out of three times when I've performed with the RR since the update, so it's fairly serious. After the first time, I did an hardware update on the RR and it was ok the next time, but it happened again last weekend. Any insight into this would be greatly appreciated!
It's not working for me - no matter how many times I open/close RB. Any tips for how this can be fixed?
I'm talking about the filter knobs not being responsive
@Andrew > As you're posting to an old and haven't provided much to go on, I'll need to ask...
- which OS?
- which version of rekordbox?
- what hardware are you using with rekordbox?
- which version of the drivers and firmware are installed for that hardware?
Hi,
Sorry for lack of details.
OS is Mojave (10.14.2)
Rekordbox is 5.4.3
Using the DDJ-RR
And.... OK, that's done it. Just updated the firmware and that seems to have done the trick.
Thanks!
OK, I take that back - just updated the DDJ-RR firmware to 1.08 and driver to 1.300 and it worked at first, but then stopped again.
It's working again now, but I'm not sure for how long...
Okay, please let us know if the issue returns.