Another config tool

[elrules]

:?: Could Mac users tell us what MCT features currently work with your MD?

I second that

[acspike]

As I'm waiting for the possible open source release of MCT, I've been trying to learn some Java and learn how to talk to the MegaDrum. I've created a minimal example of detecting the MegaDrum and returning the firmware version. I don't have delusions that this is beautiful code or even idiomatic Java, but it still might give someone a leg up as they do their own investigations.

[Ken Forgettable]

learn how to talk to the MegaDrum.

I'll make a sober assessment tonight thanks, and keep it up!

Are you MAC or linux?

[acspike]

I'm using Ubuntu linux. I did get a chance to test it once on Windows XP last week too.

[Ken Forgettable]

:?: Could Mac users tell us what MCT features currently work with your MD?

I second that

Can fuzzysnuggleduck, kimouette, userfriendly, or any other MAC troopers find the time to see if acspikes little proggy (above) works for them and report back with the OS version please.

[userfriendly]

I'm probably going to need a MegaDrum for that, so I'll have to wait until the kit reaches me.

As soon as I have it (and have built it, of course), I can test on OS X 10.5.6, Ubuntu Studio 8.04 and Windows XP.

[acspike]

Mac users/java experts take note of lines 82-85 and line 88 where I'm "discovering" the megadrum.

Code: Select all

      MidiDevice.Info[] mdi = MidiSystem.getMidiDeviceInfo();

      //For Linux:
      String checkFor = "MegaDrum";
      //For Windows:
      //String checkFor = "USB Audio";
      for (int i = 0; i < mdi.length; i++) {
         String info = mdi[i].getName()+": "+mdi[i].getDescription();
         if (info.indexOf(checkFor)>-1) {
...


I don't know what name the os reports for the megadrum on Mac (I'm sure it is on the forum somewhere) so checkFor will almost have to change. Also note that the program doesn't work well on linux. After I send a sysex message and get a reply I have to power cycle the megadrum before I can send and receive another sysex set (though it continues to get short messages from the drum).

[fuzzysnuggleduck]

I'll have a chance to test tomorrow. Hopefully I remember.

[Ken Forgettable]

acspike stuff works just dandy, I can't make it misbehave on XP - but check out the comments in MidiDevice.java - written my morons for use by idiots!

... my interpretation is:

+ A MidiDevice can be opened explicitly as well as implicitly.

+ A MidiDevice should always be closed explicitly, even if it has been opened
implicitly.

+ Explicit access is accomplished by calling open and close on a MidiDevice
instance.


... but the ladies seem to go to say

+ Implicit opening is accomplished by calling
javax.sound.midi.MidiSystem#getReceiver MidiSystem.getReceiver and
javax.sound.midi.MidiSystem#getTransmitter MidiSystem.getTransmitter.

... and

/**
* Obtaining a Transmitter with this method does not
* open the device. To be able to use the device, it has to be
* opened explicitly by calling #open.
*/
public Transmitter getTransmitter() throws MidiUnavailableException;


... then they twist the knife

/**
* 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;

I don't like to see a woman compromised

[acspike]

Ken, I think you're trying to tell me something, but I'm not sure exactly what.

In regard to closing MidiDevices I think you make a very valid point that the devices need to be closed unconditionally. I should move lines 132-138 outside of the if statement and check for nullness individually. Good eye.

I have to confess that I have no idea what you are telling me about the MidiDevice.open() method and the various women involved with it. Are you saying that I should store up a Transmitter and Receiver object at the same time I open the devices? Are you recommending that I explicitly close the Receiver and Transmitter?

You have to lay it on the line for me. I'm a java newb here!