Pioneer controller editor

[lauti]

Pioneer controller editor

Hi, I just got myself a Pioneer ddj sp-1.
I’m trying to map it to traktor, and I’m REALLY missing something that all NI controllers have: The controller editor, to be able to define the midi behaviour of the device itself.

I know the answer is probably no, but…is there something similar for pioneer? (in particular for the sp-1)

For example, I know that there is at least two templates for the sp-1 (the serato template, and the non-serato template) which you can switch, and it changes the behaviour of the device itself (buttons for deck 3 and 4, in non-serato mode, work as a whole secondlayer for the pads)

[astromech]

@lauti

Hi, I just got myself a Pioneer ddj sp-1.
I’m trying to map it to traktor, and I’m REALLY missing something that all NI controllers have: The controller editor, to be able to define the midi behaviour of the device itself.

I know the answer is probably no, but…is there something similar for pioneer? (in particular for the sp-1)

For example, I know that there is at least two templates for the sp-1 (the serato template, and the non-serato template) which you can switch, and it changes the behaviour of the device itself (buttons for deck 3 and 4, in non-serato mode, work as a whole secondlayer for the pads)

Does Traktor detect the controller as a device? You might just need to create a mapping yourself.

[lauti]

Does Traktor detect the controller as a device? You might just need to create a mapping yourself.

Yes. I am doing it.
The problem is not mapping in traktor, but actually, defining which midi notes does each button trigger.

Like, in controller editor, you can define what kind of midi signal each button sends.

I’d like to do that, since there’s some buttons that work as layers, which is annoying to me.

[Stewe]

Bome’s Midi Translator to the rescue