Re: Allowing a user-space driver to be the default system
Re: Allowing a user-space driver to be the default system
- Subject: Re: Allowing a user-space driver to be the default system
- From: Jeff Moore <email@hidden>
- Date: Wed, 30 Mar 2005 13:02:27 -0800
On Mar 30, 2005, at 4:50 AM, Stéphane Letz wrote:
I don't understand here. When using HALLab, I see that "Built-in
audio" can be hogged. What do you mean by "they can't be hogged"?
I mean that hog mode can't be owned by any process for the given device.
My device *can* be selected as a default input/output/system using
HALLAB and when i select it as default input/output/system, the
property is notified to already running CoreAudio application that
correctly switch to my device.
The only thing that does not work is that the "my device as default
input/output/system" state is not properly saved in the system.
What else should I check?
The HAL stores the default device's UID in the user's preferences. Is
the UID of your device always the same? If not, the HAL would not be
able to match what it stored in the prefs with your device.
Is there a precise list of error code that would have to be
returned for each property?
There really isn't much in the way of documentation for what you are
doing at all.
--
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