How to map the center coder of the X1 to the deck in focus?

[Jerry Bears]

Hi all,

I'm learning to map, and I'm wondering how to map the center encoder of the X1 to the deck in focus?

For example, I want to use the center encoder as a "loop move" macro, to move the loop that I just created with the main loop knob on the x1 for a particular deck? Thanks

[Stewe]

Add In > Layout > Deck Focus Selector
type of controller: Encoder
Interaction mode: Relative

rotary sensitivity = 100%
rotary acceleration = 0%

Check the "Override Factory Mapping" if you're editing native map.

Enjoy

[Jerry Bears]

Add In > Layout > Deck Focus Selector
type of controller: Encoder
Interaction mode: Relative

rotary sensitivity = 100%
rotary acceleration = 0%

Check the "Override Factory Mapping" if you're editing native map.

Enjoy

Hm, I'm having trouble getting this to work.

With that mapping in controller manager tied to my X1, I:
- Press the left loop button to make a loop and I set it to my desired size
- I go to move the center browse encoder, which I want to have move that loop that was just made, but nothing happens.
- I've tried setting a "modifier" of Cue/Loopmode>Device Target, but that just makes the encoder act as a browser encoder still.
Not sure what I'm missing.


Another question, I've tried to read up how to assign the SHIFT key to control an alternate button press (just like the unit does on default,) but I'm a little confused on how to do that.

Thanks!

[Stewe]

I can see your point now, thanks for input!



In the native mapping Shift button acts like a hold button type of the modifier so if you overwrite that mod with some new modifier command than all your pre mapped Shift+ functionality will be lost because the old modifier from default mapping will be replaced with the new one. This automatically means that you would need to map every command from your shift layer (del cue, fx assign, loop etc)

Step 1: Add new modifier and midi learn it to the Shift button

Add in > Modifier 1 / type=button / mode=hold / value=1

Now you have the Shift button overwritten with new modifier. To make sure it works, look in the little modifier state slots in the Controller Manager while holding down the button. The value of your mapped modifier should appear in corresponding slot and become active for the time the Shift button is pressed down because we set the interaction mode to hold.

M=1 should be displayed in first slot


Step 2: Map Deck Focus functionality

Ideally, I would use Shift+Encoder to select loop move target. You can do it by mapping the entry from my previous post but this time you need to make a modifier assignment because a deck should be selected only for the time the Shift button is held. I don't have X1 to test it and say for sure, but In theory you could also map the Displays to show which deck is in the focus if you know what midi velocity and channel is used for all characters.

Add In > Layout > Deck Focus Selector
add a condition of the pressed button state
type of controller: Encoder
Interaction mode: Relative

rotary sensitivity = 100%
rotary acceleration = 0%

Step 3: Creating Loop Move Encoder with three command macro

Add In > Deck common > Move > Size Selector
condition: M1=0
type=button
interaction=direct
Value=Loop (or whatever direct value you wish to use)

Add In > Deck common > Move > Mode Selector
condition: M1=0
type=button
interaction=direct
Value=Loop (because you want to move entire loop)

Add In > Deck common > Move > Move
condition: M1=0
type=encoder
interaction=relative
encoder mode=try both 3Fh and 7Fh (one will work for your X1 encoders)
sensitivity=100% (or less)


Note that modifier condition slots are two per one command. This means that you could use the second one to determine the Loop state modifier to move while the loops are active and still be able to browse tracks if out of the loop