Log In
Register
Home
Topic RSS
I've run into some problems when trying to validate my AU
when I ran "auval -v aufx ABCD ABCD" it would return:
----------------
Bad Max Frames - Render should fail
ca_require: inFramesToProcess <= mMaxFramesPerSlice TooManyFrames /Users/samferguson/Desktop/DelayTroll/AUBase.cpp:1360
from AU (0x80596062): 'aufx' 'ABCD' 'ABCD', render err: -10874
PASS
Checking parameter setting
Using AudioUnitSetParameter
Using AudioUnitScheduleParameter
/usr/bin/auval: line 11: 1430 Segmentation fault: 11 arch -x86_64 /usr/bin/auvaltool "$@"
-----------------
I have tried to solve it myself but to no avail, any ideas?
Sam
Hmmm. I've never seen this from a RackAFX ported AU project. Which version of RackAFX are you using for this?
- Will
Offline
I get the
Bad Max Frames - Render should fail
PASS
And then continues on to validate successfully. I've just ignored that. 
Not sure if it's relevant to your issue as mine does not give the other errors you see.
Well, the Bad Max Frames test will PASS if the test fails, which it does here and that is normal.
The problem is the seg fault that occurs during the AudioUnitScheduleParameter test which looks like an uninitialized pointer or other non-existent object access. There are a couple of things to try:
1) get the new Beta version (use Contact form and I'll send you a password) -- the Make AU function was overhauled in the beta, in part to handle thread-sync issues, and might fix your issue
2) since the error involves the AU Parameters (which correspond to your RackAFX UI variables) you could try removing the controls and then doing the port to AU; this should now pass validation. Then you can add the controls back one at a time until you find the one that is causing this
Do you have any out-of-the-ordinary UI controls?
Sorry I don't have more info but I've never see this failure before - I've seen many auval fails during testing and implementation of RackAFX's Make AU function and there is always a reason and usually simple fix; the problem is that you have to sort of guess what's going on because you can't easily debug auval.
- Will
That's a helpful clue when I was making the GUI I lost a tab switch container inside another tab switch container but with an origin outside the size of the parent switch container, essentially off screen. I couldn't see it so I kind of ignored it... I thought I'd try to delete that first and see if that's what was causing the issue but when I tried to open it up in xcode I got this message:
"Project Delay Troll Debug.xcodeproj cannot be opened because the project file cannot be parsed"
It also gives me that message when I try to open the make VST xcode project, whether it is on my mac or my friend's. I suspect this is unrelated as it has nothing to do with auval but a problem none the less.
I do have a few custom Cview stuff going on, they are for display only but they would also be likely suspects. If it's not one of those or the lost tab switch container then I'll probably try the new Beta. I have 102 controls so I'm not eager to add them all in one at a time but will do it if necessary. But in the mean time any thoughts on the "cannot be parsed" issue?
Sam
Update:
So I got the new Beta version and that solved the "cannot be parsed" issue and the auval issue, the only odd thing is that now when my project loads all the Enum lists default to the last item in the list and not the first as it did before, but when I load up the AU in logic it seems to be the right way around so no harm no foul I suppose.
I am still getting errors when I try to build the VST on my mac, but I'll post that in the VST forum
-Sam
Offline
I'm wondering if anyone has any ideas as to what might cause the auval cold open test to fail.
I've built a number of plugins and built VST3s and AUs. I have a Silicon M1 mac but I've made a set of plugins built to target the Intel x86_64 platform (with the parameter -arch x86_64 passed to xcodebuild). These all work on my M1, with Big Sur, but when a user tested these on an Intel Mac running MacOS High Sierra 10.13.6, two of the plugins failed to load. I asked the user run auval for me and got the following output:
$ auval -v aufx RELQ DOOM
AU Validation Tool
Version: 1.6.1a1
Copyright 2003-2013, Apple Inc. All Rights Reserved.
Specify -h (-help) for command options
--------------------------------------------------
VALIDATING AUDIO UNIT: 'aufx' - 'RELQ' - 'DOOM'
--------------------------------------------------
Manufacturer String: Doomsville Soundscapes
AudioUnit Name: Reliq
Component Version: 2.0.0 (0x20000)
PASS
--------------------------------------------------
TESTING OPEN TIMES:
COLD:
FATAL ERROR: OpenAComponent: result: -1,0xFFFFFFFF
I'm pretty sure these are all correctly notarized now, and another M1 user has successfully tested that set of builds, notarized using the same notarization scripts, and other plugins built the same way to run on Intel architecture could load without any problem.
Any ideas what might cause the above would be very welcome. Thanks. Searching for this error on the web produced no useful results.
Running the same auval command on my development Mac passed:
* * PASS
--------------------------------------------------
AU VALIDATION SUCCEEDED.
--------------------------------------------------
Most Users Ever Online: 152
Currently Online:
6 Guest(s)
Currently Browsing this Page:
1 Guest(s)
Top Posters:
Chaes: 56
Skyler: 48
StevieD: 46
Derek: 46
Frodson: 45
Peter: 43
TheSmile: 43
Nickolai: 43
clau_ste: 39
jeanlecode: 37
Member Stats:
Guest Posters: 1
Members: 768
Moderators: 1
Admins: 6
Forum Stats:
Groups: 13
Forums: 42
Topics: 842
Posts: 3347
Moderators: W Pirkle: 689
