Plug-in won't load AU GUI in Logic, fails initialisation load for VST3 in Reaper, but works in Plug-In host

Audio Plugins
1

I am working on a plug-in at the moment that successfully builds and runs in the juce plug-in host. It functions as I’d expect and allows me to step through the code following the logic I expect and the GUI is represented accurately.

I got an AU build of the plug-in to work in Logic, with the GUI appearing. At this point it loaded the GUI in Logic Pro (didn’t run any functionality tests) and works as expected in JUCE plug-in host as a VST3. Despite this, it fails to load in Reaper (ends up in the plug-ins that failed to scan section). I can’t get Reaper to log the results of the vst-log for some reason but my vst64.ini file has this information below (where the X’s are a similar format character combination to the one above):

reaxcomp.vst.dylib=0044D15FA7F7DA01,1919252579,ReaXcomp (Cockos)
my_vst_name.vst3=XXXXXXXXXXXXXXXX

Also, I have a local application that acts as a VST (and au) host. It doesn’t find the AU module which is strange. It deactivates the VST3 due to it failing stages at initialisation.

Since then, Logic has stopped loading the GUI. It merely opens up a window with the name of the plug-in.

Could anyone point a light on what might be going wrong for me here?

2

I would suggest running auval on your plugin.

3

Thanks for getting back, I did run the auval test and it passed validation. One thing I am aware of is that I changed the project name some time ago and I wonder if this is still existing somewhere in the compilation (though I can’t seem to find any reference to it).