Hi everyone,
Following up on the DDJ-RR native mapping limitations, I wanted to share some findings after extensive testing.
I successfully managed to “revive” the buttons that are completely ignored by the native mapping (specifically the PAD FX1 button) and are not detected by the MIDI Learn feature by default.
The Findings:
- The Inputs exist: Using an external MIDI Monitor, I confirmed the PAD FX1 button sends Note 30 on Channel 2.
- Manual Injection works: By manually editing the
.djayMidiMappingXML file and injecting the code for this specific note, Djay Pro does recognize the button. It appears in the MIDI Configuration list, allowing me to assign actions to it. - GUI Limitation Confirmed: While the functional mapping works (the pads change behavior internally), the GUI does not visually switch to the corresponding FX/Loop view. This confirms what @Slak_Jaw mentioned in this thread regarding hardware-specific UI locks.
Conclusion & Future Outlook: I have decided to leave this manual mapping active in my configuration. My reasoning is to “future-proof” the setup: if the development team eventually decides to support the feature voted on in the thread linked above (allowing MIDI commands to trigger UI changes), my mapping will already be prepared to work fully.
Regarding the other missing functions I reported in my other thread regarding the DDJ-RR (specifically the Grid Adjust /2 & x2 and FX Hold buttons, I haven’t had time to apply this fix to them yet, as I’ve been focused on solving the PAD FX issue first.
I am slowly learning the ins and outs of XML editing to bypass these limitations. Since official answers or updates can sometimes take a while and these functions are becoming essential for my workflow, I will continue testing to manually map the remaining dead buttons and will update the community with my results.
Hope this helps anyone trying to customize their DDJ-RR mapping further!
Best, Albert_Maro
