"Megadrum Config Tool" released

[elrules]

Very nices suggestions Gastric. I will take more or less all of them for the next version.

I will also copy some other nice suggestions of Gabriel (to have them all together):

I use MCT a lot and I think it's brilliant. I do have a few suggestions, some features I would really like to see.

- To use both note name and MIDI note number. (eg. D2-38), or just a switch between them if adding extra digits means redoing the whole interface.

MIDI Monitor:
- For instant xtalk spotting - an option similar to this 'HOLD NOTE' but instead of removing all other notes, it simply colors them very distinctly, eg. red.

- For instant retrigger spotting - show the time gap between hits in a number above the note bar. Could be capped at 100 millisec. and show values above as +100.

I have zero knowledge of programing and therefore no way of telling if these wishes are silly or sane.


And a side question: is the 'FROM FILE' option broken? I never seem to get data from file...

Maybe it is better if I start a new thread with a Feature Requests...

[dmitri]

Dmitri, is there any firmware change apart from the HH pedal sysex?

One bit, AltFalseTrSupp, in "Miscellaneous configuration data".

[Ken Forgettable]

Code: Select all

  MegadrumConfigTool.log.info("Sending firmware...");
            mp.writeLongMessage(data, data.length, Common.SYSEX_SEND_TIMEOUT);
            MegadrumConfigTool.log.info("Firmware was sent. Now closing...");
            mp.close();
           
            return true;
        } catch (Exception e) {
            MegadrumConfigTool.log.error("Trying to send BIG SYSEX message<br>The error was: "+e.getMessage());
            return false;
        }
    }

Don't know if it applies but from MidiDevice.java:
/**
* Note that some devices, once closed, cannot be reopened. Attempts
* to reopen such a device will always result in a MidiUnavailableException.
*/
public void open() throws MidiUnavailableException;

Why - I dunno - what about leaving the device open until app exit.

Code: Select all

            //IF SECURITY SYSEX NEEDED, SEND IT NOW
            if(bootloader == Common.BOOTLOADER_WITH_SECURITY){
                MidiCommon.sendSysex(SysexRequest.firmwareUpdateRequest(),out);
                try{
                    Thread.sleep(1000);
                }catch(Exception e){}
            }

I have no trouble concatenating the security SysEx with the firmware and sending it all in one go with 100ms delays between bytes but I have noticed MidiOX can be made to fail with 'Delay after F7' set too high (Default 60ms) - so I'm suggesting reducing the sleep calls.

Also does MidiPort require you to handle the timecode? Somewhere in the MIDI system will be a dispatcher based on message time codes (java sequencer seems to reset these on opening a new pipe). Maybe they just go down the sink if you send them back-to-the-future?

[elrules]

Ey, dmitri, i have just released version 1.61. It has only small changes. I started by doing the Misc Settings work with the newest firmwares.

Can you try it to know if I programmed the misc sysex correctly?

[dmitri]

For AltFalseTrSupp you're setting/checking the wrong bit.

[elrules]

dmitri, I have changed it. I guess if AltSupr bit was wrong, then MIDI Speed was also wrong. I changed the byte where those bits are read/written from byte 11th to byte 8th.


LATEST NEWS!!

Megadrum COnfig Tool source code has been published. Just update yout MCT and you will see a button in the About dialog that will send you to the source code webpage, with info on how to download it and installing netbeans and so on.

(I hope I´m doing the right thing... ¬¬ )

[Ken Forgettable]

Fantastic - he he he.

(I hope I´m doing the right thing... ¬¬ )

You must be I got the download going just before your announcement

[dmitri]

It now sets/checks AltFalseTrSupp correctly. 20090516 firmware was not applying AltFalseTrSupp bit when received so I now released a new version. Btw, MegaDrum ignores the 'MIDI speed' bit in Sysex for obvious reason.

[Ken Forgettable]

Was it copied to the correct folder?

The file system on the server is case sensitive. So, there are now two files there:
MegaDrumConfigTool.jar 256544 30/03/2009
MegadrumConfigTool.jar 256581 25/04/2009

Shit dude! ok, i will upload it with an uppercase D

v1.6.1 svn project still only references MegadrumConfigTool.jar.
The stale MegaDrumConfigTool.jar file is still on the server.
If someone used an old jnlp file they will get unspecified behavoiur.

[elrules]

I changed it again to lower case.

And I also changed the install.jnlp file.

It updates correctly so don't worry.

The file with the upper case can be deleted

By the way, did you install all the netbeans crap and saw the code?