relationships between javax.sound.midi and com.apple.audio.midi
relationships between javax.sound.midi and com.apple.audio.midi
- Subject: relationships between javax.sound.midi and com.apple.audio.midi
- From: Michael Harbour <email@hidden>
- Date: Sat, 3 Jan 2004 11:07:31 +0000
Hello. Hope you are well. Happy new year etc.
Could anybody shed some light on the relationship between the pure
javax.sound.midi package in the J2SE and the implementation or not of
them on Mac OSX, possibly using core audio? Is it possible to send and
receive MIDI events via USB through 5-pin MIDI cables to external
devices using the pure-Java solution?
If the pure-java solution is not implemented by Apple, why not? is
there like a fundamental mismatch in the API designs that cant be
hooked up? With every respect to Apple, and really wanting to be
informed - i wonder - why would anyone take the strategic design
decision to write a third-party midi app in the CoreAudio MIDI API
rather than the javax.sound.midi if it was available?
If the pure-java solution is in fact implemented, should a USB MIDI
interface show up in the call
javax.sound.midi.MidiSystem.getMidiDeviceInfo() ? I cant seem to see my
USB MIDISport with this.
Finally, would anyone who is familiar with both OO and procedural
programming agree with me that the rendering of the Java
com.apple.audio.midi API over the native C API should have been done
quite a bit more OO? There's still way way too much static methods,
krappy konstants and passing uninitialised references into methods for
the filling up thereof. The javadoc-style commentary is really sparse,
too.
Many thanks
Mike Harbour
_______________________________________________
coreaudio-api mailing list | email@hidden
Help/Unsubscribe/Archives:
http://www.lists.apple.com/mailman/listinfo/coreaudio-api
Do not post admin requests to the list. They will be ignored.