I'm demoing MuLab, its modular section in specific.
Each time I assign a certain midi controller to a specific parameter I loose the connection with the previous one that I had just set.
Mapping still reports the right assignment but the Midi controller just doesn't move it.
What should I check ?
thank you
midi control of parameters
-
- KVRist
- 236 posts since 1 May, 2009 from Italy
-
- KVRAF
- 7412 posts since 8 Feb, 2003 from London, UK
Are you trying to control multiple modules' parameters at the same time? There's a few ways to do that.
MIDI input follows focus by default, so you should be able to click between modules and use the mapping you set for that module (i.e. it's not lost at all).
MIDI input follows focus by default, so you should be able to click between modules and use the mapping you set for that module (i.e. it's not lost at all).
-
- KVRist
- Topic Starter
- 236 posts since 1 May, 2009 from Italy
I think there's something going wrong on my configuration.
This is what it happens:
right click on "rack A" fader > map midi controller > midi focus > hit midi cc 20 on channel 7 = the midi is received and the fader moves.
right click on "rack B" fader > map midi controller > midi focus > hit midi cc 21 on channel 7 = the midi is received and the fader moves.
at this point, if I move the midi controller of rack A fader, the fader doesn't react anymore.
Settings are still stored correctly though
This is what it happens:
right click on "rack A" fader > map midi controller > midi focus > hit midi cc 20 on channel 7 = the midi is received and the fader moves.
right click on "rack B" fader > map midi controller > midi focus > hit midi cc 21 on channel 7 = the midi is received and the fader moves.
at this point, if I move the midi controller of rack A fader, the fader doesn't react anymore.
Settings are still stored correctly though
-
- KVRAF
- 7412 posts since 8 Feb, 2003 from London, UK
No, that's what I said: MIDI input follows focus by default. You changed focus from Rack A to Rack B, so MIDI input is now on the focused rack.
-
- KVRist
- Topic Starter
- 236 posts since 1 May, 2009 from Italy
So it means you cancontrol one parameter at the time ?
Just that which is in the enlighted module ?
Just that which is in the enlighted module ?
-
- KVRAF
- 13865 posts since 24 Jun, 2008 from Europe
You can also map MIDI controllers on project level so they work 'globally', independent from the focused module: Project menu -> Edit Project MIDI Input Controller Map. It's a bit less easy to setup though as you have to manually select the target module/parameter. I've taken note on the wishlist to smooth this workflow so it becomes equally easy as doing it per focused module.
-
- KVRist
- Topic Starter
- 236 posts since 1 May, 2009 from Italy
yes, it would be better and more intuitive to let the mappings that you assign being copied in the MIDI Input Controller Map.
But the map is a good thing anyway.
It would also be useful to use it a container to show the full summary of all midi assignments to keep a good track of what's been setup ( in an app I'm using they call it Midi bindings).
But the map is a good thing anyway.
It would also be useful to use it a container to show the full summary of all midi assignments to keep a good track of what's been setup ( in an app I'm using they call it Midi bindings).