Numark Mixtrack Pro FX

Basic mapping for the Numark Mixtrack Pro FX


browse              - cycle
load                - load

master gain
cue mix/gain pfl
channel faders
pre fader gain
high,mid,low eq
pitch faders
top four pads used for loop points, shift to close


browse      - scroll
load        - load and play
play        - reverse direction
cue         - goto begin of track

This is all new to me, so its not going to be perfect. I’m still trying to get the vumeters to work.

1 Like

This controller is almost the same as the Numark Mixtrack Pro 3 and I suspect most of the MIDI messages are the same. So I suggest starting with the Mixtrack Pro 3 mapping and making the changes specific to this controller.

Thanks for making a great start on this. For me, the shift functionality is wrong - for instance, to remove a cue you press shift, release, press the pad, and then press shift again to come out of shifted mode. When I have some time I will look to fix this.

Hello, I am quite interested in this controller (FX line).

In my opinion, doing a mapping for the pro FX mixtrack will almost allow you to have a mapping for the platinium FX.
The only differences between these 2 controllers are:

  • the information screen on the platinium jogs (which already existed on the old platinium mixtrack)
  • the 4 turntables on the platinium (which also existed on the old platinium mixtrack)

Also all the platinium fx buttons are present on the pro fx, which means that it should also be possible to have 4 turntables on the pro FX.

I have the impression that this line of Mixtrack FX controllers is in direct competition with the popular Pionneer DDJ400 and the NI S2 mk3.

In any case if I opt for this controller, which is likely I would be happy to give feedback.

Thank you very much for starting to write the mapping for this controller.

Then, Why wouldn’t it be better to start the platinum FX mapping out of the platinum mapping instead of the pro one? Isn’t it just a few more buttons?

1 Like


I just got a Mixtrack Platinum FX and would love to see a mapping for it.
Also, I’m pretty new to mixxx and have only glanced the mappings but am wondering the same question as @JosepMa: would it not make more sense to start with the platinum mapping instead of the pro one?

Also, I’d like to help out with the mapping development. At the very least, I can test stuff. But if needed, I can also work on the mappings in order to help with the effort. I would just like to avoid duplicate work.

@bad1dea5 thanks for sharing your work!
One thing I’d like to ask, If I may: how did you tell the controller to stop his ****ing “carnival mode” (LEDs jumping around and not responding to midi, although the controls work) when Mixx launches?

I know it didn’t before installing your script, so I’m curious, how did you do that?

Is that a midi message sent to the unit on connect? If so, what message? I’m trying to map the Mixtrack Pro fx in Traktor Pro 3 and knowing this could MAYBE help me getting rid of that stupid demo mode…


That’s done with a MIDI SysEx message, which is used to exit the so-called demo mode. The message
depends on the controller and I have just found out that it is the following for my Platinum FX:

[0xf0, 0x00, 0x20, 0x7f, 0x04, 0x01, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0xf7]

1 Like

well thanks a lot man! now i only need to find how to send sysex from traktor! But hey, it’s a start!

Thanks again!

@bad1dea5, any news on the progress with your mapping? What is the current status? Do you think it makes sense for me to start the Platinum FX mapping based on your work, rather than doing it from scratch?

I think it would probably be easier to start from the Mixtrack Pro 3 mapping.

I have a Mixtrack Platinum FX too but the MIDI Sysexmsg does not seem to work for me (I copied the “Mixtrack Platinum” Controller mapping and edited the “end demo-mode” line).

Where did you get the “Message-String” from?
Do you have the displays on the Jogwheels working?


P.S. Maybe we should move this to an extra topic? Numark Mixtrack Platinum FX Mapping

I did a bit of reverse-engineering. Please try out the files at Right now there’s not much else besides exiting the demo mode.
Let me know if it works for you.

No, but I guess it should not take too much effort…

Definitely, I’ll continue the discussion there.
Thanks for joining the Platinum FX club! :slight_smile:

I’ve made updates for this, check out the github page.

You can exit demo mode with
0xF0, 0x7E, 0x00, 0x06, 0x01, 0xF7

Thanks for getting off to a great start with this work. For me the change function is incorrect, for example to delete a signal, press Shift, release, press the keyboard and press Shift again to exit Shift mode. If I have time I will try to fix this problem.

Hello bad1dea5, I’m having a lot of trouble understanding, I tried your mapping files for the Mixtrack Pro FX and nothing works (except the code you gave to turn off demo mode), I even have a code error on each launch (here was a problem parsing the XML file /home/user/.mixxx/controllers/MixTrack_Pro_FX_MIDI_1.midi.xml. unexpected character at line 50, column 90) and I do not see the name of the midi file in the Presets … On the other hand, when I try the controller having chosen the mapping of the Mixtrack Platinum, I have a partial operation of the controller.

So, since my Mixtrack Pro FX works partially with the MIDI mapping of the Mixtrack Platinum, I am considering replacing it with the Mixtrack Platinum FX, what do you think?
Has anyone tried the Platinum FX with the Platinum mapping and does it also have partial and correct controller operation?
Thank you in advance for your answers :wink:

I have my new Mixtrack pro FX controller. I started by buying the Pioneer DDJ400 which is almost fully mapped with Mixxx. But I found it too plastic. So I turned it over to take the pro FX. I find that it is of better quality than the DDJ400 … But now there is still the mapping to be done with Mixxx.

Thanks to @ bad1dea5. I tested your mapping. It works for my controller (I’m on Ubuntu).

I am new to controller mapping. I do a tiny bit of javascript so I am limited enough to help with development. I am ready to contribute anyway.

I did again a midi learning of the controller on mixxx just to get the midi codes. From what I see they are not really identical with the Mixtrack pro 3 or the platinum. In addition, it is possible to do a lot of things just with XML mapping without having to go through JS, and I like the default behavior of Mixxx.

The point that seems difficult to manage and which does not yet work with your mapping is the management of pad modes. The pads work very well (for example to map cues points) but without using the mode pads (CUE, LOOP, Fader-cuts, Sampler, FX1, FX2 …). And the best would be if we could also manage the pad modes with shift to increase the possibilities even more. Then add to that the activation of the leds :star_struck:

I tried to see how to do it and there it is difficult for me to program. One difference that I noticed compared to the mapping of the Pioneer DDJ400 which also has the mode pads, is that the pioneer generates a different midi code when we activate a mode, which really simplifies the task. For the mixtrack FX, the mode does not modify the midi code of the pad.

Do you have any idea how to manage the pad modes?

In any case, thank you again for the work done.

@WumaSoundMix. Hello, could you tell us which platnium fx mapping you used? Because from what I see for the platinium FX the mapping seems less advanced than that of the pro FX offered by @bad1dea5. I think the mapping of one will suit the other because the differences are so small. We still have to check that the midi codes are the same (I hope anyway!). I would even say that the Platinum FX could be completely suitable for the Pro FX except for the display on the decks. We should also be able to use 4 decks on the pro FX. I even think it would be wise to eventually have the same mapping for the Platinum FX and the Pro FX and just have parameters to modify to indicate that it is the Pro or the Platinum. (or for example 2 or 4 decks).

Hello @snib,
So finally I opted for the Numark Platinum FX and I therefore use the mapping of the Platinum existing natively with Mixxx.
I just personally “reassigned” the following functions which do not work when I load the Platinum mapping:
1 - Browse
2 - Master Gain
16 - Pitch Bend Down
17 - Pitch Bend Up
18 - Pitch Fader
21 - Software FX (Addition of the 3 “Echo”, “Reverb” and “Phaser” effects which did not work …)
36: Loop On / Off
37: Loop 1/2
38: Loop x2

But couldn’t find how to assign the toggle effects with the button:
22 - Fx On / Off
Nor the buttons:
19: Beats Multiply
20: FX Wet / Dry Knob
And the same for everything relating to the complete management of the PAD:
35 - Performance Pads
As well as the key:
27 - Shift
Neither the display of:
6 - Master Ouptut LEDs

This is roughly where I am to date with this Numark Platinum FX controller for its operation with Mixxx.

Unfortunately at the moment I had to give up mixing due to health problems preventing me from using the computer, all of this is therefore (temporarily I hope) abandoned and pending …

Sorry if my English is not perfect, not being bilingual, I translate with Google Translation :wink:

Hi @WumaSoundMix,
Don’t worry about your English, mine is bad and I also use to the translator frequently. We could obviously use French mutually but so that everyone can follow it is better to make the effort to stay on English!

I am interested in having access to your mapping. I would try to run it on the pro fx.

Yesterday I looked at the code (mapping) which had been wrote for pro 3. Firt of all, the code seems very well done, very clear and very well documented. At the time, there was mixtrack pro 3 and mixtrack 3 (and platinium). The mapping for pro 3 and 3 is the same. It takes into account the differences of the both controllers. As it could be the case between the platinium fx and the pro fx.

So I think it’s realya good things to start either from the platinum or from the pro 3. And modify for what does not work.

Anyway, from what I understand on the platinum / pro 3 there was a special code generated when activating a pad mode (Cue, Loop, Sampler).

For the FX, the pad mode does not change the code of the pad “n”. In my opinion, it will be necessary to check which mode is activated before activating the pad function.

I have tried observing what Serato does when changing pad modes and I think it does this. So, If anyone has an idea of ​​how to implement this, don’t hesitate to give it to us …

Thank you all the contributors.