Program changes to load drum maps + configs?

[Rubis]

Great work!! We actually have more drum maps now? Dmitri, you are a miracle worker.

[elrules]

Curves in drummaps???? Weren't we talking about including Channels into drummaps?

[dmitri]

Curves in drummaps???? Weren't we talking about including Channels into drummaps?

MCU have very limited memory resources. Wherever possible I pack data. From the beginning a MIDI channel number, 4 bits, was packed with a Curve number, 4 bits, into a single byte. Hence if I move MIDI channel numbers I move Curve numbers. Do you think I should revert?

[dmitri]

Curves in drummaps???? Weren't we talking about including Channels into drummaps?

MCU have very limited memory resources. Wherever possible I pack data. From the beginning a MIDI channel number, 4 bits, was packed with a Curve number, 4 bits, into a single byte. Hence if I move MIDI channel numbers I move Curve numbers. Do you think I should revert?

Or, I can make it to ignore Channels numbers when loading drum maps on it's own, i.e. when not loading with a Config.

[el-dr]

Curves in drummaps???? Weren't we talking about including Channels into drummaps?

MCU have very limited memory resources. Wherever possible I pack data. From the beginning a MIDI channel number, 4 bits, was packed with a Curve number, 4 bits, into a single byte. Hence if I move MIDI channel numbers I move Curve numbers. Do you think I should revert?

No, please!!! This architecture is good as it is. I don't see why anyone would want you to revert to the old DrumMaps: the inclusion of Channels and Curves gives them a vastly increased versatility. If sy doesn't want to use them for changing Channels and Curves, then he shouldn't touch these parameters and use the DrumMaps like before, without even noticing the changes, but I'm sure that many of us would take advantage of the new DrumMaps.

Or, I can make it to ignore Channels numbers when loading drum maps on it's own, i.e. when not loading with a Config.

Does this mean that if you ignore the Channel settings when loading a DrumMap, only the Note Numbers and Curves would change? This wouldn't make any sense to me.

[dmitri]

Or, I can make it to ignore Channels numbers when loading drum maps on it's own, i.e. when not loading with a Config.

Does this mean that if you ignore the Channel settings when loading a DrumMap, only the Note Numbers and Curves would change? This wouldn't make any sense to me.

Sorry, of course I meant Curves.

[dmitri]

Or, I can make it to ignore Curves when loading drum maps on it's own, i.e. when not loading with a Config.

So, any opinions on this?

[Rubis]

Loading a drum map is supposed to change the MIDI mapping, correct? And the configs are meant to hold settings for each pad with regard to how they process each hit?

If this is the case, Curves probably belong with the configs, but it would not be detrimental to have them loaded with the maps. If it saves time in loading a drum map or saves space, they should be loaded only with the configs. I am sure there is someone who would want to change them mid song for some effects, maybe setting the curve to all max or something, but wouldn't they just be able to load a config?

EDIT: Just had a thought, is it possible to send a message to tell it to load a part of a map or config, but not the whole thing? Maybe just a curve from config/map 2 or a midi channel on map 3?

[dmitri]

EDIT: Just had a thought, is it possible to send a message to tell it to load a part of a map or config, but not the whole thing? Maybe just a curve from config/map 2 or a midi channel on map 3?

Hm, interesting. Anyone else thinks so?

[el-dr]

EDIT: Just had a thought, is it possible to send a message to tell it to load a part of a map or config, but not the whole thing? Maybe just a curve from config/map 2 or a midi channel on map 3?

Hm, interesting. Anyone else thinks so?

I still think you should leave the current object architecture as it is. However, this suggestion could be useful, but you must judge how big effort it would take to develop a reliable solution for it with a clear user interface, especially with a small display like this. If it doesn't get done properly, it may result in a difficult to use menu, where it would be easy to mess things up and it would also affect how MD should react to Program Changes (unless you decide to keep it restricted to loading entire Configs and DrumMaps only).