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 15:13:24 -0700
If clearing the AU cache helps, then my first suspicion is that you
did not change the official AudioUnit version number when you
released the latest version of your plugin. The system cannot tell
the old version from the new version unless you change the version
number. Maybe try 1.1.0 instead of 1.0.8?
Brian Willoughby
Sound Consulting
On Sep 2, 2011, at 13:56, Sean Costello wrote:
It seems that the problem goes away for some users when they clear
their AU cache, reboot, that sort of thing. This implies that it
isn't an issue with my plugin code proper, as it seems that code
bugs would show up for all people using the same OS/host (OS
10.6.8, Logic 9.1.5).
The esteemed Chris Randall has suggested that this has to do with
file permissions, which makes me think it has something to do with
the settings in my PackageMaker installer script. I'm not messing
with the permissions settings, but apparently these can be set in a
pseudo-random manner by PackageMaker.
Any suggestions on what might be going on here? A Google search
turns up plenty of posts with this issue, but no definitive solutions.
Also, any actual auval documentation, that shows what these error
codes mean? The only documentation I have found is the same as the
help file for auval. Which doesn't really help me out much.
On Sep 1, 2011, at 11:33 PM, Sean Costello wrote:
I am getting reports from beta testers that the latest version of
my plugin, ValhallaRoom, is failing AU Validation for some of
them. The problem it, I don't run into this issue on any of my OSX
machines. And users are reporting that the plugin works fine on
one machine that is running OS 10.6.8/Logic 9.1.5, and fails
validation on another machine with the identical OS/Logic version.
So, what are the common causes of failing AU validation? Is there
a document somewhere that can answer this question?
Thanks for your help,
Sean Costello
P.S. Here's a typical crash report:
validating Audio Unit ValhallaRoom by Valhalla DSP, LLC:
* * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * *
* * *
AU Validation Tool
Version: 1.6.1a1
Copyright 2003-2007, Apple, Inc. All Rights Reserved.
Specify -h (-help) for command options
* * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * *
* * *
--------------------------------------------------
VALIDATING AUDIO UNIT: 'aufx' - 'Ruum' - 'oDin'
--------------------------------------------------
Manufacturer String: Valhalla DSP, LLC
AudioUnit name: ValhallaRoom
Component Version: 1.0.8 (0x10008)
* * PASS
--------------------------------------------------
TESTING OPEN TIMES:
COLD:
FATAL ERROR: OpenAComponent: result: -50,0xFFFFFFCE
validation result: Öffnen fehlgeschlagen
updating properties of AU ValhallaRoom by Valhalla DSP, LLC...FAILED!
_______________________________________________
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