That might be correct, but it still is not the proper way to
implement the kind of audio driver Mr. Dautermann is describing. As
I said in my previous email, this kind of driver needs to be
written in a two parts. First, there needs to be a daemon that
handles the actual interaction with the hardware. Then the HAL plug-
in and the vdig component communicate with the daemon using shared
memory and the IPC API of your choice (I prefer Mach IPC using MIG).
So taking your advice, I'll be adjusting the "big picture"
architecture into being a daemon pushing a video stream to a 'vdig'
and an audio stream to the audio plugin. Other than that we'll soon
have the possibility of hearing audio play through in HALLab, there
will still be the immediate issue that QTSetComponentProperty returns
a kAudioUnitErr_InvalidPropertyValue error .
B.T.W., thanks for that suggestion, Chandrasekhar!
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Coreaudio-api mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
http://lists.apple.com/mailman/options/coreaudio-api/email@hidden
