elrules wrote:dmitri wrote:elrules wrote:Well, in MCT I think (not sure now that you doubt about it) that when you select Actions->Drummaps->Load frokm file or Save to file. You actually save all the midi notes and all the channels of all inputs. It is not related to live switching drummaps because you have to send then the whole config to MD, but it is just the idea I had of what a drummap is.
Well, in this case in MegaDrum you can call Configs DrumMaps because it saves both notes and channels in Configs.
As I said, I can add MIDI channels to drum maps but it will half the number of available drum maps.
How many drummaps are available? (to see the impact of halving them). I mean, I prefer having 3 drummaps that I can quickly change live to control different instruments (more easily done with different channels) than having 100 drummaps where I can only change midi notes. Just my 2 cents
I think it's only a linguistic question what we mean by DrumMaps and Configs. I started this thread when I discovered that DrumMaps don't store Channel settings but Configs do. Then I realized that Configs can be regarded as the objects that store "kits" or "drum maps", while a DrumMap is something that doesn't exist in other systems I know and can be useful if you want to switch between the samples of a single instrument. Anyone who uses multitimbral setups or more than one instrument will probably switch between Configs and not DrumMaps in most cases.
The good thing about having all settings in your "kits" is that sometimes you might need different velocity curves and other settings, so having Channel and Note information only in the kits (which is used by many manufacturers) can be very restrictive: e.g. if I play a sample on a specific pad, I'd choose a dynamic velocity curve for it, but if the same pad in the next tune is used to trigger drum loops, I'd prefer to set a constant velocity "curve", so that the volume of the loop would be consistent whenever I hit the pad and would set a very high threshold to eliminate the chance of starting the loop by an accidental hit. MD is actually better than most other systems at this, because the ones that store Note and Channel data only in their kits, putting all other parameters (curves, sensitivity etc.) to the Global Settings category, don't usually allow to store multiple Global Settings (the equivalent of MD Configs).
So, I think if memory limitations have to be considered, I personally would prefer to store more Configs than to increase the number of DrumMaps with or without Channel info. But of course, it would be more flexible if the Channel settings were part of the DrumMap object. If I had to make a choice for the sake of saving memory, I'd sacrifice DrumMaps completely if I could store more Configs.