Kits, maps, slots, and configs (oh my)

[BiggerNoise]

I am having a bit of trouble with some of the terminology for MD/MDM.

Config & Slot
In MDM, it appears that we are working with a "config". There's definitely the idea of a config that is being edited and I can get/send that config to and from MD. There's also the load and save to slot, which puts the config being edited into Non-volatile storage so it can be reloaded on the next MD start up. Load All and Save All load/save a single config from/to an MDS file.

MDM indicates that there are 22 cfg slots and that I am working with the config in slot1.

So far, all of this is actually pretty straightforward.

Now in the middle of MDM, there's a drop list with config1..8 as my choices. Is this supposed to be a supercharged A-B comparison? I.e. Load my config from Slot1 into 1 & 2, then modify one version and be able to quickly toggle back and forth between them. If that's not right, I would love some clarification

Kits and Maps
In the AD thread, there are downloads for kits and maps. These downloads appear to have the same information and are what I would expect to be called configs. I have seen maps referenced elsewhere, but I can't tell the difference between a kit, a map, or a config.

I would expect that a map would change the note & controller values and a kit would also include the actual setup for the sensors. But I can't see where this distinction ever comes into play with MDM.

If someone can point me towards a a document somewhere that gets into this, I would be happy to update this thread with what I find.

Thanks,
Andy

[angr77]

Hi Andy.

Yes, I must agree that the terminology could sometimes be a bit confusingly... and there is not any real manual available for MDM... which maybe makes the first experience for a new comer a bit hard. However, what you see in MD/MDM have evolved for more than a decade, sometimes there is new functionality which have replaced old... but the old still remains etc.

I think you have grasped the idea regarding config and slots. The 1-8 configs is to my knowledge rarely used. It could be used to do A-B comparisons but the configs are only active in MDM(In RAM).... you need to press send all or do a save to slot for each config 1-8...you want to hear...

Then it is better to use two slots and do the A-B comparisons here instead. Then you both have the data in MDM and in the MD.

Regarding the new ROM Kit and ROM MAP... have you seen my manual?

Best regards

Angr77

[dmitri]

Now in the middle of MDM, there's a drop list with config1..8 as my choices. Is this supposed to be a supercharged A-B comparison? I.e. Load my config from Slot1 into 1 & 2, then modify one version and be able to quickly toggle back and forth between them.

This is exactly what config 1..8 in MDM are meant for.

Kits and Maps
In the AD thread, there are downloads for kits and maps. These downloads appear to have the same information and are what I would expect to be called configs. I have seen maps referenced elsewhere, but I can't tell the difference between a kit, a map, or a config.

Kit/config is the same thing - it contains all MegaDrum settings. Drum Map contains only all Notes and Curves settings.

[BiggerNoise]

Thank you guys for replying. I am pretty familiar with feature accretion and definitely expected that some of that was at work here.

As far as your manual goes, I assume you are referring to the guide you put up at digital drummer. If so, yes, I did see that (very nice). It did make me think that I was definitely missing something on kits/maps.

Is there any way to save or load a drum map from MDM? I see the function on the MD menu, but I do not see any way to manage them from MDM. That's certainly fine if that's the case, I just want to make sure that I am not missing something.

[dmitri]

MDM can only save complete config but it can load partial configs, e.g. if you manually edit the config file and remove everything except Notes and Curves then you can load it with MDM and it will only modify Notes and Curves, i.e. this edited config becomes a drum map.

[BiggerNoise]

OK, makes sense. Thanks.