# AudioUnit won't get detected by auval or Logic

**URL:** <https://forum.juce.com/t/audiounit-wont-get-detected-by-auval-or-logic/39140>\
**Category:** Audio Plugins\
**Created:** [May 1, 2020, 11:57pm UTC](https://forum.juce.com/t/audiounit-wont-get-detected-by-auval-or-logic/39140 "2020-05-01T23:57:54Z")\
**Posts on this page:** 6\
**Page:** 1

<div class="post-metadata">

**Author:** ![Laphicet](https://sea2.discourse-cdn.com/flex026/user_avatar/forum.juce.com/laphicet/32/7198_2.png) [@Laphicet](https://forum.juce.com/u/Laphicet)\
**Post date:** [May 1, 2020, 11:57pm UTC](https://forum.juce.com/t/audiounit-wont-get-detected-by-auval-or-logic/39140/1 "2020-05-01T23:57:54Z")

</div>

I’ve been struggling to develop a JUCE-based AU plugin for Logic for a while now. Up until now, I’ve been manually moving the \*.component from the home library to /Library, or else auval does not detect it. I’m getting really peeved doing this because a good chunk of my development time has been going to doing that every time I compile. I tried bumping the minimum supported OS to High Sierra which is my employer is having me use and can’t update, but nothing. Other third party \*.components in home library are detected just fine, but for my plugin auval always wants it in /Library.

However, if this is because I’m building debug instead of release, that raises another problem: How can I test my plugin if I can only run it with the debug info optimised out?

---

<div class="post-metadata">

**Author:** ![anoesisaudio](https://sea2.discourse-cdn.com/flex026/user_avatar/forum.juce.com/anoesisaudio/32/1132_2.png) [@anoesisaudio](https://forum.juce.com/u/anoesisaudio)\
**Post date:** [May 2, 2020, 12:04am UTC](https://forum.juce.com/t/audiounit-wont-get-detected-by-auval-or-logic/39140/2 "2020-05-02T00:04:51Z")

</div>

Have you seen this thread?

> [@Installing new Audio Units requires restart in High Sierra](https://forum.juce.com/t/installing-new-audio-units-requires-restart-in-high-sierra/26753/45):
>
> killall -9 AudioComponentRegistrar

---

<div class="post-metadata">

**Author:** ![Laphicet](https://sea2.discourse-cdn.com/flex026/user_avatar/forum.juce.com/laphicet/32/7198_2.png) [@Laphicet](https://forum.juce.com/u/Laphicet)\
**Post date:** [May 2, 2020, 1:54am UTC](https://forum.juce.com/t/audiounit-wont-get-detected-by-auval-or-logic/39140/3 "2020-05-02T01:54:22Z")

</div>

Hmmm… will I need to do this on every new compilation?

---

<div class="post-metadata">

**Author:** ![anoesisaudio](https://sea2.discourse-cdn.com/flex026/user_avatar/forum.juce.com/anoesisaudio/32/1132_2.png) [@anoesisaudio](https://forum.juce.com/u/anoesisaudio)\
**Post date:** [May 2, 2020, 2:04am UTC](https://forum.juce.com/t/audiounit-wont-get-detected-by-auval-or-logic/39140/4 "2020-05-02T02:04:25Z")

</div>

Yes. Add it in your build script if you use one or just run that one line in the terminal.

---

<div class="post-metadata">

**Author:** ![daniel](https://sea2.discourse-cdn.com/flex026/user_avatar/forum.juce.com/daniel/32/790_2.png) [@daniel](https://forum.juce.com/u/daniel)\
**Post date:** [May 2, 2020, 1:28pm UTC](https://forum.juce.com/t/audiounit-wont-get-detected-by-auval-or-logic/39140/5 "2020-05-02T13:28:58Z")

</div>

Actually no, once the plugin is found in the registry, the recompiled versions are automatically used when restarting the DAW. There is no need to kill the AudioComponentRegistrar again, unless you created a new plugin.  
But you can add it as safety measure into your build script, afaik it won’t have any negative effects.

---

<div class="post-metadata">

**Author:** ![Laphicet](https://sea2.discourse-cdn.com/flex026/user_avatar/forum.juce.com/laphicet/32/7198_2.png) [@Laphicet](https://forum.juce.com/u/Laphicet)\
**Post date:** [May 3, 2020, 12:28am UTC](https://forum.juce.com/t/audiounit-wont-get-detected-by-auval-or-logic/39140/6 "2020-05-03T00:28:15Z")

</div>

Awesome! Thanks! I’ll go ahead and try it.