shipping an aggregate device
shipping an aggregate device
- Subject: shipping an aggregate device
- From: Alex Sheh <email@hidden>
- Date: Wed, 27 May 2009 13:49:48 -0700
- Acceptlanguage: en-US
- Thread-topic: shipping an aggregate device
Hi,
Currently
we implement an AudioHardwarePlugInInterface, which aliases any audio
driver on the system, by basically forwarding any audio requests onto the
aliased audio driver. However, since AudioDeviceRead() has been deprecated
and the documentation recommends using an aggregate device instead, we are
planning on rewriting our plugin as an aggregate device.
Does this sound like
the correct approach? Or are there any limitations that I would run into
in terms of replicating this "aliased audio driver/forwarding audio requests"
behavior with an aggregate device? Is it possible to build the aggregate
device into a bundle, so that we can ship it to the customer as a
plugin?
I found a posting
called "Creating Core Audio aggregate devices programmatically" at http://www.thismuchiknow.co.uk/?p=51.
Does anyone know of other documentation that would be
helpful?
Thanks for your
help!
-
Alex
_______________________________________________
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