I'm not sure that I follow what you're asking. In general though, the macros that you set up for use with XMODE can trigger any actions you want including BIND actions. Would that suit what you're looking to do here?
Unfortunately not because I use two buttons only for +12 bindings with this two XClips on a track named "BIND A" :
[FXA-UP] "BIND A"/PLAY > and [FXA-DOWN] "BIND A"/PLAY <
then if I have to use the BIND action included with an X-Mode button I would need +12 buttons (I suppose but quite shure).
The solution would be if I could recall an X-Mode within the same X-Clip from where I recall the bindings (although I suppose this is not possible).
The image i show here is for showing the project face and in particular the Max device I would like to cut. This Max device just turn a parameter in a play Xclip command since bindings only works with existing parameters.
im wanting to have multiple “shift butttons” like shift, ctrl and alt
You could do that by modifying the file included in that post to create a ctrl and alt action. The file is pretty well documented and the logic is pretty simple, so it should be straightforward to do it.
hi all! i would like to use this "mode functionality" to provide my launch control xl with extra layers. actually im using 8 buttons of my LCXL (assigned to x actions) to trigger 8 different macros, each one with a list of BINDs actions (one for each fader, button or knob in my LCXL) example: on my x-actions.txt ...BIND_SUBMASTER = CC, 15, 91, 0, 127, $tempmacro1$ BIND_DRFX = CC, 15, 92, 0, 127, $tempmacro2$
on my macros.txt ...$tempmacro1$ = BIND fader1 20/DEV(1) P1; BIND fader2 20/DEV(1) P2; BIND fader3 20/DEV(1) P3; $tempmacro2$ = BIND fader1 16/DEV(1) P1; BIND fader2 16/DEV(1) P2; BIND fader3 16/DEV(1) P3; etc.. i would like to use this functionality to duplicate de funcionality of my 8 buttons. is it possible? im trying this way, but it doesnt work: on x actions.txt: mode_1_button = CC, 15, 47, 0, 127, xmode 1 mode_2_button = CC, 15, 48, 0, 127, xmode 2 b1 = CC, 15, 91, 0, 127, $b1$ b2 = CC, 15, 92, 0, 127, $b2$ on macros.txt $b1_mode_1$ = $tempmacro1$ $b1_mode_2$ = solo $b1$ = $b1_mode_1$ $b2_mode_1$ = $tempmacro2$ $b2_mode_2$ = solo $b2$ = $b2_mode_1$
the "mode 2" works, but the mode 1 wich should trigger the macros that contains all the bindings dont
sorry if i wasnt clear and thanks in advance to all!
Post by johnsvensson on Feb 12, 2020 13:29:50 GMT -5
Hi everyone! Diving into this cool feature at the moment! Though I'm stuck at the last step; getting the mode-changing messages to actually change the macros.
In my Macros document I've defined: $pedal1_mode_1$ = tapbpm $pedal1_mode_2$ = srec on; play sel $pedal1$ = $pedal1_mode_1$
And in my X-OSC document I've defined: /main/pedaltap = xmode 1 /main/pedalrec = xmode 2
Anything obvious I'm missing? The footswitch I'm trying to change the behaviour of is controlling the tap function correctly, but nothing happens when I press the buttons to change the X-Mode in TouchOSC on my iPad. Other stuff in that TouchOSC layout is working correctly.
Thanks for posting the log. Sorry, I overlooked the fact that you previous reply conveyed the problem. Control and macro names need to be in the form of bx (where x is any whole number). So the naming scheme you're using wouldn't work. In X-Controls.txt, you should change pedal1 to b1 and in Macros.txt you should replace pedal1 with b1. Also, in Macros.txt, you should remove all the empty bx entries.
For the sake of other readers, I clarified the first post to point out the naming requirement.