History of MegaDrum firmware versions

[gabriel1712]

Will using "sent all to MD" or "write to slot 1" mess up things for MD or will it simply disregard the Pedal settings and sent the rest, no harm done?

"send all to MD" may definitely mess up things for MD like buffer overflows.

Oki, I'll stay clear of that. But "write to slot 1" should be fine?

[dmitri]

Will using "sent all to MD" or "write to slot 1" mess up things for MD or will it simply disregard the Pedal settings and sent the rest, no harm done?

"send all to MD" may definitely mess up things for MD like buffer overflows.

Oki, I'll stay clear of that. But "write to slot 1" should be fine?

"write to slot 1" should be fine. And stay away from sending pedal settings.

[popesky]

midox doesn't work

It never failed me.

ye ... works fine when I set the output (not INPUT ) buffers to 60000

[kimouette]

Any chance I'm having problems with the latest firmware because I'm using MCT to upgrade?

Anyone else using the following method having similar issues?

- Downloaded megadrum32_20090508.zip
- Plug MD and open MCT
- Select "update Firmware" in MCT
- When MCT asks for it, unplug MD and plug it back while holding the left button
- MD is ready, press "down" on the MD, and "yes" in MCT
- Firmware is being sent, the LED flashes and when it stop flashing I press "ok" in MCT
- MD shows the initial screen and the normal Vu-Meter (and actually, everything remains normal until I chose "Load Config")

- Use the "down" button to navigate to "Load Config" and select "config 1" (which contains my latest/best settings)
- And that's when I get the first pic I showed you
- Once I'm there, nomatter what I press ("up", "down", "left" or "right"), the only screen I can get, is the one showing "Loaded DrumMap" (1,2,3 or 4)

- Since there's nothing else I can do, I unplug MD and plug it back
- Same thing... everything is normal, everything works fine.
- Navigate to "Load Config" and chose "Config 2"
- I get the third screen I showed you. But nothing works, even though I keep trying "left", "right, up or "down".

- I tried to download the firmware 3 times to make sure the problem wasn't caused by some failure while downloading.

- I also double check everytime I chose the firmware version, to make sure I select "megadrum32_16_32_20090508.syx"

- Like I said, I went back to an older version and everything's back to normal

[gabriel1712]

MCT firmware update is broken. Use the MIDI-OX method.

[kimouette]

MCT firmware update is broken. Use the MIDI-OX method.

It's ok I'll just wait for the next firmware upgrade and keep my fingers crossed !
I have a Mac, so I can only use MCT to upgrade my firmware.

[dmitri]

I didn't try it myself but I guess this program can send/receive Sysex MIDI on Mac: http://snoize.com/SysExLibrarian/

[kimouette]

I didn't try it myself but I guess this program can send/receive Sysex MIDI on Mac: http://snoize.com/SysExLibrarian/

Yeah this is one of the rare (or only?) soft supposed to allow Mac users to send sysex messages to any hardware connected to the computer. But in fact, I can only read the content of sysex messages with it... trying to send them to MD failes.
Normally when the messages are sent, the LED blinks about 50 times and when it's done, the initial MD screen is loaded. But with this soft, the LED doesn't blink, the "Send sysex message" never disappears, and when rebooting MD, the Vu-Meter is all messed up.

I guess the problem I've had couldn't have been be caused by MCT, otherwise I would have got similar problems with the previous versions too. But anyway, right now none of this matters. If the next firmware does the same thing, I'll start to worry, but until then, I'm fine with the one from April.

[fuzzysnuggleduck]

I just found someone's work on Cocoa and CoreMIDI stuff online...

http://members.shaw.ca/akochoi-old/blog ... index.html

The "SysExSenderX" program is available but only as source code. It may or may not work better than SysEx Librarian. Could be worth a shot, or a look at the code.

[kimouette]

Well the latest firmware does the same thing with my MD

Oh and another weird symptom that goes with the Vu-Meter blocs problem... a sound! A sound coming from my tom piezo whenever I have one of the two laterst firmware installed. That bug is terrible. It literally makes my piezo squeal! I hope it didn't kill it! Didn't have the time to check this morning.

I'll try to look at that Cocoa source code... but even though I'm the only one with this weird bug, I still dont understand how MCT could manage to let me install a firmware correctly and not a certain upgrade of that same firmware

Geez I'm really starting to pile up problems!