Re: Accessing other audio devices from a user-land driver
Re: Accessing other audio devices from a user-land driver
- Subject: Re: Accessing other audio devices from a user-land driver
- From: Daniel Vollmer <email@hidden>
- Date: Thu, 14 Mar 2013 10:47:10 +0100
Hi,
On 14 Mar 2013, at 05:17, Kyle Sluder <email@hidden> wrote:
> I'm thinking about writing a user-land audio driver that acts as a
> filter. I just want to affect audio on its way out of the system.
[snip]
> So… am I up the river without a paddle here? I really can't do anything
> with the audio data other than send it to IOKit? What's the point of
> having a user-land audio driver if I can't do anything with the data
> other than send it to the kernel?
My approach for a similar problem is to select my user-land driver as System Default output
(to capture it) and then provide a normal, user-land application that reads data from input of
my driver (which is then processed output it received) and forward that to a real output device.
I haven't gotten around to this application part yet, because AUGraph restricts you to one
AUHAL per graph, and I need the AUHAL input from the user-land driver, and the AUHAL
of the real output device. Shuffling the data around manually with callbacks is of course
possible, but I haven't bothered yet.
Daniel.
_______________________________________________
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