Loop Move issue

[Laserbeam]

I would like to map the loop move function to my xone 4D. I used this news from djtt as a helper: http://djtechtools.com/2014/01/05/lo...p-move-macros/
However, as I am not using an X1 M1 but a Xone 4D, I would like to emulate the loop move from the mk2 with the shift button hold to move the loop. Now here is my mapping:

Loop Set: Encoder Push (Button Hold)
Loop Size Selector: Encoder Relative
Mode Selector (X1 Shift function): Button Hold of a Midi-Button
Move: Encoder Rotate

So far so good, I can simply map the loop move on a different encoder than the loop size selector. If I want to use the same encoder though, I extend or shorten the loop size while moving the loop (from 1/32 to 32 beat loop). How can I deactivate the loop size selector while I am holding the shift button midi-button?

cheers

[Stewe]

Ean made that tutorial using his X1's but the encoders on your 4D are not sending out the same type of message I believe.

Can you please check what midi note/CC is sent out from encoders? If I'm correct, those encoders are sending out two different CC events depending of both directions and therefor you'll need a different approach. X1 in default mode is using only one CC but the mode is toggling trough MIDI velocity values (3Fh or 7Fh)

[Laserbeam]

Ean made that tutorial using his X1's but the encoders on your 4D are not sending out the same type of message I believe.

Can you please check what midi note/CC is sent out from encoders? If I'm correct, those encoders are sending out two different CC events depending of both directions and therefor you'll need a different approach. X1 in default mode is using only one CC but the mode is toggling trough MIDI velocity values (3Fh or 7Fh)

The Encoder I want to Loop Deck B for example (Encoder Number 8, out right) sends CH16.CC.043, but the CC event is the same, no matter which direction I turn it.

[Stewe]

The Encoder I want to Loop Deck B for example (Encoder Number 8, out right) sends CH16.CC.043, but the CC event is the same, no matter which direction I turn it.

Interesting, they seem to have different encoder types on 2D's then. Thanks for clarifying this.

In that case all you need to create is one modifier button that you're gonna use as a Shift button.

Add In > Modifier 1 (could be any of 8 Modifiers)
type=button
mode=hold
value=1

You can check little modifier slots (1-8) in the Controller Manager. If you set everything properly your M1 slot will display value of "1" each time you hold the shift mod and going back to value of "0" each time you let go of the button.

With modifier button all set up you will have to go trough all loop/move/size commands and add corresponding modifier states at the modifier conditional slots (there are only 2 slots available per command)

In this scenario...
Loop Size equals to M1=0
Loop Move equals to M1=1

[Laserbeam]

Thanks that modifier at 0 was my issue, now everything works out fine

[Stewe]

Glad to help!
Cheers,