• Open Menu Close Menu
  • Apple
  • Shopping Bag
  • Apple
  • Mac
  • iPad
  • iPhone
  • Watch
  • TV
  • Music
  • Support
  • Search apple.com
  • Shopping Bag

Lists

Open Menu Close Menu
  • Terms and Conditions
  • Lists hosted on this site
  • Email the Postmaster
  • Tips for posting to public mailing lists
Re: OSX audiounit Component's Bundle Version & auval
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: OSX audiounit Component's Bundle Version & auval


  • Subject: Re: OSX audiounit Component's Bundle Version & auval
  • From: Brian Willoughby <email@hidden>
  • Date: Fri, 14 Oct 2011 15:09:28 -0700

At one point in the history of CoreAudio, there was incomplete documentation of whether AudioUnit version numbers were supposed to be encoded as hexadecimal ("hex") or Binary-Coded Decimal (BCD). Thus, 3.10.1 might be 0x31001 or 0x30A01. I would not be surprised if there are still lingering bugs in the code. Also, I have no idea whether bundle version numbers, component version numbers, and AudioUnit version numbers are all on the same page.

If your problem persists, and it only happens with numbers 10 or greater in a version, then I suggest that you report this as a bug to Apple via bugreport.apple.com, along with documentation on how to reproduce the issue.

Brian Willoughby
Sound Consulting


On Oct 14, 2011, at 06:20, Oli Larkin wrote:
auval v1.6.1a1

i changed my CFBundleVersion version number to 3.1.1 which is what it should be really and that prints fine in auval

Component Version: 3.1.1 (0x30101)
Component's Bundle Version: 3.1.1

the reason I had a funky version number before was because I made a mistake with the CFBundleVersion for the standalone version of my product which is on the appstore, and if you make an error like that on the appstore you're screwed. Hence i needed to bump the version number.

I just wondered why a CFBundleVersion like "3.10.1" didn't register with auval


On 13 Oct 2011, at 20:20, tahome izwah wrote:
What version of auval is this? Mine (v1.6.1a1) simply prints

Component Version: 1.0.5 (0x10005)

No bundle version.

--th

2011/10/12 Oli Larkin <email@hidden>:
if my audiounit's CFBundleVersion in the info.plist is "3.10.1"

in auval it prints like this...

Component Version: 3.10.1 (0x30A01)
Component's Bundle Version: 0.0.0

is that a bug in auval or is the 3.10.1 an invalid CFBundleVersion?

_______________________________________________ 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
References: 
 >OSX audiounit Component's Bundle Version & auval (From: Oli Larkin <email@hidden>)
 >Re: OSX audiounit Component's Bundle Version & auval (From: tahome izwah <email@hidden>)
 >Re: OSX audiounit Component's Bundle Version & auval (From: Oli Larkin <email@hidden>)

  • Prev by Date: Re: CoreAudio vs CoreData
  • Next by Date: Mac64 linker error
  • Previous by thread: Re: OSX audiounit Component's Bundle Version & auval
  • Next by thread: How to use Time Code ?
  • Index(es):
    • Date
    • Thread