"Megadrum Config Tool" released

[elrules]

I have updated MCT to version 1.84.

It contains the changes Firelord did to it, that is: supporting the new update system for encrypted firmwares.

Hope it works ok for all of you. Just execute the MCT you had downloaded from www.megadrum.info/configtool and it should autoupdate to latest version.

[Ken Forgettable]

I still think that moving the problematic MIDI sysex timing/buffering to the file system level (where time-outs and transfer blocking are properly handled on *all* platforms) could be worthwhile.

NB. This would break the standard cable MIDI firmware updating compatibility, but open the way for unlimited config' / patch definitions...

Question is:- is a combined MIDI / mass storage device possible

[elrules]

It could be interesting to use the library davem is doing, and adapt the Java MCT version to use that library. That is, make everything work perfectly on all platforms with the current java version, and then we could start another project, which may take a long time.

[Ken Forgettable]

... make everything work perfectly on all platforms with the current java version ...

I hope the davem lib' will have XML support (try <http://sourceforge.net/projects/tinyxml/>), and maybe there is no real incentive to hang mass storage from the PIC at all

[Thud]

I'm trying to do a firmware update but I'm confused about which settings to choose.

In the MCT manual it says:
Make sure you select the one that suits your MCU and clock.

Where can I check what MCU & clock I have?

Me too.

EDITED:

It's ok. I found the details - in one of my old posts