Re: implementing an AudioHardwarePlugin
Re: implementing an AudioHardwarePlugin
- Subject: Re: implementing an AudioHardwarePlugin
- From: Michael Dautermann <email@hidden>
- Date: Tue, 6 Feb 2007 22:02:06 -0800
Thanks for responding to me, Jeff.
On Feb 6, 2007, at 12:33 PM, Jeff Moore wrote:
2)
I created a CFPlugin project in XCode, gave the bundle a name
ending in ".plugin", a unique UUID into the Info.plist file for my
factory function and the kAudioHardwarePlugInInterface3ID UUID for
the CFPlugInType. After putting my new bundle into ~/Library/
Audio/Plug-Ins/HAL (or ~/Library/Audio/Plug-Ins/Components), I did
not see any of my printfs (e.g. in my Factory function, in my
QueryInterface function) in the console when I launched HALLab.
Am I using the wrong format for the CFPlugin or the wrong testing
app (just to see if I can get the component opened/enumerated)?
Sounds like your plug-in wasn't being found by the HAL as it is in
the wrong directory.
I put my CFPlugin into /Library/Audio/Plug-Ins/HAL, gave it the same
permission bits and root:group ownership as the iSightAudio.plugin,
launched HALLab and still did not see any telltale printfs showing up
in the console from my factory function or QueryInterface function.
Is HALLab the proper app to be testing my plugin with?
As for the UUID's in the plist file, I am using a CFPlugInType key of
"38D78A18-77A5-11D8-B8B8-000A9588787E" (the same as
kAudioHardwarePlugInInterface3ID) and this is also the string value
in the array associated with the key. My Factory function has a
unique UUID that I generated.
What else might be keeping my Factory or QueryInterface functions
from firing when I launch HALLab?
I'm sure it's been said before on this list, but I sure *wish*
there was a basic AudioHardwarePlugin sample project I could use.
THe request has been noted.
If it would help anyone out, maybe once I get this
AudioHardwarePlugin skeleton working, I could post it as a sample
project on my site.
Thanks again...
_______________________________________________
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