KVR Audio

valhallasound · Post by **valhallasound** » Fri Sep 02, 2011 6:02 pm

Hi all,

I'm having beta testers check the latest version of ValhallaRoom. A few of them are reporting AU Validation issues, but they are erratic. For the people getting crashes, this is what auval shows:

Code: Select all

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

However, most of my users don't report this, and the ones that are getting the crashes often find that a reboot and/or rescan fixes things. I can't get the error on any of my machines.

Is this a permissions issue? And if so, would it have something to do with updates to my PackageMaker script? I have updated my version number in the script from 1.0.4 to 1.0.8. The fact that the script was at 1.0.4, while the latest released version of ValhallaRoom was 1.0.7, makes me think that the version number issue must have created bugs in the past. I've also changed the machine I build things on, but the PackageMaker and Xcode versions are the same.

Thanks for any help,

Sean Costello

Sampleconstruct · Post by **Sampleconstruct** » Sat Sep 03, 2011 10:56 am

As I was eager to check out the new algos I tried again to install it but no luck - in both 32 Bit and 64 Bit modes AU validation in Logic fails on both my machines, one being a Mac Pro 8 core the other one being a Macbook Pro. I refuse to delete my Plug-In caches for now as rescanning hundreds of Plugs takes time and I need to work right now.

valhallasound · Post by **valhallasound** » Sun Sep 04, 2011 11:37 pm

Sampleconstruct wrote:As I was eager to check out the new algos I tried again to install it but no luck - in both 32 Bit and 64 Bit modes AU validation in Logic fails on both my machines, one being a Mac Pro 8 core the other one being a Macbook Pro. I refuse to delete my Plug-In caches for now as rescanning hundreds of Plugs takes time and I need to work right now.

I've just sent you V1.0.8, beta 4. If you can give this installer a try, it would be greatly appreciated. I'm actually happy that you haven't deleted the plugin caches, as I want to fix things without having to suggest this option to users.

Also: WTF is up with the whole AU Validation and plugin caching in Logic? Ableton Live doesn't cache the plugins, and opens up WAY faster than Logic with the same plugin set. And the AU Validation won't catch bugs that cause a plugin to crash. Meanwhile, auval spits out an error number, and I haven't been able to find ANY documentation as to what this error number means.

Sean Costello

Sampleconstruct · Post by **Sampleconstruct** » Mon Sep 05, 2011 1:51 am

I ran the new installer (beta 4) with no luck, again AU validation failed - then I manually deleted the 2 AU components from HD/Library/Audio/Plug-Ins/Components - reinstalled and then it worked and passed the validation. So I didn't have to delete the AU cache after all but obviously the new installer didn't overwrite the old components properly...

Sampleconstruct · Post by **Sampleconstruct** » Mon Sep 05, 2011 3:11 am

And now I tried to install it on my studio machine the Mac Pro 8-core and axactly the same thing happened:
First validation failed, then I quit Logic, deleted the Au components manually, reinstalled and then validation worked fine. So there seems to be a pattern here

valhallasound · Post by **valhallasound** » Tue Sep 06, 2011 10:25 pm

So it sounds like the installer should delete the .component files before installing the new versions. Or is this a profoundly bad idea?

Sean Costello

yeahtuna · Post by **yeahtuna** » Sat Sep 10, 2011 4:39 am

Sounds like you might not be updating the .plist file to inform Logic that your plugin is a new version. If it thinks it's the same version, then it won't rescan and it'll use the copy it has cached instead.

valhallasound · Post by **valhallasound** » Sat Sep 10, 2011 4:44 am

yeahtuna wrote:Sounds like you might not be updating the .plist file to inform Logic that your plugin is a new version. If it thinks it's the same version, then it won't rescan and it'll use the copy it has cached instead.

How does one update the .plist file? Or, to say the same thing from another angle, how would I be compiling my AU in such a way as to NOT be updating the .plist file? Or is this more of an installer issue?

Thanks,

Sean Costello

yeahtuna · Post by **yeahtuna** » Sat Sep 10, 2011 4:54 am

The .plist file should contain a value for the version of your plugin. CFBundleVersion or something like that... actually there are two values. Might have to search to find them out. I'm not by my machine right now. You can create some user-defined macros corresponding to the version of your plugin and make references to them in your .plist file...That'll save you from having to update version information in too many places.

aradaz · Post by **aradaz** » Sat Sep 10, 2011 5:45 pm

Try Iceberg to make the installer.

valhallasound · Post by **valhallasound** » Sat Sep 10, 2011 7:25 pm

aradaz wrote:Try Iceberg to make the installer.

I've looked into it. Slow going through the manual, but that has more to do with my brain this week than the manual itself.

I've been reviewing my PackageMaker script, and the file owners and groups seem to be set seemingly randomly. I don't think that having the owner of a file being MY user name is a good idea. I've reset things, but PackageMaker REALLY likes to change things to other settings. I may end up using Iceberg.

Sean Costello

ralphb · Post by **ralphb** » Sun Sep 11, 2011 12:16 pm

Are you using PackageMaker GUI or the commandline tool? The commandline stuff works pretty well for me, I gave up understanding the GUI version. I can send you an example bash script if you're interested.

aradaz · Post by **aradaz** » Sun Sep 11, 2011 3:59 pm

I've experienced with the validation problem when making the installer on Mac OSX Tiger (10.4). So make sure you make the installer on MacOSX 10.5 or above.

Erratic issues with AU validation