Trait PluginScanner 

pub trait PluginScanner {
    type Plugin;

    // Required methods
    fn scan(&self) -> Result<Vec<PluginInfo>>;
    fn scan_path(&self, path: &Path) -> Result<Vec<PluginInfo>>;
    fn load(&self, info: &PluginInfo) -> Result<Self::Plugin>;
}

Discover and load audio plugins of a single format.

Thread safety

Scans are off the audio thread. They walk the filesystem, open dylibs, and can take seconds (a fresh AU scan touches 100+ plugins on a typical Mac). Hosts should never call scan from a real-time context — wrap in a worker thread if you need a non-blocking discovery flow.

Required Associated Types

type Plugin

Concrete plugin type this scanner produces. Always implements crate::Plugin for at least one sample precision.

Required Methods

fn scan(&self) -> Result<Vec<PluginInfo>>

Scan default OS plugin directories for this format. Each format wrapper picks the conventional paths (~/Library/Audio/Plug-Ins/CLAP and /Library/... for CLAP on macOS, the registry on Windows, etc.).

Errors

I/O errors propagate from the directory walk; per-plugin load failures are logged and skipped rather than aborting the scan.

fn scan_path(&self, path: &Path) -> Result<Vec<PluginInfo>>

Scan a specific directory. Useful for hosts that bundle their own plugins or that want to test against a known fixtures directory.

Errors

Same as PluginScanner::scan.

fn load(&self, info: &PluginInfo) -> Result<Self::Plugin>

Materialise an instance from the PluginInfo returned by scan / scan_path. Most wrappers actually dlopen the plugin’s dylib at this point; expect file I/O.

Errors

crate::Error::PluginNotFound when info.unique_id doesn’t match anything in this scanner’s index; crate::Error::LoadFailed on dylib / signature errors.

Dyn Compatibility

This trait is dyn compatible.

In older versions of Rust, dyn compatibility was called "object safety".

Implementors