Page 1 of 1
Make EVERYTHING on screen MIDI mappable.
Posted: Tue Jul 29, 2014 12:44 am
by akm
I'd like to have the ability to make an ultimate workstation where I can map EVERYTHING to MIDI controllers, including loop start/end positions, screen layouts, input-output routing menus, adding-deleting tracks, just everything that can be clicked with a mouse or keyboard commands, just as much as possible. There are lots of things in the clips editing windows that could be mapped to MIDI as well.
Re: Make EVERYTHING on screen MIDI mappable.
Posted: Thu Jul 31, 2014 8:54 am
by aubford
I don't see why there need to be limitations. EVERYTHING should be mappable duh!
Re: Make EVERYTHING on screen MIDI mappable.
Posted: Thu Jul 31, 2014 8:54 am
by aubford
I don't see why there need to be limitations. EVERYTHING should be mappable duh!
Re: Make EVERYTHING on screen MIDI mappable.
Posted: Thu Jul 31, 2014 9:43 am
by JoshG567
I've learned to map previously "unmappable" things by writing M4L devices to do it. Once you have a basic idea of the LOM it isn't that hard to whip something up.
Re: Make EVERYTHING on screen MIDI mappable.
Posted: Fri Aug 01, 2014 4:08 pm
by akm
JoshG567 wrote:I've learned to map previously "unmappable" things by writing M4L devices to do it. Once you have a basic idea of the LOM it isn't that hard to whip something up.
Thank you for the reply, I'll ask more about it in the M4L forum branch.
viewtopic.php?f=35&t=205656
Re: Make EVERYTHING on screen MIDI mappable.
Posted: Fri Aug 01, 2014 4:37 pm
by JoshG567
What you can't do in a straightforward way with M4L you may be able to do with ClyphX X-Controls. Of the list of things you mention it sounds like the easiest way to add/delete tracks with MIDI controls. I've done the input routing stuff with M4L, as well as time sig changes, record quantize, undo/redo, maybe a few other things. Clip loop start/length are totally mappable - were you referring to something else in that regard?
Re: Make EVERYTHING on screen MIDI mappable.
Posted: Sun Oct 08, 2017 12:31 am
by akm
@JoshG567
Just saw the reply, thank you very much for the info.