• 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: MIDI Rescan: Panther vs. Jaguar
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: MIDI Rescan: Panther vs. Jaguar


  • Subject: Re: MIDI Rescan: Panther vs. Jaguar
  • From: Doug Wyatt <email@hidden>
  • Date: Mon, 19 Apr 2004 21:53:44 -0400

I can think of one Jaguar-Panther difference in CoreMIDI in this area. It marks driver-owned devices offline before calling Start. This was to fix a bug where devices created by drivers which are no longer installed would show up as being online. One obvious side effect is that a driver that fails to mark its devices as online on every call to Start (e.g. one that only does this the first time start is called?) would now have its devices appear offline.

But if your devices are disappearing ... ! I can't explain that because the only way for a device to completely disappear is for someone to call MIDISetupRemoveDevice, and no one is supposed to call that except AMS, and it should only (and does only, AFAIK) do that in response to the user deleting the device.

I suggest running MIDIServer under gdb (make sure no MIDI apps are running and no other MIDIServer is running first), setting a breakpoint on MIDISetupRemoveDevice, and see if it gets hit -- if it is, the backtrace will tell us whether an application or a driver is making the call.

Or is your driver using the v1 driver API?(FindDevices etc.) If memory serves, you're not, but it's something to check. Check your interface UUID's ...

If necessary, I will investigate further based on more info ...

Doug

On Apr 19, 2004, at 19:52, Pete Gontier wrote:

Recent (unreleased) changes to my MIDI driver have broken the Rescan button
in Audio MIDI Setup under Jaguar. From a user's perspective, my devices
simply disappear. From a debug-log-reader's perspective, my driver gets a
stop message followed by a start message which seems to do all the right
things. (My logs are fairly detailed, as those of you who have debug builds
are probably painfully aware by now.) Indeed, on Panther, the devices do not
disappear. Obviously, something I changed recently disagrees with Jaguar,
and I am not seeking to assign blame to anyone but me, but is there some
difference between Jaguar and Panther of which I should be aware?
_______________________________________________
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.


  • Follow-Ups:
    • Re: MIDI Rescan: Panther vs. Jaguar
      • From: Pete Gontier <email@hidden>
References: 
 >MIDI Rescan: Panther vs. Jaguar (From: Pete Gontier <email@hidden>)

  • Prev by Date: Re: getc?
  • Next by Date: frame count, audio output unit
  • Previous by thread: MIDI Rescan: Panther vs. Jaguar
  • Next by thread: Re: MIDI Rescan: Panther vs. Jaguar
  • Index(es):
    • Date
    • Thread