Re: Rép : User-land CoreAudio driver and Leopard
Re: Rép : User-land CoreAudio driver and Leopard
- Subject: Re: Rép : User-land CoreAudio driver and Leopard
- From: Jeff Moore <email@hidden>
- Date: Thu, 15 Nov 2007 15:07:48 -0800
On Nov 15, 2007, at 2:52 PM, Stéphane Letz wrote:
>This is going to fail if the Jack server crashes and never sends
the stop notification.
But the jack server never crash...(-: More seriously, using a
CFMachPort like described herehttp://developer.apple.com/technotes/tn/tn2050.html
would be better?
Yup. Basically, it works like this: First, the server creates a port
of some kind and registers it such that clients can look it up. The
best way to do this is with launchd. Then the client then can
boostrap_lookup the server port and ask for a notification for when
the port goes away. This notification will fire regardless of how the
server exits, even if it crashes.
>You don't want to remove/restore the plug-in, you simply want to
make your device (and other objects) go away. Typically, this just
involves calling >AudioObjectsPublishedAndDied() for the objects
that are going away. Then when they come back, you get new object
IDs with AudioObjectCreate() and call
>AudioObjectsPublishedAndDied() to make the objects visible.
Thanks, I'll try
You can see the sequencing and mechanics of making theses calls in the
SHP_PlugIn's InitializeWithObjectID() and Teardown() methods. In your
case, you'll be doing this outside of the initialization/teardown of
your plug-in.
--
Jeff Moore
Core Audio
Apple
_______________________________________________
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