Built AU doesn't show up in DAWs

[mviljamaa]

So I was transferring a project I originally was making in Windows and VST format to OSX and AU and I'm having problem getting it run.

I had some problems getting the libraries I need properly included, but now they seem to be fine since the project compiles.

However, the built .component is not seen by any DAWs I've tried.

Any idea if it's because there's something wrong with the build still?

[earlevel]

Your plugin is in /Library/Audio/Plug-Ins/Components (or ~/Library...)?

[mviljamaa]

/Library/Audio/Plug-Ins/Components.

And other plug-ins in this folder are properly seen.

[stw]

Is it seen by auval?

[mviljamaa]

It now seems to occur on all duplicated (duplicate.py) Example projects, but not the original Example projects.

[mviljamaa]

Originally Posted by stw

Is it seen by auval?

How to use auval?

Writing auval -a doesn't bring my audio unit up, but brings up others in my Plug-ins/Components folder.

[mviljamaa]

There's something really strange.

By duplicating the same project (IPlugEffect), sometimes the resulting project compiles a .component that's seen by DAW, but sometimes it compiles a .component that's not seen by DAW.

So far it has seemed like it would be related to the name of the plug-in somehow. That some names are seen and some aren't.

???

[CaptnWillie]

Bump, have the same issue. Been updating target settings for the AU and nothing seems to help. In AU Labs it told me that it was an unidentified target, and Ableton Live can't populate it when I point to it.

[CaptnWillie]

It appears that auval is a useful tool to authenticate .components as Apple will certify an AU.

I can understand that my project somehow meets some of these criteria? For instance if I use a lookahead but I deleted my buffer, will that have some latency issue that would disallow AU certification even though the .component still compiles? I just cant see it in AU labs or Audacity.

[ynohtna]

Have you ensured that your plugins have got varying CFBundleIdentifiers, constructed from the BUNDLE_MFR & BUNDLE_NAME defines in resource.h?

[CaptnWillie]

I've got different values for both,

#define BUNDLE_MFR "CaptnWillie"
#define BUNDLE_NAME "HypeLimit"

what do you mean by varying? I see that there are the same values for bundle and for plugin_mfr/plugin_name