Thread: AU validation
View Single Post
Old 02-26-2017, 07:39 AM   #4
JD Young
Human being with feelings
 
JD Young's Avatar
 
Join Date: Nov 2014
Location: Leiden, the Netherlands
Posts: 36
Default

Hi Tunca,

I’m by no means an expert on this, but I have had similar issues in the past caused by the following reasons:

- AU not validated when I had two GUI controls linked to the same parameter. I had to explicitly call ‘false’ as in SetDirty(false), in one of the GUI elements, instead of just SetDirty(), which has ‘true’ as default argument. (The AU plug-in worked fine initially in Reaper, but not in Logic. It didn’t validate though, because of some seemingly unrelated parameter inconsistency. It did successfully validate after my fix)

- I had some bundle ID issues, when the ID’s didn’t match in recource.h and the plist files.

- If you get inconsistent results over different systems, it’s possible your AU got blacklisted by the host after giving an error during load. (It could be another problem in combination with this as well.) It’s usually not very difficult to find the actual ‘blacklist’ in a host.

Not sure if this is any help, but it might give you some clues...

Cheers! JD
JD Young is offline   Reply With Quote