|
Post by rickywander on Jul 25, 2019 12:04:44 GMT -5
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. I need some more Action buttons :-) Attachments:
|
|
|
Post by Stray on Jul 26, 2019 10:05:33 GMT -5
You can do that. For example: [FXA-UP] "BIND A"/PLAY > ; XMODE 1
|
|
|
Post by rickywander on Jul 26, 2019 12:14:02 GMT -5
Thanks a lot Stray. It was not easy for me to realize that I could trigger X-Modes from within X-Clips.
Next time I will make more experimentation regardless my limits before asking.
|
|
|
Post by kirkwoodwest on Jan 21, 2020 15:49:04 GMT -5
|
|
|
Post by rickywander on Jan 22, 2020 9:00:32 GMT -5
I am not shure to understande your question but anyway, Shift funcionality is a momentary X-Actions modifier while X-Modes is a static one. You can have as many as you want. And we can trigger X-Modes and X-Shift from OSC too.
|
|
|
Post by Stray on Jan 22, 2020 17:14:48 GMT -5
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.
|
|
|
Post by kirkwoodwest on Jan 23, 2020 13:59:50 GMT -5
I am not shure to understande your question but anyway, Shift funcionality is a momentary X-Actions modifier while X-Modes is a static one. You can have as many as you want. And we can trigger X-Modes and X-Shift from OSC too. yup you understood correctly! thanks for the clarification! @stray thanks for the tip. ill do some mods 🙏🏻
|
|
|
Post by jjenron on Feb 9, 2020 23:53:42 GMT -5
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 Stray on Feb 10, 2020 16:52:57 GMT -5
That wouldn't work since ClyphX Pro doesn't handle assigning a macro to a macro to a macro. You'd need to specify the actual action list (not a macro) for $b1_mode_1$ and $b2_mode_1$.
|
|
|
Post by jjenron on Feb 10, 2020 19:44:38 GMT -5
Thanks stray!
|
|
|
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.
|
|
|
Post by Stray on Feb 13, 2020 6:15:30 GMT -5
Please follow the debugging procedure covered in the Troubleshooting section. While debugging, trigger the xmode 2 action and then attach the resulting debug log here.
|
|
|
Post by johnsvensson on Feb 15, 2020 8:57:06 GMT -5
Please follow the debugging procedure covered in the Troubleshooting section. While debugging, trigger the xmode 2 action and then attach the resulting debug log here. Thanks Stray, here's the debug log file. Hope I did it right. Attachments:Debug Log.txt (37.92 KB)
|
|
|
Post by Stray on Feb 15, 2020 11:08:35 GMT -5
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.
|
|
|
Post by johnsvensson on Feb 18, 2020 13:18:07 GMT -5
Thanks again Stray, now everything is working as intended! Good thing to clarify in the introduction posts!
|
|