History of MegaDrum firmware versions

[dmitri]

Dmitri, did you notice if you try to change the edge gain on the yamaha cymbals to anything other than 4 it will not send aftertouch messages? I used to have my edge gain at 2 this is not possible anymore.

Of course. After changing the gain on the switch inputs you will have to change the threshold.

[kurtus420]

Thanks Dmitri.

Dmitri, did you notice if you try to change the edge gain on the yamaha cymbals to anything other than 4 it will not send aftertouch messages? I used to have my edge gain at 2 this is not possible anymore.

Of course. After changing the gain on the switch inputs you will have to change the threshold.

[elrules]

Hi Dmitri, I have seen you introduced a new parameter in the Misc config. I will update MCT as soon as I can.

I have thought about an improvement for the "check for updates" feature. Could you put in the latest_version.txt file all the info about new versions?
It must be something like:

Code: Select all

20091007
1. Fixed the issue with a switch type HH pedal where it was not possible to get proper results without using a pull up resistor.
20091004
1. Further optimized some firmware internals. No kidding!
20090927
1. Further optimized some firmware internals.
20090926
1. Added an "InputsPriority" option. When set to Yes the first 3/4th of Head/Bow inputs are given slightly higher priority (sampled more often) then the rest of inputs.
2. Considerably optimized some firmware internals which should have positive effect on overall performance.
[etc]

With the version numbers in separate lines so I can detect if a the next line is info text or the beginning of another version
I will have 2 different ways to parse it.
1 - When I check for new versions available, I will parse the file from the beginning till I find the version number that the user currently has, and I will show the user a screen where he can read the new changes made since the last time he updated his MD.
2 - I will add an option "Firmware version history" where I will parse the whole file to show the user all the changes made in MD. I may show the user this info like the version history screen of Winamp, although as there are not so many changes to show from one version to another I think it could be more user-friendly to show him the whole list

Tell me if you do this so I can make real tests

[dmitri]

I will do it.

[elrules]

Is it possible to add the option to change hihat pedal MIDI channel? (I suppose now it is hard-coded to channel 10). We can currently change this parameter on any pad input, but not on the hihat pedal, which for me is a bit weird

[dmitri]

Is it possible to add the option to change hihat pedal MIDI channel? (I suppose now it is hard-coded to channel 10). We can currently change this parameter on any pad input, but not on the hihat pedal, which for me is a bit weird

I'm away from my main laptop but I'm pretty sure the HH pedal MIDI channel is tied with the channel number of the HH input.

[elrules]

Is it possible to add the option to change hihat pedal MIDI channel? (I suppose now it is hard-coded to channel 10). We can currently change this parameter on any pad input, but not on the hihat pedal, which for me is a bit weird

I'm away from my main laptop but I'm pretty sure the HH pedal MIDI channel is tied with the channel number of the HH input.

Sounds pretty logical

[dmitri]

Hi Dmitri, I have seen you introduced a new parameter in the Misc config. I will update MCT as soon as I can.

I have thought about an improvement for the "check for updates" feature. Could you put in the latest_version.txt file all the info about new versions?
It must be something like:

Code: Select all

20091007
1. Fixed the issue with a switch type HH pedal where it was not possible to get proper results without using a pull up resistor.
20091004
1. Further optimized some firmware internals. No kidding!
20090927
1. Further optimized some firmware internals.
20090926
1. Added an "InputsPriority" option. When set to Yes the first 3/4th of Head/Bow inputs are given slightly higher priority (sampled more often) then the rest of inputs.
2. Considerably optimized some firmware internals which should have positive effect on overall performance.
[etc]

With the version numbers in separate lines so I can detect if a the next line is info text or the beginning of another version
I will have 2 different ways to parse it.
1 - When I check for new versions available, I will parse the file from the beginning till I find the version number that the user currently has, and I will show the user a screen where he can read the new changes made since the last time he updated his MD.
2 - I will add an option "Firmware version history" where I will parse the whole file to show the user all the changes made in MD. I may show the user this info like the version history screen of Winamp, although as there are not so many changes to show from one version to another I think it could be more user-friendly to show him the whole list

Tell me if you do this so I can make real tests

I did this with the latest version.

[dmitri]

Got carried away a bit with latest optimizations and as a result the latest versions have too long key delays when navigating the menu. Will upload a new version which fixes this issue right after the midnight.

[Ken Forgettable]

Got carried away a bit with latest optimizations [snip]

There is about 45K left in flash - can you think of a use for this space (via the bootloader)?