Re: what would cause QTSetComponentProperty to fail with a kAudioUnitErr_InvalidPropertyValue err?
Re: what would cause QTSetComponentProperty to fail with a kAudioUnitErr_InvalidPropertyValue err?
- Subject: Re: what would cause QTSetComponentProperty to fail with a kAudioUnitErr_InvalidPropertyValue err?
- From: Chandrasekhar Ramakrishnan <email@hidden>
- Date: Thu, 22 Mar 2007 15:42:32 +0100
Am 20.03.2007 um 22:30 schrieb Michael Dautermann:
I'd love to be able to fully use HALLab for my validation tool, and
the plug-in seems to do all the right things at least on the Info
dialog (the main dialog) of HALLab.
In the big picture, audio data for the plug-in comes from a
Quicktime 'vdig' component I've written that gathers video and
audio streams from a USB device. Because this 'vdig' needs to be
running, I don't think I can easily use HALLab play-through to do
validation. I have to do it this way as a USB device can only be
exclusively opened by one process / app at a time (and 'vdig'
counts for one and 'audi' for another).
I have an AudioHardwarePlugIn that uses AudioUnits and thus the
component manager internally. This works fine.
The one tricky aspect was instantiating the components at the right
moment -- I couldn't do this in the Initialize() method because I was
encountering problems with reentrancy and the ComponentManager when
the app requesting the HAL plugin uses the AUHAL audio unit. Moving
the component instantiation to a later point in time solves that.
- sekhar
--
C. Ramakrishnan
Illposed Software http://www.illposed.com
_______________________________________________
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