• Open Menu Close Menu
  • Apple
  • Shopping Bag
  • Apple
  • Mac
  • iPad
  • iPhone
  • Watch
  • TV
  • Music
  • Support
  • Search apple.com
  • Shopping Bag

Lists

Open Menu Close Menu
  • Terms and Conditions
  • Lists hosted on this site
  • Email the Postmaster
  • Tips for posting to public mailing lists
Re: CoreMIDI via Java and MIDISport -- funny you should ask
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: CoreMIDI via Java and MIDISport -- funny you should ask


  • Subject: Re: CoreMIDI via Java and MIDISport -- funny you should ask
  • From: Scott Ruda <email@hidden>
  • Date: Mon, 27 May 2002 22:55:34 -0700

On Monday, May 27, 2002, at 10:07 PM Joshua Strickon <email@hidden> wrote:

I have been having similar problems with this through jni. I am writing my
gui in java but using coreaudio and midi natively through jni. The data
never even makes it into java as part of my application.

I'm curious why you have chosen to do this yourself via JNI instead of using the Apple supplied CoreMIDI/Java implementation. I already had a JNI lib written to get MIDI (OMS) plumbed up to Java for OS 9 and I chose not to port it to OS X and instead opt for using the CoreMIDI /Java approach. I figured that Apple had essentially already done the JNI work for me in OS X and any problems they were having I would probably have also in any JNI implementation I could write. Your experience seems to confirm that assumption. I refactored my Java code to use a factory method which returns one of my JNI based objects in OS 9/Win and a CoreMIDI/Java based object for OS X.

I am also a bit curious as to why Apple chose to write their own Java MIDI implementation when there is already a Sun developed one in Java 2 which is standard on OS X. My MidiPort factory can create those too now (which can be used in Windows), but I have found that my MIDISport USB interface does not show up in the available device lists in OS X Java - just the built-in soft synth. I've considered extending the Sun MIDI API and making my CoreMIDI Java ports redirect through the Sun API (by implementing custom derivations of their MIDI Transmitters, Receivers and Devices) just for consistency at the application layers of my code, but I already had all the JNI code in there and I had to refactor to get the runtime choice anyway, so the current factory approach is <now> working, albeit with the problems mentioned. Of course that approach won't do any good either if the CoreMIDI/Java part itself doesn't work.

Scott
_______________________________________________
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.

  • Prev by Date: Re: coreaudio-api digest, Vol 2 #139 - 4 msgs
  • Next by Date: Re: CoreMIDI via Java and MIDISport -- funny you should ask
  • Previous by thread: Re: CoreMIDI via Java and MIDISport -- funny you should ask
  • Next by thread: Re: CoreMIDI via Java and MIDISport -- funny you should ask
  • Index(es):
    • Date
    • Thread