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: patrick machielse <email@hidden>
- Date: Mon, 05 Sep 2011 22:24:00 +0200
Op 5 sep. 2011, om 22:10 heeft Sean Costello het volgende geschreven:
> I am pretty sure that the bug my users are encountering is somewhat related. One of my users consistently is unable to validate the latest plugin versions after running the installer, where he is installing over the top of an existing installation. If he goes and deletes the .component "files," and then runs the installer again, things validate for him no problem.
>
> So...what is the fix? Is this a PackageMaker issue, as I suspect? Is there some permissions/overwrite flag that I should be setting, or should I "touch" the plugin folder, or should I use a script in the installer to delete all the files before I install them? Will switching over to Iceberg fix things?
It's not a PackageMaker issue.
I ran into this because I run auval as part of my AU sub-projects. Copying to and removing the units from .../Audio/Plug-Ins/Components/ seems to confuse the 'magic' loading of the audio units at runtime. Touching the Components folder 'clears out the cache' and does a full component search next time. Or at least that's my theory…
I think this started (for me) somewhere with 10.6.
Touching the Components folder as a final step in your PackageMaker install may fix it.
p.
--
Patrick Machielse
Hieper Software
http://www.hieper.nl
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