i have multiple Maschine Jam midi controllers which are highly configurable (best midi controller in my view)
what are the best workflow methods for MMV for use with midi controllers??
i havent used this software often enough to work out the best workflows, so that if i have an idea and only wish to pipe in the assetts video feeds/jpegs/3d models etc etc,
currently the aspect of working with a midi controller would have me constantly mapping &remapping parameters
which is not ideal when restarting a project
is there any method, that can automap a module that is focussed, so that a midi-controller will dynamically automap 8 encoders/touchstrips & buttons to a focussed module??
is there keyboard-shortcut that will cycle through modules so that it becomes focussed?
also what are the efficient workflows that users are implementing to get up and running quickly?
Work flows?? Auto mapping of midi parameters per module?
Re: Work flows?? Auto mapping of midi parameters per module?
I’m not sure I understand. Generally, you set up MIDI with the MIDI Learn function. Have you found that yet?
Re: Work flows?? Auto mapping of midi parameters per module?
I don't really use MIDI preferring OSC however, I can think of a couple of workflows that you could use. They're not auto-mapping of parameters - Magic doesn't do that (yet), more a library of pre-configured nodes. The first is to have a sort of library project that contains pre-midi-configured nodes either by using inside the Post Processing node or copy and pasting to scenes. The second workflow is to apply midi configs to globals then use those clobals in your nodes. In each case you import the library or the globals when starting a new project.
Re: Work flows?? Auto mapping of midi parameters per module?
@magic
yes i have found the midi-learn, very useful, but would become cumbersome as you choose to change through the modules
the idea of automapping, i guess is a feature request
essentially the idea behind it, is based upon a single focussed module
which would have x amount of parameters based on the common actions per module
so in the case of a module having 8 main parameters assigned to cc 1-8 (user defined)
the moment another module is focussed, cc 1-8 are automatically reassigned to the focussed module, and their respective parameters
this does away with the requirement to constantly midi learn for every single module
this type of dynamic remapping is what i use with VST's in reaper, which i would envisage as being very useful in workflow/manual manipulation
heres an example of the remapping VST script in Reaper, for which i have 64 assignable parameter slots
https://www.youtube.com/watch?v=nWoXs3-8WuY
yes i have found the midi-learn, very useful, but would become cumbersome as you choose to change through the modules
the idea of automapping, i guess is a feature request
essentially the idea behind it, is based upon a single focussed module
which would have x amount of parameters based on the common actions per module
so in the case of a module having 8 main parameters assigned to cc 1-8 (user defined)
the moment another module is focussed, cc 1-8 are automatically reassigned to the focussed module, and their respective parameters
this does away with the requirement to constantly midi learn for every single module
this type of dynamic remapping is what i use with VST's in reaper, which i would envisage as being very useful in workflow/manual manipulation
heres an example of the remapping VST script in Reaper, for which i have 64 assignable parameter slots
https://www.youtube.com/watch?v=nWoXs3-8WuY
Re: Work flows?? Auto mapping of midi parameters per module?
with respect to the video above
imagine a single rotary encoder
and holding(or toggling) 1 of 64 buttons as a modifier + encoder movement, like that on a APC64 or a maschine Jam or a simple maschine mk1/2/3 or similar
one could envisage quick manipulation or quick selection of modules *shrugs (just some added thoughts)
imagine a single rotary encoder
and holding(or toggling) 1 of 64 buttons as a modifier + encoder movement, like that on a APC64 or a maschine Jam or a simple maschine mk1/2/3 or similar
one could envisage quick manipulation or quick selection of modules *shrugs (just some added thoughts)