Re: User space driver plug-in problems on Tiger
Re: User space driver plug-in problems on Tiger
- Subject: Re: User space driver plug-in problems on Tiger
- From: Stéphane Letz <email@hidden>
- Date: Wed, 1 Jun 2005 12:50:23 +0200
------------------------------
Message: 4
Date: Tue, 31 May 2005 13:10:36 -0700
From: Jeff Moore <email@hidden>
Subject: Re: User space driver plug-in problems on Tiger
To: CoreAudio API <email@hidden>
Message-ID: <email@hidden>
Content-Type: text/plain; charset=ISO-8859-1; delsp=yes; format=flowed
Catching up on the back log. Sorry for the delay.
kAudioHardwareBadDeviceError is only ever returned when the
AudioDeviceID in question can't be found. How did you get that ID?
The device ID was read in a preference file that was written by
another component that was using kAudioHardwarePropertyDevices
property.
Anyway it seems that accessing most of CoreAudio API function fails:
In my plug-in Initialize function, i do :
err = AudioHardwareGetPropertyInfo(kAudioHardwarePropertyDevices,
&outSize, &outWritable);
and the returned outSize value is 0 instead of 4...
I'm still compiling my plug-in on Panther and basically the plug-ins
still implements the kAudioHardwarePlugInInterface2ID version of the
kAudioHardwarePlugIn interface. Could this be the problem?
I see also that the kAudioHardwarePlugInInterface3ID defines some new
entry-points like InitializeWithObjectID, ObjectShow....
Is is absolutely necessary to implements all of them when the plug-in
is running on Tiger?
What about Panther compatibility?
Thanks
Best Regards
Stephane Letz
_______________________________________________
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