• 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: Java CoreMIDI vs javax.sound vs MMJ etc
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: Java CoreMIDI vs javax.sound vs MMJ etc


  • Subject: Re: Java CoreMIDI vs javax.sound vs MMJ etc
  • From: William Stewart <email@hidden>
  • Date: Mon, 17 Mar 2008 16:33:08 -0700

The best check for this is to see if the device is showing up in Audio MIDI Seup's MIDI pane and that it can be seen by native applications (AU Lab in /Developer/Applications/Audio is one that you can try when you add an AU Instrument track)

If it does show up there, than that seems like it is a java.midi bug.

If it doesn't show up there, then that is a problem with the device and CoreMIDI in general

Bill

On Mar 14, 2008, at 10:53 PM, Jason Proctor wrote:

hi,

after switching to Intel recently i noticed that my Java CoreMIDI applications compiled with deprecation warnings and generated "platform not supported" exceptions when run.

i googled around and found a post on this list from William Stewart late in 2006 advising a poster with similar issues to (essentially) use the javax.sound.midi interface instead.

i thought going to the standard Java interface was reasonable so i knocked up some code and found that... my hardware MIDI interface, which works fine from native CoreMIDI applications and which used to work fine from Java CoreMIDI, isn't visible at all via the MidiSystem.getMidiDeviceInfo() call. the only devices returned are the Real Time Sequencer and Java Sound Synthesizer.

i went looking around again and found MMJ, and gave that a try. that too saw my hardware interface without any issues.

now call me old-fashioned for having a hardware MIDI interface, 5- pin DIN cables, and real hardware, but given that all these APIs (i assume) basically call the underlying native CoreMIDI API, shouldn't the javax.sound.midi implementation show the same device list as the other Java APIs?

thanks,
j

MBP 1.83
MacOS 10.4.11
Emagic AMT8
etc

_______________________________________________
Do not post admin requests to the list. They will be ignored.
Coreaudio-api mailing list      (email@hidden)
Help/Unsubscribe/Update your Subscription:
This email sent to email@hidden

_______________________________________________ Do not post admin requests to the list. They will be ignored. Coreaudio-api mailing list (email@hidden) Help/Unsubscribe/Update your Subscription: This email sent to email@hidden
  • Follow-Ups:
    • Re: Java CoreMIDI vs javax.sound vs MMJ etc
      • From: Jason Proctor <email@hidden>
References: 
 >Java CoreMIDI vs javax.sound vs MMJ etc (From: Jason Proctor <email@hidden>)

  • Prev by Date: Re: Enable system volume when driver doesn't
  • Next by Date: Re: ExtendedAudioFile on iPhone
  • Previous by thread: Java CoreMIDI vs javax.sound vs MMJ etc
  • Next by thread: Re: Java CoreMIDI vs javax.sound vs MMJ etc
  • Index(es):
    • Date
    • Thread