App + Device Driver (having design issues)
App + Device Driver (having design issues)
- Subject: App + Device Driver (having design issues)
- From: John Johnson <email@hidden>
- Date: Fri, 7 May 2010 12:28:06 -0500
| Hey everyone. I'm building an app that works very closely with a kernel level device driver and Im having some design issues. Hopefully someone here can point me in the right direction.
The device driver I have built is very similar to Soundflower, i.e. it takes the output of a program and passes is through to the input of another. But I need something a little more than that.. I need the driver to be able to route sound to multiple applications. How Soundflower works is by saving audio from the clipOutputSamples() routine and supplying it in the convertInputSamples() routine. Pretty basic. The problem with is that it creates feedback loops if more than one app is sending output or receiving input, for obvious reasons. The design limits it to only two applications.
OK. So here is the Sounflower model:
And here is the model I need:
I have considered many ways of doing this, but I am unsure how to implement this design. If I use the Soundflower implementation in this model, a feedback loop will be created if audio is coming in to the main app at the same time it is sending audio out. I have considered many ways to solve this problem.. i.e. using multiple streams, or multiple audio engines. Multiple audio engines is probably best, but how can I access a specific engine of the device driver from CoreAudio api's, and insure that it gets passed through correctly?
I appreciate you reading this long-winded post and I sure appreciate any suggestions you could offer.
John |
_______________________________________________
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