# AU plugin not being recognized with Juce 1.5

**URL:** <https://forum.juce.com/t/au-plugin-not-being-recognized-with-juce-1-5/4201>\
**Category:** Audio Plugins\
**Created:** [August 22, 2009, 9:46am UTC](https://forum.juce.com/t/au-plugin-not-being-recognized-with-juce-1-5/4201 "2009-08-22T09:46:29Z")\
**Posts on this page:** 7\
**Page:** 1

<div class="post-metadata">

**Author:** ![in23d](https://avatars.discourse-cdn.com/v4/letter/i/46a35a/32.png) [@in23d](https://forum.juce.com/u/in23d)\
**Post date:** [August 22, 2009, 9:46am UTC](https://forum.juce.com/t/au-plugin-not-being-recognized-with-juce-1-5/4201/1 "2009-08-22T09:46:29Z")

</div>

I just compiled the example Mac plugin I have a JuceDemoPlugin.component however it is not showing in Aulab, logic Pro or Live . AUval -a does not see it however it compiled fine.

Also, what is JuceDemoPlugin.component.dSYM created and where is the plugin’s .exp file? Thanks for any help!

---

<div class="post-metadata">

**Author:** ![jules](https://avatars.discourse-cdn.com/v4/letter/j/41988e/32.png) [@jules](https://forum.juce.com/u/jules)\
**Post date:** [August 22, 2009, 9:55am UTC](https://forum.juce.com/t/au-plugin-not-being-recognized-with-juce-1-5/4201/2 "2009-08-22T09:55:18Z")

</div>

No such problems here, so not sure what to suggest…

.dSYM is just the debugging info, and why do you want an .exp file? It’s not needed!

---

<div class="post-metadata">

**Author:** ![in23d](https://avatars.discourse-cdn.com/v4/letter/i/46a35a/32.png) [@in23d](https://forum.juce.com/u/in23d)\
**Post date:** [August 22, 2009, 10:50am UTC](https://forum.juce.com/t/au-plugin-not-being-recognized-with-juce-1-5/4201/3 "2009-08-22T10:50:58Z")

</div>

Thanks jules, after compile the JuceDemoplugin.component is placed in the plugin componenets folder automatically is this the correct one or do I need to replace it with the one in the release directory?

I also had to delete PluginLibrary.xcodeproj from the project as I don’t need RTAS and it was giving errors before the delete

Also, I am not changing anything else, I am compiling the demo plugin as it is, target is OS 10.5, release mode.

Do i need to modify the info.plist in any way? The Bundle OS Type code is TDMw, is it right?

Thanks again for any help.

---

<div class="post-metadata">

**Author:** ![jules](https://avatars.discourse-cdn.com/v4/letter/j/41988e/32.png) [@jules](https://forum.juce.com/u/jules)\
**Post date:** [August 22, 2009, 1:04pm UTC](https://forum.juce.com/t/au-plugin-not-being-recognized-with-juce-1-5/4201/4 "2009-08-22T13:04:47Z")

</div>

Did you have a look through the how-to file about building plugins? Most of this stuff is covered there, I think, and something in there might be a useful hint.

---

<div class="post-metadata">

**Author:** ![in23d](https://avatars.discourse-cdn.com/v4/letter/i/46a35a/32.png) [@in23d](https://forum.juce.com/u/in23d)\
**Post date:** [August 23, 2009, 10:37am UTC](https://forum.juce.com/t/au-plugin-not-being-recognized-with-juce-1-5/4201/5 "2009-08-23T10:37:09Z")

</div>

Ok got it, thanks, working now

---

<div class="post-metadata">

**Author:** ![peterv](https://sea2.discourse-cdn.com/flex026/user_avatar/forum.juce.com/peterv/32/151_2.png) [@peterv](https://forum.juce.com/u/peterv)\
**Post date:** [August 30, 2009, 1:52pm UTC](https://forum.juce.com/t/au-plugin-not-being-recognized-with-juce-1-5/4201/6 "2009-08-30T13:52:50Z")

</div>

I also cant get the AU to be visible by the Plugin Host. I use the the JuceDemoPlugin and I build it as it is, with removing PluginLibrary.xcodeproj. I checked the HowTo file but I cant see the hint.

thanks  
peter

---

<div class="post-metadata">

**Author:** ![jules](https://avatars.discourse-cdn.com/v4/letter/j/41988e/32.png) [@jules](https://forum.juce.com/u/jules)\
**Post date:** [August 31, 2009, 8:39am UTC](https://forum.juce.com/t/au-plugin-not-being-recognized-with-juce-1-5/4201/7 "2009-08-31T08:39:39Z")

</div>

I’ve also occasionally seen problems with the plugin not being recognised properly (and showing up in finder as a normal folder instead of a component), but have never figured out why. Seems to be something to do with the OS not realising that it’s a component, but it seems to magically fix itself if you delete or copy it, and kick the OS into rescanning it.
