when the gui of a vst plugin is opened,
then I also can choose the option menu (upper left button).
There I can choose <map midi controller> and e.g.
I can assign the modulation wheel to a parameter like <cut off>
or what ever the plug in offers.
But on the other hand I have an add. menu item
<Edit Focus midi controller map> where I hopped
all the mappings are listed, but this map is empty.
There I can add mappings with similar entries
as when using <map midi controller>. (But this does not work)
What is the difference, why one menu item for "single mapping"
and a second one for mapping in list form ?
again: mapping of midi controller
-
- KVRAF
- 13862 posts since 24 Jun, 2008 from Europe
There are currently two MIDI CC -> Plugin Parameter map modes:
Global and Focus.
Global = The mapping is alway active.
Focus = The mapping is only active when the respective plugin is focussed.
Of course having these 2 map modes makes things a bit more complex, but imagine you have a MIDI keyboard with only a couple of MIDI CC's.
Then when there would only be Global mode you would run out of free MIDI CC's very quick.
Atoh, when there would only be Focus mode, you could not create maps where multiple CC's control multiple plug parameters at the same time. The global mode is also good because you don't have to worry about focussing a certain plug.
---
In the future, there may come a third map mode "Type Focus".
This would be the same as Focus, but it's not especially the plugin itself that should be focussed, but the type of plugin.
Example: When you map CC 50 to Rack Volume with Type Focus, then this map will be active as soon as any rack is focussed. Focussing a rack and tweaking MIDI CC 50 will move the volume slider of that rack.
I'm aware that these different map modes makes things more complex to understand, especially when in the mood of making music. But they're technically very relevant.
Please let me know if you have any ideas to make this MIDI CC map system easier/better. Thanks.
Global and Focus.
Global = The mapping is alway active.
Focus = The mapping is only active when the respective plugin is focussed.
Of course having these 2 map modes makes things a bit more complex, but imagine you have a MIDI keyboard with only a couple of MIDI CC's.
Then when there would only be Global mode you would run out of free MIDI CC's very quick.
Atoh, when there would only be Focus mode, you could not create maps where multiple CC's control multiple plug parameters at the same time. The global mode is also good because you don't have to worry about focussing a certain plug.
---
In the future, there may come a third map mode "Type Focus".
This would be the same as Focus, but it's not especially the plugin itself that should be focussed, but the type of plugin.
Example: When you map CC 50 to Rack Volume with Type Focus, then this map will be active as soon as any rack is focussed. Focussing a rack and tweaking MIDI CC 50 will move the volume slider of that rack.
I'm aware that these different map modes makes things more complex to understand, especially when in the mood of making music. But they're technically very relevant.
Please let me know if you have any ideas to make this MIDI CC map system easier/better. Thanks.
-
- KVRAF
- 7412 posts since 8 Feb, 2003 from London, UK
I think there needs to be an easy way to see all the wiring up that you've done -- i.e. a big picture view of what CCs are connected to what and in what mode. It would help (a) understand what's happening and (b) track down problems. If this "view" could also work as an editor, that might be very handy.
-
- KVRist
- Topic Starter
- 152 posts since 15 May, 2009 from Germany
Ah, thank you for the explanation,
I only had a simple midi key board with pitch and modulation wheel.
(oh God, what a big list of possible midi CC's !)
remarks:
1) global mode works, but when opening the <map midi controller> again,
the data fields shows some nonsense, not the last entry (e.g. all fields show default values: none, none, any, ... but after some seconds suddenly "mod wheel" appears as source, but target parameter still "none", channel shows "1" instead of "any" --> so I agree to pljones, a list view is missing.
2) How can I <focus> a plugin ?
When using this mode (again mapping mod wheel to e.g. cutoff, Synthia SGbassyn) I have no effect when spinning the wheel, focusing the track, the sequence, the rack, no change of <cutoff>.
I only had a simple midi key board with pitch and modulation wheel.
(oh God, what a big list of possible midi CC's !)
remarks:
1) global mode works, but when opening the <map midi controller> again,
the data fields shows some nonsense, not the last entry (e.g. all fields show default values: none, none, any, ... but after some seconds suddenly "mod wheel" appears as source, but target parameter still "none", channel shows "1" instead of "any" --> so I agree to pljones, a list view is missing.
2) How can I <focus> a plugin ?
When using this mode (again mapping mod wheel to e.g. cutoff, Synthia SGbassyn) I have no effect when spinning the wheel, focusing the track, the sequence, the rack, no change of <cutoff>.
Everything should be made as simple as possible, but not simpler!
-
- KVRAF
- 13862 posts since 24 Jun, 2008 from Europe
1. Can you please email me a screenshot.Eggu wrote:1) global mode works, but when opening the <map midi controller> again, the data fields shows some nonsense, not the last entry (e.g. all fields show default values: none, none, any, ... but after some seconds suddenly "mod wheel" appears as source, but target parameter still "none", channel shows "1" instead of "any" --> so I agree to pljones, a list view is missing.
2. Note that the global CC mappings and the focussed mappings are in separate lists, i.e. see Edit menu -> Edit Global MIDI Controller Map and in the plugin context menu -> Edit Focussed MIDI Controller Map respectively.
I also agree with pljones that a unified list would help to make things more clear. Added to the whishlist.
Just click the plugin name, or just click the track or part. That should do it.2) How can I <focus> a plugin ?
Note that if you chose to "Use Manual MIDI Target" then you'll have to use the plugin context menu -> "Set As MIDI Input Target".
This 'manual' mode is handy when, for example, you're jamming with 2 or more people, and you don't want that the actions on the computer change the sound on the keyboard.
Hope this clarifies things.