How to overwrite factory mapping for X1 mk3 ?

Jörn

I can't overwrite the factory mapping for my X1 mk3. I wanted to set the hot cues in a different way. I can't find a way to delete the factory settings! How can I do this? I'm using Version 3.11.1 17.

Thanks for your reply!

Sûlherokhh

https://community.native-instruments.com/discussion/comment/180692#Comment_180692

You need to add a 'modifier' assignment without factory override to the shift button (type: button, mode: hold, value: 1. This is to assign a custom shift layer without blocking the native shift function.

Then add the hotcue type 1-8 assignments to the numbered buttons with the modifier condition 'modifier #X = 0'.

Then add the hotcue type 1-8 delete assignments to the numbered buttons with the modifier condition 'modifier #X = 1'.

Then add OUT assignments in the same way to get visual feedback. You can add a second modifer condition for the different hotcue types to get different colours, making the LED output assignment list about 4 times as long as the input list.

Sûlherokhh

You can customize the shift layer for the number/nudge buttons. What are your settings?

If you only override the not-shift layer the leds of all buttons that have a shift layer resets to factory led. Make sure that you make your own overmapping shift layer with the modifier assignment to your shift button and then have all your custom functions use this custom layer with the modifier condition (modifier X = 0 / 1 for shift) AND have your LED assignments ALSO use the modifier condition.

Sûlherokhh

You can't delete them, only map different functions to the control elements and make a checkmark in the checkbox that says 'override factory mapping', which will prevent Traktor from engaging the factory mapping for the element.

Have a look at the mapping file for the x1. It's empty. All factory assignments are internal (using qml). But you can add your custom assignments to the empty list (to override the original).

Jörn

Thanks for your reply, I know this. But the invisible factory settings prevent me from mapping as I want it. I want to use all 8 Arrow/Hotcues/Nodge Buttons as Hotcues and I want to delete them with Shift+Hotcue Button. I don't get this…

Sûlherokhh

https://community.native-instruments.com/discussion/comment/180692#Comment_180692

You need to add a 'modifier' assignment without factory override to the shift button (type: button, mode: hold, value: 1. This is to assign a custom shift layer without blocking the native shift function.

Then add the hotcue type 1-8 assignments to the numbered buttons with the modifier condition 'modifier #X = 0'.

Then add the hotcue type 1-8 delete assignments to the numbered buttons with the modifier condition 'modifier #X = 1'.

Then add OUT assignments in the same way to get visual feedback. You can add a second modifer condition for the different hotcue types to get different colours, making the LED output assignment list about 4 times as long as the input list.

Jörn

Hey mate, thanks a lot! I will try this tomorrow!

I just wanted to ask you if there could be another solution…

I don't need the "estrafunctions" that show up, when I push the shift button. Is there a way to delete this function?

Sûlherokhh

1. another solution to the hotcues?
2. what extra functions? Everything related to the 8 hotcue buttons on each side will be overridden, including the shifted functions. Or do you mean shift+ (play, sync, browse/loop encoders, FX assign).

Jörn

When I push/hold Shift, the whole FX Buttons and knobs switch into a different mode… I don’t know what kind of functions these are but the Colours of the buttons are changing, and the text displays show something else. In this moment all hot cues that are active lose their led colour. When I release the button the hotcue leds stay off. That absolutely makes no sense for me…

Sûlherokhh

You can customize the shift layer for the number/nudge buttons. What are your settings?

If you only override the not-shift layer the leds of all buttons that have a shift layer resets to factory led. Make sure that you make your own overmapping shift layer with the modifier assignment to your shift button and then have all your custom functions use this custom layer with the modifier condition (modifier X = 0 / 1 for shift) AND have your LED assignments ALSO use the modifier condition.

Jörn

Hey Sûlherokhh,

I made everything like you described here:

You need to add a 'modifier' assignment without factory override to the shift button (type: button, mode: hold, value: 1. This is to assign a custom shift layer without blocking the native shift function.

Then add the hotcue type 1-8 assignments to the numbered buttons with the modifier condition 'modifier #X = 0'.

Then add the hotcue type 1-8 delete assignments to the numbered buttons with the modifier condition 'modifier #X = 1'.

Then add OUT assignments in the same way to get visual feedback. You can add a second modifer condition for the different hotcue types to get different colours, making the LED output assignment list about 4 times as long as the input list.

It seems that the Hotcue, LED and delete function is working…

But now there is still a problem with the LEDs. They should be absolutely off, when there is no active Hotcue but they are still showing a little bit off light even if there is no Hotcue. As long as I'm still holding Shift after deleting the hot cue the button led is of but when I release the shift button the LED lights up a bit. Is there still a not overwritten function active? How can I turn this off when I cannot see any of these active Mappings?! Thanks in advance!!!

Sûlherokhh

Overmapping will only provide dimmed or full brightness. There is no OFF state you can trigger. If you leave out the condition M1=0 from the OUT assignments, you will have dimmed brightness even when holding shift, so that there is no difference between SHIFT or NOT SHIFT layers for the LED's. But you can't turn the LED off across the board without having the factory LED assignments take over again by being not overwritten.

Sorry to say…

The only working solution is to dip into the qml code that provides the factory mapping and adjust it accordingly. There is a rather quick solution, that will let you have no control over the colours used, and a longer more difficult solution that lets you pick the colours, either a fixed colour or a colour depending on the cue type. Both will have zero LED output when no hotcue is defined at all.