Re: properties data size
Re: properties data size
- Subject: Re: properties data size
- From: Eric Gorouben <email@hidden>
- Date: Thu, 07 Mar 2013 20:53:55 +0100
Of course, you're right!
Thanks
Eric
Le 7 mars 2013 à 20:44, Jeff Moore <email@hidden> a écrit :
> Are you sure you are implementing the property correctly?
>
> By my calculations:
> 4 * sizeof(AudioStreamRangedDescription)
> = 4 * 56
> = 224
> != 160
>
> FWIW, it sounds like you are using sizeof(AudioStreamBasicDescription) rather than sizeof(AudioStreamRangedDescription):
> 4 * sizeof(AudioStreamBasicDescription)
> = 4 * 40
> = 160
>
>
> --
>
> Jeff Moore
> Core Audio
> Apple
>
>
>
> On Mar 7, 2013, at 11:30 AM, Eric Gorouben <email@hidden> wrote:
>
>> I have a strange problem with the properties data sizes in my AudioServer plugin.
>> For example, I implement the kAudioStreamPropertyAvailablePhysicalFormats property.
>>
>> In the GetPropertyDataSize proc, I give a 160 bytes answer (4*sizeof(AudioStreamRangedDescription))
>> But in the GetProperty proc, inDataSize is only 112 bytes (for the same inObjectID, of course).
>>
>> In another similar situation, I give 320 bytes as data size, and get only 280 for the data.
>>
>> What did I miss?
>
>
> _______________________________________________
> 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
_______________________________________________
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