Hi!
Could you explain how to launch clips with the function keys (F1 - F12)?
I can't figure it out!
Thanks so much
Live Matrix Map to Note Action
-
- KVRAF
- 13850 posts since 24 Jun, 2008 from Europe
You can use the Virtual MIDI Keyboard for that.
Set it to the function keys and make sure the composer has MIDI focus, then you'll get what you want.
Why does the composer need MIDI focus?
Because it's the same as when you would want to trigger Note Actions via MIDI.
See these doc pages:
https://www.mutools.com/info/M10/docs/m ... n-map.html
https://www.mutools.com/info/M10/docs/m ... board.html
Note that starting with MuLab 10.2.7 the Virtual MIDI Keyboard can be set to a specific channel, and if you also setup the Project MIDI Input Channel Target for that Virtual MIDI Keyboard channel to that composer module, then these function keys will always send MIDI to the composer. That way it is independent of the MIDI Input Target Module, which typically changes while clicking around on racks, plugin editors, etc, ad MIDI Input typically goes to what you're working with on screen, that's the "Automatic MIDI Input Focus".
Hope you see the picture.
Does this answer your question?
Set it to the function keys and make sure the composer has MIDI focus, then you'll get what you want.
Why does the composer need MIDI focus?
Because it's the same as when you would want to trigger Note Actions via MIDI.
See these doc pages:
https://www.mutools.com/info/M10/docs/m ... n-map.html
https://www.mutools.com/info/M10/docs/m ... board.html
Note that starting with MuLab 10.2.7 the Virtual MIDI Keyboard can be set to a specific channel, and if you also setup the Project MIDI Input Channel Target for that Virtual MIDI Keyboard channel to that composer module, then these function keys will always send MIDI to the composer. That way it is independent of the MIDI Input Target Module, which typically changes while clicking around on racks, plugin editors, etc, ad MIDI Input typically goes to what you're working with on screen, that's the "Automatic MIDI Input Focus".
Hope you see the picture.
Does this answer your question?
-
- KVRist
- Topic Starter
- 68 posts since 5 Mar, 2020
well, by now it works only if I click the notes on the Virtual MIDI Keyboard (minimized on the controlbar) or if I open the Virtual MIDI Keyboard
otherwise, the function keys doesn't work
otherwise, the function keys doesn't work
-
- KVRAF
- 13850 posts since 24 Jun, 2008 from Europe
The Virtual MIDI Keyboard needs to be active indeed.
But you can keep it minimised in the window dock at the bottom of the project editor.
Maybe an extra option could be added to keep the Virtual Keyboard keys active all the time.
But you can keep it minimised in the window dock at the bottom of the project editor.
Maybe an extra option could be added to keep the Virtual Keyboard keys active all the time.
-
- KVRist
- Topic Starter
- 68 posts since 5 Mar, 2020
Yesss, it works !MuTools wrote: Thu Mar 26, 2026 11:17 am The Virtual MIDI Keyboard needs to be active indeed.
But you can keep it minimised in the window dock at the bottom of the project editor.
Maybe an extra option could be added to keep the Virtual Keyboard keys active all the time.
I think it could be a good idea to keep it active ...
-
- KVRAF
- 7411 posts since 8 Feb, 2003 from London, UK
Even better if there was a visible button to keep it active (i.e. not under a menu).
-
- KVRAF
- 13850 posts since 24 Jun, 2008 from Europe
It won't be a single Always Active option ( forthcoming in M10.2.8 ), but definable per key row, so some VMK keys can be Always Active, others not.
If you want to have some toggle option for the VMK being active or not you can dock the VMK window. If docked it's active, when the VMK is closed only any 'Always Active' VMK keys will remain active. So that's an already existing implicit visual button.
I'm careful with adding buttons for each and every function as that bloats the GUI.
If you want to have some toggle option for the VMK being active or not you can dock the VMK window. If docked it's active, when the VMK is closed only any 'Always Active' VMK keys will remain active. So that's an already existing implicit visual button.
I'm careful with adding buttons for each and every function as that bloats the GUI.