Re: custom properties plugin
Re: custom properties plugin
- Subject: Re: custom properties plugin
- From: Laurent Cerveau <email@hidden>
- Date: Wed, 26 Jun 2002 10:41:06 +0200
This is a bug and it should be fixed in Jaguar. Some properties will
however be passed as it might be interesting for the plugin to override
them.
You should be able to do a workaround it the following way , by simply
returning an error .
OSStatus AudioDriverPlugInDeviceSetProperty( AudioDeviceID inDevice,
const AudioTimeStamp* inWhen,
UInt32 inLine,
Boolean isInput,
AudioDevicePropertyID inPropertyID,
UInt32 inPropertyDataSize,
const void* inPropertyData){
OSStatus theResult;
theResult = kAudioHardwareUnknownPropertyError;
switch (inPropertyID) {
case kAPropertyThatMyPluginLikes:
//something like
theResult = IORegistryEntrySetCFProperty.....
theResult = noErr;
break;
default:
break;
}
return theResult;
}
Laurent
On Wednesday, June 26, 2002, at 09:03 AM, Jason Bagley wrote:
>
I have a basic custom property plugin for my audio driver, and despite
>
what the docs say, it is being called for every property. The way I
>
interpret the docs, it seems only those properties which are not known
>
to
>
core audio will be passed to a driver's plugin.
>
>
Is there a way to get the default property behavior for the common
>
properties?
>
>
Is this a bug which will be fixed in Jaguar?
>
>
Thanks,
_______________________________________________
coreaudio-api mailing list | email@hidden
Help/Unsubscribe/Archives:
http://www.lists.apple.com/mailman/listinfo/coreaudio-api
Do not post admin requests to the list. They will be ignored.