Re: Common Causes of fatal errors during AU Validation?
Re: Common Causes of fatal errors during AU Validation?
- Subject: Re: Common Causes of fatal errors during AU Validation?
- From: Brian Willoughby <email@hidden>
- Date: Fri, 02 Sep 2011 17:14:27 -0700
If your CoreAudio engine code changed in the slightest, or even if
you just compiled the same code with a new Xcode, different compiler
or options, then you need to change the version of the audio engine.
The GUI is completely independent of the audio engine, so you can't
get by with only changing the GUI version unless the audio engine is
exactly the same - we're talking binary-compare identity. Even then,
it might confuse some other piece of software if both versions are
not changed.
Brian Willoughby
Sound Consulting
On Sep 2, 2011, at 16:45, Sean Costello wrote:
Well, for the incremental beta updates I send to testers, I have
only been incrementing the version number in the GUI. So the plugin
is still at version 1.0.8, but the GUI shows 1.0.8b3 in the corner,
using my own string display.
On Sep 2, 2011, at 4:43 PM, Brian Willoughby wrote:
You mentioned both the audio engine version and the GUI version;
are both being updated? Not sure that it would matter if the GUI
hasn't changed, but it's worth checking.
On Sep 2, 2011, at 16:18, Sean Costello wrote:
I should clarify my overly caffeinated text:
The beta testers would all have ValhallaRoom 1.0.7 installed on
their systems. The new beta has a version number of 1.0.8.
On Sep 2, 2011, at 4:10 PM, Sean Costello wrote:
I've checked my code and the various version numbers I can see
when I view the files in the .component directory, and all of
the version numbers have been incremented to 1.0.8, versus the
1.0.7 version that the beta testers would have. Plus, for some
of my beta updates, I've been incrementing the version number in
the plugin GUI only, yet people who jump through the hoops to
get the plugin validated are able to see the beta updates no
problem, even with the same 1.0.8 number. It is the people going
from 1.0.7 to 1.08 that are reporting the issue.
_______________________________________________
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