midi controller map question in MUX
-
- KVRist
- 32 posts since 16 Dec, 2014
It seems that, no matter what I do, the midi mappings that I assign in my synths always end up in the Modular Area level, and not in my Module's map list. This means that the module does not respond to midi CC data sent from another module. I have to manually make the mapping from the module's list, instead of being able to use the shortcut knob above the plugin window. Is there a way around this? Other than putting the synth in another mux and sending my midi in there... that doesn't feel clean
-
- KVRAF
- 13865 posts since 24 Jun, 2008 from Europe
Indeed when right-clicking a module parameter and do "Map MIDI Controller" the mapping will be stored in the top most module that can take MIDI focus. For MUX VST that is the MUX module itself, as you saw. Otherwise your mapping may not be effective as possible the MIDI events won't get thru to that specific module, depending on the patch structure. Solution: Use the module's "Map MIDI Controller" or "Edit MIDI Controller Map" functions to ensure controller mapping for that specific module. Please also see http://www.mutools.com/info/docs/mux/us ... llers.html
-
- KVRAF
- 3162 posts since 28 Mar, 2008 from a Galaxy S7 far far away
Just thinking about mapping, would it be possible for mulab to auto assign certain controls as soon as a device is plugged in? Just to make things easier getting setup.
You could auto assign things like filter, amp, envelopes, as a starter. Maybe even transport?
So switching between presets and VST's always keep the setup as is, at least for instruments. If a CC isn't present it's ignored.
What do you think?
You could auto assign things like filter, amp, envelopes, as a starter. Maybe even transport?
So switching between presets and VST's always keep the setup as is, at least for instruments. If a CC isn't present it's ignored.
What do you think?
-
- KVRAF
- 3207 posts since 17 Apr, 2010 from Slovenia
I'd be worried that it will step on just as many people's toes... automapping is a dangerous thing. Would be cool if you could store and apply mapping presets, that's a different story. But then... preset to what? It's a modular system and everything could be different... so... I'd go "never mind" on all of this! 
-
- KVRAF
- 3162 posts since 28 Mar, 2008 from a Galaxy S7 far far away
I agree, but as an option to get started, it could be helpful when loading a new VSTi to have the basics catered for without needing to manually setup when just jamming?
In the two years of having a license, I've not really had the chance to get really stuck in to figure stuff out. My time is limited due to family. I did request ages ago though that Presets store mappings, to this day I still don't know if it can be done!
But after sorting a lot of things out lately, I plan on making more time for music as I miss it. Maybe Mulab 7 will add some sort of mapping saves?
I realise that it's a modular system but CC74 is and always has been used for filter cutoff. So it wouldn't matter what the preset was, if it contained a filter your detected hardware could be auto-detected and assign a control to this parameter. Same for Res, Amp Level, Pan, Envelope's, etc, depending on how many controls your hardware has.
I don't know if it's feasible but I'd love to be able to connect my ESX1 and the knobs match the parameters for either VST or MuX presets where applicable. Can it be done? Is it possible Mulab could detect hardware in this way? Or maybe detection like this isn't needed as long as a MIDI device is connected, Mulab would just detect an incoming CC74 and adjust filter on the relevant software device used?
Perhaps this is just wishful thinking? I have a Novation Impulse, but would prefer to use something smaller. I also have a MiniNova and the same principal I described would make using VST's sooo much easier. It would also make Mulab stand out as I bet no other DAW does that? And, after all, isn't ease of use Mulab's ethos?
In the two years of having a license, I've not really had the chance to get really stuck in to figure stuff out. My time is limited due to family. I did request ages ago though that Presets store mappings, to this day I still don't know if it can be done!
But after sorting a lot of things out lately, I plan on making more time for music as I miss it. Maybe Mulab 7 will add some sort of mapping saves?
I realise that it's a modular system but CC74 is and always has been used for filter cutoff. So it wouldn't matter what the preset was, if it contained a filter your detected hardware could be auto-detected and assign a control to this parameter. Same for Res, Amp Level, Pan, Envelope's, etc, depending on how many controls your hardware has.
I don't know if it's feasible but I'd love to be able to connect my ESX1 and the knobs match the parameters for either VST or MuX presets where applicable. Can it be done? Is it possible Mulab could detect hardware in this way? Or maybe detection like this isn't needed as long as a MIDI device is connected, Mulab would just detect an incoming CC74 and adjust filter on the relevant software device used?
Perhaps this is just wishful thinking? I have a Novation Impulse, but would prefer to use something smaller. I also have a MiniNova and the same principal I described would make using VST's sooo much easier. It would also make Mulab stand out as I bet no other DAW does that? And, after all, isn't ease of use Mulab's ethos?
-
- KVRist
- Topic Starter
- 32 posts since 16 Dec, 2014
Is there any way you could make this behavior optional? It really slows down my workflow to not be able to use the shortcut knob to map directly to midi plugins like MidiShaper and LFOTool on the same level. Especially when I use a synth with a very long list of parameters like z3ta+. Thank you for your consideration.mutools wrote:Indeed when right-clicking a module parameter and do "Map MIDI Controller" the mapping will be stored in the top most module that can take MIDI focus. For MUX VST that is the MUX module itself, as you saw. Otherwise your mapping may not be effective as possible the MIDI events won't get thru to that specific module, depending on the patch structure. Solution: Use the module's "Map MIDI Controller" or "Edit MIDI Controller Map" functions to ensure controller mapping for that specific module. Please also see http://www.mutools.com/info/docs/mux/us ... llers.html
OR, otherwise, maybe a way to quickly copy paste midi mappings from one module to another? or something, anything but having to dig through the parameter list please
Or you could take the fl patcher route and allow us to add a blue input specifically for a certain parameter?
midishaper is a free plugin you can try it to see what I mean, I'm sure you will feel my suffering.
-
- KVRAF
- 13865 posts since 24 Jun, 2008 from Europe
You mean the 'focused parameter' knob at the top of the VST editor?anisotonic wrote:Is there any way you could make this behavior optional? It really slows down my workflow to not be able to use the shortcut knob
If you tweak a VST parameter it becomes the focused parameter and then when doing "Map MIDI Controller" via the plugin's context menu (not the knob's context menu) then the last focused parameter is pre-selected so you don't need to choose it from the (long) VST parameter list. Maybe i'm missing something?to map directly to midi plugins like MidiShaper and LFOTool on the same level. Especially when I use a synth with a very long list of parameters like z3ta+.
-
- KVRist
- Topic Starter
- 32 posts since 16 Dec, 2014
Oh. You're right, the parameter is selected in the other menu. My bad, I had not noticed. I thought you had to use the shortcut knob's menu.
I get it now: the point of the shortcut knob's menu is to send the mapping to the top level where you're sure that external midi coming into MUX will work. makes sense yeah.
Well then... I guess that's it
Oh wait. There's something else I'm wondering. When I use the internal LFO, I send it to a parameter event generator, which allows me to use the knob in the PEG to control the parameter's default position while it's being modulated. Is there such a knob I could use between a Midi lfo plugin and my parameter? because it seems I can't use the PEG for that. Something like the Offset in the modulation mapper but with a blue output. Thanks again
Oh. I was supposed to use the Automation Range for that. Silly me, I was looking everywhere inside MUX when what I was looking for was right in my face in the mapping menu all along.
And! not only can I set the automation range in mux, but there's even a Center knob I was looking for in midishaper
I get it now: the point of the shortcut knob's menu is to send the mapping to the top level where you're sure that external midi coming into MUX will work. makes sense yeah.
Well then... I guess that's it
Oh wait. There's something else I'm wondering. When I use the internal LFO, I send it to a parameter event generator, which allows me to use the knob in the PEG to control the parameter's default position while it's being modulated. Is there such a knob I could use between a Midi lfo plugin and my parameter? because it seems I can't use the PEG for that. Something like the Offset in the modulation mapper but with a blue output. Thanks again
Oh. I was supposed to use the Automation Range for that. Silly me, I was looking everywhere inside MUX when what I was looking for was right in my face in the mapping menu all along.
And! not only can I set the automation range in mux, but there's even a Center knob I was looking for in midishaper
Last edited by anisotonic on Sat Jul 18, 2015 6:08 am, edited 1 time in total.
-
- KVRist
- Topic Starter
- 32 posts since 16 Dec, 2014
Therefore this thread is now a feature suggestion: button to go directly to the module's Edit Midi Controller Map in the header, and ability to change Min and Max values directly from the Midi Controller Map window.