Program changes to load drum maps + configs?
Posted: Tue Jun 23, 2009 11:31 amDmitri,
a few days ago I made a feature request, so that MD would accept program change messages, which you added to the latest fw the same day (that's what I call perfect support
). Now that I managed to heal the infamous USB plague, I tried this new feature and it works as expected, thanks. You also asked me if program changes should be used to select Configs as well.
I was very wrong when I said it's not so important, because I was not fully aware of the MD object concept at that time. Because all other trig-to-MIDI converters I know have some kind of "kit" or "set" object, I thought Drum Maps were the MD equivalent of that, which is basically true, but with an important restriction.
While other converters have a set of common parameters (base channel, sometimes input sensitivity, threshold etc.) and "Kits" usually contain at least a pair of Channel and Note numbers for each input (and sometimes curves etc.), the MD Drum Maps contain Note assignments only and the Channel info belongs to the Config objects.
This means that if I want to change between "setups" (e.g. switching from triggering one sound source to a different one, which is likely to be set to a different MIDI Channel), changing the Drum Maps is not always enough, because selecting a new Config is the only way to change the transmit Channel. So would it be possible to apply this new feature to changing the Configs, too? It could work the exact same way as for the Drum Maps: because MD will never store 128 Drum Maps, there could be a currently unused range of Program Change messages (e.g. above 64) that would Load Configs.
I hope this would be just as simple as adding the Load Drum Maps by Program Changes feature... Please
a few days ago I made a feature request, so that MD would accept program change messages, which you added to the latest fw the same day (that's what I call perfect support
). Now that I managed to heal the infamous USB plague, I tried this new feature and it works as expected, thanks. You also asked me if program changes should be used to select Configs as well. I was very wrong when I said it's not so important, because I was not fully aware of the MD object concept at that time. Because all other trig-to-MIDI converters I know have some kind of "kit" or "set" object, I thought Drum Maps were the MD equivalent of that, which is basically true, but with an important restriction.
While other converters have a set of common parameters (base channel, sometimes input sensitivity, threshold etc.) and "Kits" usually contain at least a pair of Channel and Note numbers for each input (and sometimes curves etc.), the MD Drum Maps contain Note assignments only and the Channel info belongs to the Config objects.
This means that if I want to change between "setups" (e.g. switching from triggering one sound source to a different one, which is likely to be set to a different MIDI Channel), changing the Drum Maps is not always enough, because selecting a new Config is the only way to change the transmit Channel. So would it be possible to apply this new feature to changing the Configs, too? It could work the exact same way as for the Drum Maps: because MD will never store 128 Drum Maps, there could be a currently unused range of Program Change messages (e.g. above 64) that would Load Configs.
I hope this would be just as simple as adding the Load Drum Maps by Program Changes feature... Please
