Is Xmas already here?

[dmitri]

A new firmware has been available for 2 days already and not a single download:)

[Synthex]

It takes too long to buy gifts !

[elrules]

Too busy here. I have been selected to work in Amsterdam as practices (the Leonardo program), and I am preparing a lot of things.

I have to recompile the MCT for this new firmware. Hope I can do it tonight.

Can we start talking about automatic firmware updates detection?? I think this is a needed feature as if I update the MCT it won't work well with previous firmwares, so it would be better to have that feature to advice users to download the new firmwares.

My suggestion is to upload to for example:
www.megadrum.info/firmware/
all the firmware versions named with the format:
megadrum_inputs_MCU_clock.syx
and upload also a lastversion.txt file containing the line:
20081214

MCT will access that file and check if user has an obsolete firmware. It will prompt the user to download it and update. It will download the correct file according to Nº of inputs, MCU, and clock settings that he has set in MCT.

[dmitri]

I will think about the automatic detection of new firmware.

[Xmattz]

I didn't download firmaware, but it's Synthex fault ! He sold me the chip already programmed and now I m too lazy/affraid to do it...

[Synthex]

but it's Synthex fault !

[elrules]

When MCT runs the first time it writes LastVersion=<currentdate> so only firmwares later than this date will be detected as new.
It would be nices for example if version is sent with the Misc sysex, so it is more reliable than MCT supposing itself what version you have

[dmitri]

When MCT runs the first time it writes LastVersion=<currentdate> so only firmwares later than this date will be detected as new.
It would be nices for example if version is sent with the Misc sysex, so it is more reliable than MCT supposing itself what version you have

I will add it to the Misc SysEx.

[elrules]

There is a problem with the last firmware. I have updated (locally) MCT, and when I send Kick settings in MD screen it always sets gain to 0, no matter which value I set in MCT. Same with not-yet-updated public MCT.

When are you going to add the firmware sending with Misc sysex? I have thought that maybe a special sysex request would be better. That way MCT will always send a request for firmware version info each time it starts and check for available updates in the web.

[dmitri]

There is a problem with the last firmware. I have updated (locally) MCT, and when I send Kick settings in MD screen it always sets gain to 0, no matter which value I set in MCT. Same with not-yet-updated public MCT.

Sorry, my bad. I mixed up data order in pad config SysEx messages. It's now fixed in the latest version.

When are you going to add the firmware sending with Misc sysex? I have thought that maybe a special sysex request would be better. That way MCT will always send a request for firmware version info each time it starts and check for available updates in the web.

I did exactly that, added a firmware version SysEx message.