Re: More of Process
Re: More of Process
- Subject: Re: More of Process
- From: Jeff Moore <email@hidden>
- Date: Thu, 3 Nov 2005 15:14:04 -0800
I'll let someone else address your AU programming questions, but I'll
take a stab at answering your initial question about system-wide
processing.
First off, AudioUnits are not available to kernel entities. AU's are
user-land only constructs. So, if you intend on providing a pluggable
means of adding processing, you're on your own.
Secondly, there is no API for providing system-wide processing of
input or output data. The architecture we have for devices does not
lend itself to that sort of operation. So to implement it, you have
to, by definition, hack the system. For IOAudio-based devices, you'd
need to figure out how to glom onto each individual driver (in the
kernel) and inject your processing code into it's data handling.
Granted, the IOAudio family makes that somewhat easier by providing
the framework on which all the drivers are based, but it's still not
a job for the faint of heart and likely would not work with all bits
of hardware.
Another solution would be some kind of re-direction solution like
what AudioHijack or Jack do and, in a very primitive way, what the
AudioReflectorDriver sample code does. You'd redirect the data to
your processing code and then direct it at the actual bit of hardware.
On Nov 3, 2005, at 2:29 PM, john smith wrote:
Hi,
as I mentioned in a previous letter I'm unable to locate any
documentation for the kernel Process, except that "this is where
you process the audio".
--
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