AudioHardwarePlugIn vs AudioServerPlugIn
AudioHardwarePlugIn vs AudioServerPlugIn
- Subject: AudioHardwarePlugIn vs AudioServerPlugIn
- From: Bertrand Van Kempen <email@hidden>
- Date: Fri, 09 Aug 2013 11:46:14 +0200
- Thread-topic: AudioHardwarePlugIn vs AudioServerPlugIn
Hi,
I'm a new CoreAudio driver developer; I "inherit" of a CoreAudio driver (HAL plugin) for a network protocol.
The driver works under 10.7 but it has some issue under 10.8 and Sandboxed application.
I have a look on CoreAudio.framework and noticed that the AudioHardwarePlugIn.h says that, starting in 10.8 AudioHardwarePlugin is deprecated.
So, I'm wonder if I have to port the driver to AudioServerPlugin to have my plugin working properly in 10.8 and OSX Maveriks?
Is AudioServerPlugin will be mandatory in next release of OSX?
Are only AudioServerPlugin drivers work with SandBoxed applications?
If I understand well the bigger difference between AudioHardwarePlugIn and AudioServerPlugIn is that AudioServerPlugIn doesn't call the Host at each new IOProcess (for example triggered by an interrupt) but now it is the Host which ask to the plugin to process IO at a predicted time: right?
If true, do you know how values returned by GetZeroTimeStamp() must be precise? What is the jitter allowed?
I only found documentation in AudioServerPlugIn.h and some explanations on email@hidden but I must admit that this does not allow me to understand all.
Could you point me to documentation?
Thanks a lot to help a poor new CoreAudio developer ;-),
Bertrand van Kempen
_______________________________________________
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