Tip: Triggering Action Lists via Keystrokes

[Stray]

ClyphX Pro includes a variety of X-Trigger types including X-Controls (MIDI controls), but many of its Actions would be useful to access directly from your keyboard. In this thread, we’ll look at ways of accomplishing that on Windows and OS X. In both cases, we’ll be using an external application that converts keystrokes to MIDI messages, which can then be used as X-Controls.

[Stray]

WINDOWS

First, download and install Midi-Gridy as well as loopMIDI. Then, set up Midi-Gridy how you like. Here’s how I’ve set it up:



Next, you'll define X-Controls in ClyphX Pro's X-Controls.txt file. Here's an example:
btn_1 = note, 1, 1, 0, 127, play >
btn_2 = note, 1, 2, 0, 127, jump >
btn_3 = note, 1, 3, 0, 127, clip loop >
btn_4 = note, 1, 4, 0, 127, clip loop *0.5
btn_5 = note, 1, 5, 0, 127, clip semi >
btn_6 = note, 1, 6, 0, 127, clip
btn_7 = note, 1, 7, 0, 127, play <
btn_8 = note, 1, 8, 0, 127, jump <
btn_9 = note, 1, 9, 0, 127, clip loop <
btn_10 = note, 1, 10, 0, 127, clip loop *2
btn_11 = note, 1, 11, 0, 127, clip semi <
btn_12 = note, 1, 12, 0, 127, clip notes
Finally, you’ll select a virtual MIDI port (such as loopMIDI Port 1) as the MIDI Out from Midi-Gridy. And you’ll select the same port (such as loopMIDI Port 1) as the Input for ClyphX Pro.

Keep in mind, you can also assign HotKeys in Midi-Gridy. In the above example, I’ve assigned the top row to F1–F6 and the bottom row to Shift+F1-F6.

To take it a step further, this layout actually mirrors the layout of the control setup on my nanoPAD. So now Midi-Gridy also functions as sort of an onscreen map of my nanoPAD too.

[Stray]

OS X

Download and install Kimidi, a utility provided by wiffbi. If you find this utility useful, please consider making a PayPal donation to wiffbi.

In short, Kimidi provides a variety of pre-defined keyboard shortcuts that send out pre-defined MIDI messages. You can see the MIDI messages that each shortcut sends here. All of these MIDI messages are sent on Channel 1.

Only the shortcuts that send notes are usable with ClyphX Pro. For example, Ctrl+A sends Note 0 and Ctrl+S sends Note 1, so both are usable. Ctrl+F and Ctrl+V send CCs, so neither are usable.

You’ll need to go through the implementation chart and choose which shortcuts you’d like to use. Then you’ll need to define the MIDI messages these shortcuts send in ClyphX Pro’s X-Controls.txt file along with which Action(s) they should trigger. As an example:
Ctrl_A = note 1, 0, 0, 127, metro
Ctrl_S = note 1, 1, 0, 127, play >
Ctrl_Alt_A = note, 1, 3, 0, 127, setstop
Lastly, you’ll need to select Kimidi Input as the Input for ClyphX Pro.

[ChainsawArt]

Stray, this feature alone speeds up Ableton workflow so much.
I wasn't a fan of the Mac/Kimidi restrictions, but was able to get it working very nicely with customized key commands in Bome's Midi Translator.

I know you have used Bome MTP extensively in the past, so I'm hoping you might have some insight on this:
How do I set up the keystrokes in Bome MTP so that when I press the specific key string down, I am sending the note "on" message and when I release the key string, I am sending a note "off".  It appears that this is possible with single keys, but is it possible with a string of keys? Example Ctrl_Shift_Up?  I would like to be able to assign note on and off commands in the X-Controls.txt file for easy toggling. 

Thanks!

[Stray]

I've not done any of that, but I would think that's possible. You'd just need to have your modifiers (like Shift) set the value of global variables. I would bet you could fine some examples if you searched around on the translator forum.

[jbone1313]

I simply map keystrokes to x-clips using Ableton's key mapping functionality. Works great.

[e45]

Apr 6, 2019 16:25:25 GMT -5 jbone1313 said:

I simply map keystrokes to x-clips using Ableton's key mapping functionality. Works great.

Me too.  Here're my mappings for an 8x8 clip grid across 8 channels with 4 returns.
Keyboards can do lots of special characters (I use https://www.howtotype.net), so the potential for keyboard mapping straight to x-clips goes far beyond qwerty.


-key----|-default------|-shift----------|-alt-------------| shift + alt-----|
1 to 8  | scene select | fader -infdB   | send \ 1 bar    | send ; 2 bars   |
q to i  | ch send devs | fade out 32    | <char-map>      | fade in 32      |
a to    | dev select   | play clip      | filter select   | re-trig clip    |
z to k  | stop & reset | filter reset   | SND0dB *not ch6*| fltr rst+SND0dB |
9 to =  | <char-map>   | <char-map>     |                 |                 |
o to ]  | ret send devs| return fade 16 |                 |                 |
l to \  | return select| send devs      | return init     |                 |

-char-|-key----------|-command----------------------
>     | SHIFT .      | stop for next
®     | ALT r        | stop clips
÷     | ALT /        | reload macros.txt
'     | '            | scene up
/     | /            | scene down
»     | SHIFT ALT \  | mono
œ     | ALT q        |*returns (all) init
∑     | ALT w        | show/hide x-clips
(     | SHIFT 9      |*A RETURN decay 95%/100%
†     | ALT t        | metronome toggle on/off
¥     | ALT y        | metronome focus
)     | SHIFT 0      | test clip (9S)
=     | =            | goto fades
§     | §            | goto channels & focmain
`     | `            | toggle filter / device
~     | SHIFT `      | toggle ch-send-device / device

[Stray]

Nice!

[erik]

the link to Midi-Gridy doesnt work. Any other way to download it ?
could not find it on Google.

[diggdugg]

One of my most-used Mac apps for Abelton has been Keyboard Maestro (not free...can't remember...maybe $20?)

I use with TouchOSC to have midi CC buttons (assigned to Midi Channel#, CC# at a certain CC Value) triggering series' of tasks.
Usually task number 1: "Type Command+F" (go to browser)
Task number 2: Type "Whatever Device"
Task number 3: "Simulate keystroke RETURN"

stuff like that

You can also use keyboard shortcuts, & when you run out of those, you can trigger by typing a series-of-keys.
I haven't gotten to that point but I've thought about, for instance, typing ",.,arp" to trigger the above steps with "Arpeggiator" being my "Whatever Device" etc.
So instead of a single keystroke, triggering would be done (in my personal setup) by typing ",.," then the first few letters of each browser item (& of course, create specific original names for devices...I use a LOT of Racks)

I even make tasks do things like "Click on (pixel coordinate)" which uses whatever window is on top, then "Simulate keystroke Down-Arrow" (however many times) [for instance I use this to open families of presets inside TAL Sampler, but of course everything has to stay in-order, & TAL Sampler window has to be the selected window on-top].
Then I also have midi assignments for TAL-Sampler's parameters....so I have a whole TAL-Sampler controller (basically browsing through presets) on my phone in a TouchOSC layout.

Brian Rivlin's youtube channel has a great video (or 2) about KM...that was my inspiration for this stuff.

[jaynyc]

I know this is an old thread. I am curious in 2023/2024-- is there a speed benefit (performance difference) between

Mapping Keyboard shortcuts within Live to launch XClips which contain a set of commands

vs

Using MidiGriddy to "send" MIDI with Macros.txt to execute the same set of commands

In Live 11, is one "faster" - ie: is there less delay with one method vs. the other?

thanks

[schlapbe]

Dec 16, 2023 20:18:01 GMT -5 jaynyc said:

I know this is an old thread. I am curious in 2023/2024-- is there a speed benefit (performance difference) between

Mapping Keyboard shortcuts within Live to launch XClips which contain a set of commands

vs

Using MidiGriddy to "send" MIDI with Macros.txt to execute the same set of commands

In Live 11, is one "faster" - ie: is there less delay with one method vs. the other?

thanks        

Hi!
I would say, in terms of "delay" there should be more or less the same.

However, a big difference is, that if you trigger XClips, the transport will ALWAYS start. 
Whereas with X-Controls it does not.

But regarding, the speed of execution, which type or purpose of CXP actions are you aiming for?

Best,
S

[jaynyc]

@schlappe that's a good point about the transport I didn't realize. Thank you for that. Anyway, I got X-controls.txt to work - and it does seem a slight bit faster.