Re: MIDI Rescan: Panther vs. Jaguar
Re: MIDI Rescan: Panther vs. Jaguar
- Subject: Re: MIDI Rescan: Panther vs. Jaguar
- From: Pete Gontier <email@hidden>
- Date: Wed, 21 Apr 2004 11:28:59 -0700
circa 4/19/04 18:53, Doug Wyatt <email@hidden> 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?
>
... 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.
Did this. Nobody is calling it. Extra confusing. I looked in the prefs file
and sure enough the devices are present.
>
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 ...
I don't remember how this is specified (CFPlugInTypes, probably), but my
QueryInterface routine asserts version 2.
>
If necessary, I will investigate further based on more info ...
I don't have more info yet, though I did discover what appears to be an
unexpected oddness in IOKitLib. I'm getting interest messages for deleted
notifications, and this was causing an assertion failure in my code of which
I wasn't aware, and that in turn was causing an unexpected exception during
the stop/start sequence. I'll work around that issue and then revisit the
disappearing devices.
--
Pete Gontier
http://www.m-audio.com/
_______________________________________________
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.