AU Version Info in QA 1408

• Subject: AU Version Info in QA 1408
• From: Jim Wintermyre <email@hidden>
• Date: Tue, 8 Feb 2005 20:09:21 -0800
• Delivered-to: email@hidden
• Delivered-to: email@hidden

From: William Stewart <email@hidden>
Subject: Re: AU version hex format
Date: Fri, 10 Oct 2003 17:58:00 -0700
To: William Stewart <email@hidden>

After some further discussions we decided to use BCD for numbers
greater than 9. Thus, 10.3.1 would be:
0x100301

2.3.1 would of course be the same in either case:
0x20301

Sorry for the confusion

Bill

On 10/10/2003, at 12:55 PM, William Stewart wrote:

> We're using straight Hex: Thus 2.3.1 would be:
> 0x20301
>
> The Validation tool will try to print out the version in this format -
> and checks that the number returned from the component resource is the
> same as the number returned from the GetComponentVersion API call (but
> it doesn't do any pass/fail logic on the format of these numbers)
>
> Bill
>
> On 09/10/2003, at 11:49 PM, Jim Wintermyre wrote:
>
>> Reviewing some earlier discussion on this, I came across the
>> following response from Bill to Marc:
>>
>>> > I was wondering, is it explained anywhere what exactly the format
>>> for
>>> > Audio Unit version values should be? I mean the value in the
>>> 'thng'
>>> > resource and returned by the Version component selector. For some
>>> > reason,
>>> > I was under the impression that the format was like this:
>>> >
>>> > 0xMMMMmmbb
>>>
>>> This is the format that we are using
>>
>> I have a question. Is this similar to the old 'vers' format where
>> the M/m/b numbers are actually in *BCD*? Should our component
>> version numbers be BCD or straight hex?
>>
>> Thanks,
>> Jim

• Prev by Date: Re: Getting notifications for AudioUnit ProcessBufferLists method
• Next by Date: Re: AU Version Info in QA 1408
• Previous by thread: Re: Using an AudioConverter to convert mono to stereo?
• Next by thread: Re: AU Version Info in QA 1408
• Index(es):
  • Date
  • Thread