[NOT A BUG] Conflicting MIDI mappings Global/Sampler
-
- Posts: 59
- Joined: Sat Jun 08, 2019 8:28 pm
[NOT A BUG] Conflicting MIDI mappings Global/Sampler
When in Global Gstomper won't show me an allocated CC for Sampler, allowing to set the same CC #. How normal is this? Makes me mad...
Re: [NOT A BUG] Conflicting MIDI mappings Global/Sampler
lonbluster wrote:When in Global Gstomper won't show me an allocated CC for Sampler, allowing to set the same CC #. How normal is this? Makes me mad...
This is of course not a bug. The mappings for the global MIDI channel are completely independent from the drum sampler MIDI mappings.
You can map CC01 in global mappings to some parameter, and in the drum sampler MIDI mappings you can map CC01 to something entirely different.
As a matter of course, you should NOT use the same MIDI channel for global and sampler, as this is how modules are separated from each other in the MIDI protocol.
-
- Posts: 59
- Joined: Sat Jun 08, 2019 8:28 pm
Re: [NOT A BUG] Conflicting MIDI mappings Global/Sampler
Thanks for pointing at the channel issue.
It's the warning feature of G-stomper which is at stake.
I guess if I wanted to use All channels for Global I can only use same CCs for functions available only in Global. Or use unique CCs. Sounds good?
It's the warning feature of G-stomper which is at stake.
I guess if I wanted to use All channels for Global I can only use same CCs for functions available only in Global. Or use unique CCs. Sounds good?
Re: [NOT A BUG] Conflicting MIDI mappings Global/Sampler
lonbluster wrote:I guess if I wanted to use All channels for Global I can only use same CCs for functions available only in Global. Or use unique CCs. Sounds good?
Also note that if you use the same channel, you should clear the global key mappings. Otherwise you'll have double triggers.
Who is online
Users browsing this forum: No registered users and 27 guests