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
Checking parameter setting
/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?
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.
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?
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
Most Users Ever Online: 152
Currently Browsing this Page:
Guest Posters: 1
Newest Members:jcayetano, Alex, oneday, Phelan Kane, audiocoder, agel, Makai, Abyz, Nonlinear, IgorVish
Moderators: W Pirkle: 508
Administrators: Tom: 74, JD Young: 80, Will Pirkle: 0, W Pirkle: 508, VariableCook: 3