New features testing needed

[ibanman555]

Dmitri,

Been away a while but I'll finally have some time again to work on this project. I also have some things/ideas I'm hoping we can sort out...

I'd like to contribute to the testing in a week...

[angr77]

Hi!

I have loaded the new firmware (It was very hard to update the firmware - it took like 45 attempts before it worked - It has been like this during the last year - nothing new )

Running the new MDM / New Firmware. It seems to work like a charm. I first made a backup with MDM 20130901 of my MD config and saved it to a MDM file.

After upgrading the firmware - I was running the new MDM version and re-opened and saved my configuration back to MD. Just to be sure.

Now - I did look on the functionality - Very nice that you could set a name on the configuration instead of having a slot number.

I am guessing the new buttons "save" and "get" only sends the name of the config...not the actual configuration. Or. Nice to see which current config which is loaded in MD...on the LCD and the MD field "CurrentConfig".

I am guessing the old button "save to slot" - is saving to the current config? (I have never trusted this function...I have manually saved the config to the right slot on my MD) Does it really work now and is saving to a slot? (So if I turn the MD off...It is reading the right config saved to slot 1. (With autoload config= yes)

To be able to save the current config in MDM to another slot - please use the menu - "main - all setting - save to slot. You will here now see all slots...just to pick the right one.

Good to be reading the post above about the old config dropdown in MDM...that this has nothing to do with the MD slots...only in MDM. A bit confusing if you see it for the first time. Should maybe moved in the GUI. The save to slot could maybe moved to the slot name get - save part.

Very nice to have the update status in MDM on the amount CFG slots(I got 23 slots) and the current working slot.

Custom PAD name is nice function. Custom names has been around before - but it was a bit confusing - especially if you changed a input with the default name "crash" to a custom name...when stepping through...and just looking on the input field...you read Crash in the past...even if the padname was something else like Triggera etc...a bit confusing in the past. Much better now! The input and pad name now follows each other. The only bug I could see about this was that you were forced to step through all the pads a couple of times before the input name changed to the actual Bow/head/RIM names. Anyhow - A great function!

I have been talking a bout the disable other function before. Very nice if you have a rehearsal room with all drums connected...and want to patch one drum at home. I have fixed installed 2x8 multicables connected in my MD/Sound card 19" rack and which worked as complete drum antennas)...the false triggering could drive you nuts - Not any more with the Disable other function.

Very nice performed Dmitri!! Your dedication is just too good!!

Best Regards

ANGR77

[dmitri]

angr77, thank you for testing!

Hi!

I have loaded the new firmware (It was very hard to update the firmware - it took like 45 attempts before it worked - It has been like this during the last year - nothing new )

Running the new MDM / New Firmware. It seems to work like a charm. I first made a backup with MDM 20130901 of my MD config and saved it to a MDM file.

After upgrading the firmware - I was running the new MDM version and re-opened and saved my configuration back to MD. Just to be sure.

Now - I did look on the functionality - Very nice that you could set a name on the configuration instead of having a slot number.

I am guessing the new buttons "save" and "get" only sends the name of the config...not the actual configuration.

You mean the buttons Get and Send next to the Live updates button? These get/send Global settings, i.e. number of inputs, LCD contrast, ConfigNameEn (custom configs name enable/disable), Custom Pads Name (enable/disable) and ConfigName (if enabled) of the current config name.

Or. Nice to see which current config which is loaded in MD...on the LCD and the MD field "CurrentConfig".

I am guessing the old button "save to slot" - is saving to the current config? (I have never trusted this function...I have manually saved the config to the right slot on my MD) Does it really work now and is saving to a slot? (So if I turn the MD off...It is reading the right config saved to slot 1. (With autoload config= yes)

To be able to save the current config in MDM to another slot - please use the menu - "main - all setting - save to slot. You will here now see all slots...just to pick the right one.

The "Save to Slot" button and the menu item "Save to MD slot:" should behave identically. They are populated with available slots numbers (names) once MDM knows the number of available slots in MegaDrum after you do "Get All" or "Get" Global settings. When you select one of the slots from either "Save to Slot" or "Save to MD slot", the current MegaDrum settings are saved to the selected slot, AutoLoadConf is set to Yes with the selected slot.
Can you please re-test this functionality?

Good to be reading the post above about the old config dropdown in MDM...that this has nothing to do with the MD slots...only in MDM. A bit confusing if you see it for the first time. Should maybe moved in the GUI. The save to slot could maybe moved to the slot name get - save part.

Where do you think it should be moved to to avoid confusion?

[angr77]

Hi Dmitri.

I made a second round with my MD.

I am actually facing problems. I have my configuration in a MDS file. I can send this to MD and when verifying the settings on MD it looks right. I have saved it to slot 1.

1. If I then hit the close midi button in MDM at this stage - and just switch MD off and power it up again...my settings are gone. The default settings for all channels is entered. (autoload has been set to yes.)

2. If I do the same task again...(send my config to MD) not doing any save to slot in MDM and instead saving the configuration to slot 1 manually. The saving process says "failed" the first time...but done the second time. But when powering off the MD...and on again...the default settings are back. (e.g not my settings)

3. Ok...I then tried to save my configuration to slot2 instead. Power off/on process...which loads settings from the slot 1...with the default settings( not mine)...I am now able to load my settings manually from slot 2 on the MD. (So they are there...) Tried to save loaded settings on the MD to Slot 1....Power Off/on...no...still the defaults.

Slot 1 seems to have gone...no way to be able to save to this slot.

Something seems to be wrong here

Best Regards

ANGR77.

[dmitri]

Slot 1 seems to have gone...no way to be able to save to this slot.

I will re-check it myself.
Did you test populating "Save to Slot" and "Save to MD slot:" with slots? Do they behave identically (correctly or not doesn't matter)?

[angr77]

Hi there!

I made a third try out!

I found that if unchecked the confignamesEN checkbox..then I was able to save my config to slot 1 and make it to stay resistant!
There is something there. (I used at first a too long name like "Addictive" - e.g. 9 characters...could that cause the problems? I changed it yesterday to a shorter name but the problems still remains - I made a new test today...as soon as I used the confignamesEN checkbox my problems started again.)

Coming back to your question. I have verified the "Save to Slot" and "Save to MD slot:" and the function is the same. Works great if the confignamesEN is unchecked. Nice to get the slot dialog by just clicking the button.

Just an idea:
From a logical standpoint - I am guessing the "save to slot" means that the current config in RAM on the MD is saved into a slot. However, this could be a bit confusing in MDM ... I would expect that most people would consider that the config seen in MDM is saved in to a md slot. (But the right process would be "Send All" from MDM and then do the save to slot in MDM.

Should the work related to MDM sending/receiving MD data have it´s own panel and the internal MD operational task driven from MDM should have its own panel to make this clear? (This is why I have not been trusting - I did not understand that the "save to slot" function...and instead used the manual process on the MD)

[dmitri]

Please test these versions:

megadrum_20131110.zip

MegaDrumManager.jar.zip

The bug with AutoloadConf when Config Names are enabled should be fixed here.
Some clean up in MDM.

I used at first a too long name like "Addictive" - e.g. 9 characters...could that cause the problems?

The maximum Config Name length is 12 characters.

Just an idea:
From a logical standpoint - I am guessing the "save to slot" means that the current config in RAM on the MD is saved into a slot. However, this could be a bit confusing in MDM ... I would expect that most people would consider that the config seen in MDM is saved in to a md slot. (But the right process would be "Send All" from MDM and then do the save to slot in MDM.

Should the work related to MDM sending/receiving MD data have it´s own panel and the internal MD operational task driven from MDM should have its own panel to make this clear? (This is why I have not been trusting - I did not understand that the "save to slot" function...and instead used the manual process on the MD)

What about replacing "Save to Slot" with "Send All and Save to Slot"?

[angr77]

Hi again!

Results from race 4: Works great!! Now it is possible to save to slot 1 with a name. Rebooting the MD - And the data is there.

Some notes:
It seems like when reading back configuration from MD to MDM...the configname is truncated to 8 characters. You can send 12 characters and see it on the MD...but when reading back from MD...it is 8 letters. Saving back...then you have 8 letters also on the MD.

When starting to work with more configurations on different slots...the only way to change to e.g. slot 2 and read back the configuration...is that you need to select/load the right slot on the MD first. No problem really...but if you want control everything from MDM...it should be able to select the current slot in MDM. Saving to the right slot from MDM is no problem!

Other stuff
It seems like the LCD contrast is not working when sending from MDM.
All Gains Low - Has that parameter disappeared on the MD? I can't find it any where

What about replacing "Save to Slot" with "Send All and Save to Slot"? - I would say yes!!

Best Regards

ANGR77

[dmitri]

Hi again!

Results from race 4: Works great!! Now it is possible to save to slot 1 with a name. Rebooting the MD - And the data is there.

Some notes:
It seems like when reading back configuration from MD to MDM...the configname is truncated to 8 characters. You can send 12 characters and see it on the MD...but when reading back from MD...it is 8 letters. Saving back...then you have 8 letters also on the MD.

I'll check that.

When starting to work with more configurations on different slots...the only way to change to e.g. slot 2 and read back the configuration...is that you need to select/load the right slot on the MD first. No problem really...but if you want control everything from MDM...it should be able to select the current slot in MDM. Saving to the right slot from MDM is no problem!

I'll add "Load from Slot" a bit later.

Other stuff
It seems like the LCD contrast is not working when sending from MDM.

I'll check that.

All Gains Low - Has that parameter disappeared on the MD? I can't find it any where

It's available(and useful) only in Atmega.

[dmitri]

MDM with a fix:

MegaDrumManager.jar.zip

Hi again!

Results from race 4: Works great!! Now it is possible to save to slot 1 with a name. Rebooting the MD - And the data is there.

Some notes:
It seems like when reading back configuration from MD to MDM...the configname is truncated to 8 characters. You can send 12 characters and see it on the MD...but when reading back from MD...it is 8 letters. Saving back...then you have 8 letters also on the MD.

I'll check that.

Should work correctly now.

Other stuff
It seems like the LCD contrast is not working when sending from MDM.

I'll check that.

I checked and it seems to work correctly.