Re: App + Device Driver (having design issues)
Re: App + Device Driver (having design issues)
- Subject: Re: App + Device Driver (having design issues)
- From: "Paul Sanders" <email@hidden>
- Date: Fri, 7 May 2010 21:41:09 +0100
|
> I need a way for the main app to send (output) audio to the driver and
the driver to know that it is intended for App 1 and route it accordingly.
Well, SoundFlower appears to applications as more than one
audio device (2 channel and 16 channel in their case, but that's a
detail). Would this approach not work for you? If you appear to
applications as 2 separate audio devices that gives you 2 independent,
um, pipelines let's call them. What more do you need? Or is the
issue that you want the destination app to be selected from your driver, rather
than the other way round? I don't think you can achieve that in
kernel mode. Possibly not in user mode either, at least not without some
unpleasant and fragile hacks.
Paul Sanders.
|
_______________________________________________
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