www.megadrum.info

I've been working on some new features which require simultaneous changes both in the MegaDrum firmware and MDM.
Because of the size and nature of changes I'm now looking for brave volunteers to test new features.
The new features are:
1. Saving to any EEPROM slot from MDM.
2. Maximum number of configs reporting in MDM
3. Custom pads names options is now in Global Misc settings where it belongs.
4. Custom Config Names.

The latest test firmware and MDM versions are in viewtopic.php?p=25346#p25346
To run MDM: unzip the downloaded MegaDrumManager.jar.zip into MegaDrumManager.jar file and run it as 'java -jar MegaDrumManager.jar' from a command line):

Please let me know if you find any bugs or misbehavior in both new and old features.

Looks good Dmitri. I have only tried MDM - but the functions looks promising!

We should maybe also add the "Disable/Enable Others" function to the list - which now is included in MDM. It is like a SOLO button for the current PAD. Great function!

Function: The "Disable Others" button in the Pads controls panels.
Solves: If error seeking/configuring a single PAD where other PADs inputs interfere or if using MD in a configuration environment where only one PAD is connected but where the cables are attached to many inputs but not connected, could generate a lot of random hits from the other PADS. Very nice to use this quiet function!
Description: When you press it, it will change to "Enable Others" and send configuration (regardless of Live Updates state) to all pads with the Note set to 0 except for the current pad. When you press "Enable Others", it will change to "Disable Others" and send configuration to all pads with Note set to the original value! Also, when all other pads are disabled, pressing Get, GetAll, switching to another pad will automatically re-enable all pads and re-send the original configuration.
Warning: When entering the disable others mode - do not manually save the configuration on MD by hand to any slot.

ANGR77

Hi Dmitri,

I'm very busy at the moment, but maybe in the next few days I will find some time to install the new firmware and MDM.

But as you are just having a look at MDM ... I have a minor issue with an old feature at the moment: It seems that MDM doesn't read the midi in/out from my option file, I have to adjust the ports every time I fire up MDM. In "megadrummanager.cfg" Ports are properly saved like all the other options, so things go wrong while loading the options on startup. All other options are read on startup.

I'm using MDM on a linux machine, maybe it's because of this. Can you confirm? Megadrum firmware version is 20130901, Megadrum is the ARM based.

Thanks in advance and greetings,
Frank

Frawo wrote:But as you are just having a look at MDM ... I have a minor issue with an old feature at the moment: It seems that MDM doesn't read the midi in/out from my option file, I have to adjust the ports every time I fire up MDM. In "megadrummanager.cfg" Ports are properly saved like all the other options, so things go wrong while loading the options on startup. All other options are read on startup.

I'm using MDM on a linux machine, maybe it's because of this. Can you confirm? Megadrum firmware version is 20130901, Megadrum is the ARM based.

I'm testing it on Mac OS X and it seems fine.

I'll take a look

Just realised, in MDM, 'next config' seems to revert custom names back to default.

Same in previous firmware

airflamesred wrote:Just realised, in MDM, 'next config' seems to revert custom names back to default.

It's supposed to do that. 8 configs in MDM don't relate to configs in MegaDrum - they are completely independent from each other, including Global settings like Custom pads names, number of inputs and etc.

High level not reading back to MDM (firmware 20130612)

These test MDM and firmware versions should not be used with any other MDM or firmware versions.

No, sorry, no test versions used. I just happened to be messing with my pads and re setting the high level.