Writing a private device driver
Writing a private device driver
- Subject: Writing a private device driver
- From: Jeremy Bernstein <email@hidden>
- Date: Mon, 26 Dec 2005 19:12:44 +0100
Hello coreaudio-api -
I am trying to adapt the Phantom Audio Device driver to a specific
project. I am admittedly a newbie in the CoreAudio realm, although
I've been working with the QuickTime API for several years.
Ideally, I would like to be able to instantiate a variable number of
private, independent audio "devices" to facilitate communication
between 2 parts of my software (I need to stream audio out of a
QuickTime movie and into a more general audio signal processing
environment). I am more or less clear about how the basic
functionality needs to be implemented, thanks to the example project,
but:
- I can't determine if it is possible to create a "private" audio
device driver: that is, I don't want users to be able to use these
audio devices. As far as I can tell, I _have_ to create a virtual
device driver in order to use SetMovieAudioContext() for what I need
to do, but I'd like this private mechanism to remain private.
- I can't determine if it is possible to load multiple instances of a
driver on the fly. That is, I would prefer to instantiate and
initialize 1 (x-channel) stream for each request, rather than
assigning a hard upper limit by extending the AudioEngines array, or
by setting IOAudioStreamNumChannels to some fixed value. Ideally, I
would like to reload my device driver and create a new instance of it.
If any of this sounds interesting or possible, I'd love to know. If
any of it sounds completely impossible, but gets you thinking about
alternative solutions, I'd love to know that, too...
Thanks a lot -
Jeremy Bernstein
_______________________________________________
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