Re: Need help deciding what kind of driver is most appropriate
Re: Need help deciding what kind of driver is most appropriate
- Subject: Re: Need help deciding what kind of driver is most appropriate
- From: Jeff Moore <email@hidden>
- Date: Fri, 18 Aug 2006 17:02:47 -0700
One caveat: If you want your plug-in to run on older systems where the
HAL doesn't support the version 3 API (which was new in Tiger), you'll
still need to support the AudioDevice and AudioStream calls.
On Aug 18, 2006, at 4:21 PM, Jeff Moore wrote:
On Aug 18, 2006, at 4:01 PM, Nick Hebner wrote:
The idea of what a HAL plugin actually is, is sort of a replacement
for the HAL that you interface with using the AudioHardwareXXX
functions.
These plug-ins are only hooked into the AudioObject, AudioDevice,
and AudioStream prefixed API calls. A version 3 plug-in can safely
ignore the AudioDevice and AudioStream calls provided it fully
supports the AudioObject calls. The AudioHardware prefixed API calls
aren't covered here.
I already know that the answer to this question is probably not
what I want it to be, but is there any way for the plugin to not
have to implement all of the HAL functionality, and have it provide
some default functionality like what you would get from the
AudioHardwareXXX functions normally? Can I call AudioHardwareXXX
functions to only extend portions of the HAL that I want to operate
differently?
Sorry. It doesn't really work that way. You are, for all intents and
purposes, responsible for the entire behavior of those API calls.
You have to implement them with the same semantics as the HAL
provides for other devices. It's definitely not for the faint of
heart.
--
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