www.megadrum.info

I tried saving a second config to MD though, confusion then arose.
Here are the steps I took
1. Load mds, add config name and save to slot 1.
2. Load another mds, add config name and save to slot 2

So, when 'load from slot' the 2 configs seem to be reversed or the naming, I'm not quite sure. I'll have another go tomorrow to see where the problem is.
Anyhow, My prefered course of action is to load and save mds and send to MD. Would it be possible to display the name of the loaded mds file in MDM?

Also, how are other folks working this?

Config Names are stored only in MegaDrum in EEPROM, they are not saved in .mds
This was done intentionally so that only MegaDrum has Config Names and they can be changes only one at a time from MDM and only when you send Global Misc setting from MDM to MegaDrum.

dmitri wrote:Config Names are stored only in MegaDrum in EEPROM, they are not saved in .mds
This was done intentionally so that only MegaDrum has Config Names and they can be changes only one at a time from MDM and only when you send Global Misc setting from MDM to MegaDrum.

Got that bit but what am I not understanding here?

I have settings, type a config name in and save to slot 1
Change the name and save to slot 2.

The second save seems to replace slot 1

I just tested it again and as far as I can see it works as I meant it. Here what I do.

Suppose that none of the slots have names and I want to enable ConfigNames and name the first slot 'name1' and the second - 'name2'.
1. Open MIDI.
2. Click Get in Global Misc settings.
3. Make sure that MDM shows 'Current' slot 1. If not, do 'Load from Slot' 1. 'Current' will show 1.
4. If 'ConfigNamesEn' is not checked, check it.
5. In 'Config Name' type name1 and press Send in Global Misc settings.
6. Load an .mds file which I want to save in 'name1' slot.
7. Do 'Save to Slot' '1 name1'.
8. Make some config changes and now I want to save it to slot 2 with name 'name2'.
9. Do 'Save to Slot' 2. 'Config Name' changes to empty and 'Current' will show 2.
10. In 'Config Name' type name2 and press Send in Global Misc Settings.

If now I do 'Load from Slot' or 'Save to Slot' I will have a choice of the following slots:
1 name1
2 name2
3
4
..

First two slots have names as I intended - 'name1' and 'name2' with rest of the names empty - and they saved in MegaDrum's EEPROM.

Suppose next day I forgot what names I gave to slots. I do 'Open MIDI' in MDM and then I do 'Get All' and, vuala, I still see the same list of slots with correct names when I do 'Load from Slot' or 'Save to Slot'

I probably should have named it 'Slot Names' rather than 'Config Names' to avoid confusion. 'Config(Slot) Names' is a property of MegaDrum itself and serves one main goal:

To easily identify what is the purpose of a config in a given slot when using MegaDrum without MDM or indeed without a PC.

You don't really need to use 'Config Names' if you always use MDM and give meaningful names to saved .mds config files.

Ah, got there eventually. You need to load from slot first and then name and then save.

Anyhow, It seems to me that the quicker way is to load an mds and send.

Would it be possible to show the name of the loaded mds on the MDM ?

Seems like a good idea, I will do it.

Oh, thank you. I think most users would be instructing from MDM these days.

Please test this version:
A few notes:
This is a test version so make a backup copy of megadrummanager.cfg in your home dir.
Unzip MegaDrumManager.jar.zip to MegaDrumManager.jar
Run MegaDrumManager.jar

In this version each MDM config is mapped to a file so when you switch between configs with prefvCfg/nextCfg or selecting a config form the dropdown list, MDM actually tries to load a config from a file mapped to this config.
A file is mapped to a selected config when you do 'Load All' or 'Save All'.
When you switch to a config which doesn't have a file mapped to it yet, MDM will show '??' in red next to the dropdownlist.
When you switch to a config which already has a file mapped to it but the file doesn't exist (deleted/moved), MDM will show '??' in red next to the dropdownlist.
When you switch to a config which already has a file mapped to it, MDM will show 'Ok' in green next to the dropdownlist.
A file name of a file mapped to a config now means the name of a config.
Upon exit, MDM will save mapping of configs to .mds files in megadrummanager.cfg

Thank you, I shall have a look at the weekend.

All good as far as I can see Dmitri. Just what I was looking for and more.
Though for claritys sake on the MDM interface, maybe use 'config' for the MD saves but a different wording for this MDM/PC save. 'patch', 'plan', 'file' maybe?