Re: App + Device Driver (having design issues)
Re: App + Device Driver (having design issues)
- Subject: Re: App + Device Driver (having design issues)
- From: Jeff Moore <email@hidden>
- Date: Tue, 11 May 2010 12:04:08 -0700
There is no corresponding function call. The IO buffer size that an app uses is specific to that app. The driver has to be prepared to deal with clients with different buffer sizes.
That said, you can get an idea about what the clients are doing by watching the buffers that they register with the Engine's user client. That can be done either by subclassing IOAudioEngineUserClient and overriding the registration methods or you can override IOAudioStream::addClient in your subclass of IOAudioStream.
On May 11, 2010, at 11:50 AM, John Johnson wrote:
> Thank you Jeff and Paul. A combination of two audio streams and an IOUserClient subclass was exactly what I needed!
> Just one more question here. It seems my device driver does not respond to setting kAudioDevicePropertyBufferFrameSize. What is the corresponding function that is called in the driver when this property is being set? And how would I implement this functionality?
>
--
Jeff Moore
Core Audio
Apple
_______________________________________________
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