MegaDrum Manager

[dmitri]

Try this one:

MegaDrumManager.jar.zip

[zaklinacz]

Hi Dmitri,
this is exactly what I was looking for - thank you!
BR
Michal

[dmitri]

Can you play around with it and tell me what is missing or not behaving as desired when running on a netbook?

[zaklinacz]

yes, sure, just give me some time (1-2 days)

EDIT:
I've had some time to play around and I've found one thing:
of course when I start app I'm going full screen, and every time I do something that redraws interface, the window changes it's size and I have to maximize main window once again.
It is not something critical, but preventing this will help.

BR
Michal

[dmitri]

I just uploaded a new MDM version (20121123) with a few important updates:

1. Implemented verification when sending configs from MDM to MegaDrum. Now when you send Config(s) (with Send/with SendAll/with Live Updates) to MegaDrum, MDM request a config from MegaDrum after sending each config item (Misc, Pedal, Input and so on) and if the received config differs from the config in MDM or is not received at all then it will indicate a problem in the top menu toolbar next to "nextCfg" button. Possible messages there are:
'SysEx Ok' - means everything is ok.
'SysEx Wait' - MDM is talking to MegaDrum.
'SysEx Error' - a config item/config items mismatch between MDM and MegaDrum after sendig last config(s) to MegaDrum.
'SysEx Timeout' - after sending a config item, MDM didn't receive a response from MegaDrum.
'SysEx Timeouts' - after sending config items (SendAll) MDM didn't receive some or any response from MegaDrum.
'MIDI Init Error' - error while opening MegaDrum MIDI ports.

2. Thanks to the above implemented feature, I immediately pinpointed a bug, which many of you probably experienced, where some Sysex messages where not making out of MDM. As far as I can judge I fixed this bug in this version.

3. Added an AutoResize checkbox in the second top menu toolbar to enable/disable auto resizing of the main window.

[angr77]

Dmitri.

I can just confirm that all my USB/Midi errors disappered on my systems using the latest MegaDRUM Manager (I am using a couple of old HP/Compaq 6910p with 64 bit Windows 7)

Not a single "hang Up" during two hours of work with the MD. Before - It happend every 4-5 minutes when doing alot of sysex updates!

THANKS MATE!!! This is an early X-mas gift!!

Best Regards

Anders

[airflamesred]

Haven't tried it but thanks anyway Dmitri.

[airflamesred]

Is it just me or can anyone view the midi log. Tried detach and show - no joy,

Ah wait had to re load it - sorted

What is the 'send triggered in' box for?

[dmitri]

From http://www.megadrum.info/forums/viewtop ... f=3&t=1075 :

Changes in version 20120911:

1. Added a new configuration option in 'Miscellaneous settings' called 'TriggeredInCC'. When set to Yes and you hit a pad, MegaDrum will send a special MIDI CC message telling exactly which input was triggered. This is now being used in MDM to quickly switch between inputs configs. It will also be used in MDCommander a bit later.

[airflamesred]

Ah sorry, my fault Dmitri

So in MD there is config and drum map. I guess drum map is channel and note info and config is the rest?
In MDM there is only config. I think what I am asking is how do I harness a patch change vie pedal. I have an old simmons pedal (stereo jack) could I utilize this?