FLX10 Mapping Doesn't work in Aug 2025, Seriously?

Questions
1

So right now, i’m using the free 7 day trial to play with Djay Pro before subscribing, which i might add i will not be doing.
To have the pioneer flagship controller unable to be completely mapped on the basic functions of any controller is simply lazy and unacceptable from a company of this size.
Seems they prioritize their rather inferior controllers for complete native compatibility.
What this software is doing is incredible, and having spend 3 days engrossed into learning all the ins and outs and playing with it, i can honestly say i love it…
However…
To have the midi mapping not completely compatitble with the FLX10 is lazy. In particular the pad mode buttons not working OR being picked up within the midi mapping editor… like… what the hell?
Yes, i have updated the firmware, and the software. My hardware is not an issue here, it works on Serato, Rekordbox, and VDJ with the mapping being able to be adjusted… Sadly not DJay Pro
The pad mode issue has come up on these forums since late 2023 i believe… it’s almost late 2025. Two years this issue has been unaddressed.
The fact that the pad mode buttons are completely undetected by the software… i’m quite appauled.
Perhaps working on fixing this BASIC issue before claiming that the controller is supported, with an * next to it claiming that ONLY the jogwheel display doesn’t work.
This is a lie, as a lot of the functionality of the controller doesn’t work. Some i can live without, but being unable to see the pad mode change within the software is one of the basic control functions on any deck…
I’ll sadly be cancelling this, because this company seems unable to be honest about the FLX10’s compatibility with DJay Pro. Please be honest to save people time and potentially money on your product going forward.
I’ll look back in perhaps 2 years or so and see if you have done the mapping properly. Unlikely seeing as your topic board has posts about this same issue from 2 years ago…
Kind Regards and good luck for the future.

3

Hi @Luiscypher7, welcome to the Community! Sorry to hear you’re experiencing this issue.

Please note that the FLX10 is natively supported now on Windows including the jog wheel screens so it sounds like you are experiencing some unexpected behaviour. We recently made additional improvements in the djay 5.4 release for macOS and Windows. I would be happy to help you troubleshoot this further if you can first provide some additional details about your setup:

Device Model (ex. 2020 iPad Air 4th Gen):
Version of operating system (ex. iOS 17.3.1):
Version of djay (ex. 5.1.3):
Hardware/controllers used (ex. Reloop Ready):
Hardware Firmware Version (ex. 2.7):

Please also capture and share a short video of the issues you are experiencing so I can better understand the specifics. Thanks!

4

Device Model : 2023 MacBook Pro M3 - 32GB
Version of operating system : iOS Sequoia 15.6
Version of djay : 5.4.2
Hardware/controllers used : Pioneer DDJ FLX10
Hardware Firmware Version : ver.1.14

The issue I’m having is with the pad mode buttons not displaying any change in the Djay Pro software. the functions work fine, I heard the effects, and other things fine. just have no clue what those functions are.
Everything else works fine, including the cogwheel display changes using the Shift + Page buttons above the performance pads.
Not at home right now but I will try and make a video showing what’s going on.

5

Ah okay! That’s much more clear @Luiscypher7. Thanks for the additional info.

What you are describing is indeed expected behaviour at the moment for most DJ controllers. There is an existing suggestion topic to add MIDI commands to djay to change the onscreen display modes. The team is working on this, but unfortunately some edge cases with some hardware has prevented them from releasing this functionality yet. Please see below for the topic I’m referring to:

6

Dear @Slak_Jaw

Honestly, this Performance Pad mode mapping should really be a top priority.
I am among those not understanding how this is continuously delayed, as so many users.
It is really a must have.

I know the "there are some exception cases where this is difficult"and “some things are done under the hood” explanation, but c’mon…
It has now been three years since you raised this yourself.

At least, get these performance map buttons intercepted by the midi mapping, and provide midi entries for the pad modes, please. Long overdue, isn’t it…

7

Thanks for the additional feedback @Davidv100. I’ll let the devs know.

1 Like