AU not scanned by Logic

Discussion in 'Mac / Hackintosh' started by sd25, Jul 9, 2025 at 7:43 PM.

  1. sd25

    sd25 Newbie

    Joined:
    Mar 24, 2022
    Messages:
    1
    Likes Received:
    0
    Hi !
    I just installed BIAS AMP (I tried different versions found on audioz). The file "BIAS AMP 2.component" is visible under "Components" folder but Logic doesn't scan it...

    Could you help to understand why and apply a solution please?

    Fyi, when I opened the installer, OSX don't want to process and I had to go the security params to force the opening.


    Thanks!
     
  2.  
  3. Balisani

    Balisani Producer

    Joined:
    Oct 16, 2014
    Messages:
    169
    Likes Received:
    122
    That's one issue. I've had similar instances, with 3-4, maybe 5 plugins (out of..., 777 plugins in my components folder last I checked). The AUs load and run perfectly in other 64-bit DAWs (e.g., DSP-Quattro 5), but not in Logic.

    About which two things:
    • One of those (Roland) plugins works perfectly now - I upgraded to a new version (of the plugin), reinstalled, works 100%.
    • Half of the other plugins (part of a Lexicon bundle) run fine, but the other half is invisible to Logic.
    There's a theory about this: starting with Ventura or Apple Music, Mac OS has removed some iTunes libraries. Those libraries are theorized to have played a part in Logic scanning AUs adequately. I don't know if it's true or not, but it makes sense.

    I'm not sure why only select plugins of the same bundle were affected by these missing libraries - or how Roland and Lexicon tackled it - but it's possible some plugins are 'younger' (or more up to date) than others in the same bundle, or are coded by a different developer or team (one who is presumably more thorough than their peers).

    Bottom line: try to get the very latest version of a plugin, and if it's outside of your budget, at the very least download a trial or demo version, install it, and test/see if Logic does scan it. If it does, install the very latest sister site version available over it, and see how that helps.

    That's normal and unrelated. Google Codesign, or search the sister site - or do what you did.
     
  4. Creme

    Creme Kapellmeister

    Joined:
    Sep 20, 2015
    Messages:
    97
    Likes Received:
    53
    Location:
    Somewhere on the table
    i had some similar issue, for some reason launching logic in rosetta mode manually scanning those plugin then relaunch logic in ARM64 and the plugin were there.
     
  5. clone

    clone Audiosexual

    Joined:
    Feb 5, 2021
    Messages:
    8,753
    Likes Received:
    3,823
    Sometimes this works for plugins that do not authorize when first loaded as the ARM version. I've never seen it suggested as a way to force validation in Logic. On Intel Macs, OSX Validate All AUs is a small utility that will force validation by AUvaltool, but it almost never requires reboot. (Some really old plugins will still need a reboot).

    Otherwise, the old command line methods work fine for Intel. There is a nice writeup about an ARM method in the other place, but if it was intended to be shared here, it already would be.


    force validate plugin not scanned by logic
    ChatGPT said:


    To force Logic Pro to validate a plugin that wasn't automatically scanned, follow these steps:

    1. Reset and Rescan Using Plugin Manager
    This is the proper method to force Logic to retry scanning an AU plugin:

    1. Open Logic Pro.

    2. Go to Logic Pro > Settings (or Preferences) > Plug-In Manager.

    3. Find the plugin in the list. If it’s not showing, it means Logic hasn't detected it — more on that below.

    4. Select the plugin and click "Reset & Rescan Selection".

    5. If the plugin fails validation again, note the error message for clues.
    ️ 2. Manual Terminal Command (if Logic is skipping it completely)
    If the plugin doesn’t show in Plugin Manager at all (e.g., Logic is skipping the scan entirely), you can use this command to manually validate it:

    bash
    auval -v aufx Your Plugin’s AU Component ID

    • Example:
    bash
    auval -v aufx ABCD Manu

    Where:

    • aufx is the plugin type (can also be aumu for instrument or aumf for MIDI effect)

    • ABCD is the plugin's 4-letter code

    • Manu is the manufacturer's 4-letter code
    To find those codes, look inside the plugin's .component file located here:

    bash
    /Library/Audio/Plug-Ins/Components/

    Or use this command to list all installed AUs:

    bash
    auval -a

    3. Clear Audio Unit Cache (if plugin still won’t scan)
    If all else fails, reset the AU cache:

    bash
    rm ~/Library/Caches/AudioUnitCache/com.apple.audiounits.cache

    Then restart your Mac, launch Logic again, and it should rescan all plugins.

    Tips
    • Make sure the plugin is Apple Silicon compatible or running via Rosetta if needed.

    • Confirm you're using the AU format (Logic doesn’t support VST).

    • If you're using a plugin manager (like Waves Central, iZotope Product Portal), double-check that it's installed and activated correctly.
     
Loading...
Similar Threads - scanned Logic Forum Date
HELP ME PLEASE, I reinstall waves and I scanned it Software Feb 26, 2017
RealGuitar 4 doesn't get scanned by Ableton Live. Any Solution? Software May 8, 2016
VST3 not scanned Studio One Jan 16, 2016
Do with Kontakt what Logic's Auto Sampler Presets, Patches Yesterday at 12:17 PM
Bettermaker Bus Compressor AU crashing Logic Pro on macOS 15.5 – any solution? Software Jun 6, 2025
Loading...