Re: HAL user-land audio driver
Re: HAL user-land audio driver
- Subject: Re: HAL user-land audio driver
- From: "Mikael Hakman" <email@hidden>
- Date: Sun, 23 Mar 2008 14:00:27 +0100
- Organization: Datakonsulten AB
On March 20, 2008 10:11 PM, Jeff Moore wrote:
There are lots of processes that will load your plug-in. Basically, every
one that initializes the HAL. So you need to be sure to terminate all
those processes before you can fully delete your plug- in. The tricky ones
are coreaudiod and LoginWindow. They are always going to get
auto-launched, so it's hard to get the system in a state where they
aren't running.
I'm pretty lazy, so I usually do this by replacing the plug-in I'm
working on with the new one and rebooting. This sidesteps the issues with
making sure coreaudiod and LoginWindow are not running when the
replacement happens.
This seems to be the safest way. Following an advice given by others, I
tried to stop and restart coreaudiod after replacing a plug-in version with
new one without reboot. It works in the sense that a core audio application
uses the new code. Using Sound Preferences or AMS to set the plug-in as
default output doesn't work however. I see my plug-in on the list, I can
select it, and I can see that my new code is called, but my default choice
is not saved. Also when running iTunes (having AMS with my device selected
as default open) I can see that it calls my new code but then it somehow
reverts to standard default device. If I reboot everything seems to work ok.
Thanks/Mikael
_______________________________________________
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