Desperately need help - I’ve been developing a simple plugin and suddenly my DAW (Logic X) can’t validate the plugin, and I can’t think of anything I’ve done to affect this (I was just twiddling Slider parameters at the time, and have un-twiddled them just in case but with no improvement on the situation).
Validation result on any new plugin I try to compile (my previously compiled plugins still work):
Manufacturer String: yourcompany
AudioUnit Name: willthiswork2
Component Version: 1.0.0 (0x10000)
* * PASS
--------------------------------------------------
TESTING OPEN TIMES:
COLD:
JUCE v5.3.2
FATAL ERROR: OpenAComponent: result: -1,0xFFFFFFFF
validation result: couldn’t be opened
This even happens with a fresh Projucer project. Anyone got any experience or knowledge to what’s going on here? This error message means nothing to me!
You might be onto something with that - It’s also sometimes similar; FATAL ERROR: OpenAComponent: result: -50,0xFFFFFFCE
It’s located in my local user library plugins folder. Tried putting it in HDD/Library/audio plugins folder, but couldn’t get it to appear at all by auval.
Thanks for more links - I’m going through them right now.
What sort of settings? There’s lots - broadly;
I’m compiling just for AU
Avoiding numbers in fields (someone else had this problem), otherwise all normal alpha symbols
Good point; likely very frustrating. One of the things that I noticed a bit ago had to do with deployment target, osx architecture, etc. not matching. Sounds like it, but just to be sure…are you using Projucer defaults or have you modified those?
If I were in this situation, I would build a VERY simple version of this project from scratch (which works) and then add a few things at a time and test along the way. Its a pain if you don’t do it from the beginning, but if your project is not huge, it may be easier than further head bashing.
Well it’s likely to be machine config issue then, rather than anything in JUCE. Sorry that doesn’t narrow it down too much.
A shortcut to validation is running auval from the command line. If you do
auval -a
that will validate all plug-ins on your system. You can then look at the identifiers next to your plug-in to validate just a single one. For the JUCE plug-in demo on my machine that would be
Thanks t0m - I’ve run the auval before with no luck. Just ran it with a couple of tutorial plugins, and hit the same problem.
Suspect you’re right about it being a machine (or at least a not-code) config problem. I was tweaking code that what I would not deem sensitive to causing this sort of headache!