DropSnorz OwlPlug ( Audio Plugin Manager) v1.26.0 Win Mac Linux [FREE]

Audio plugin manager. Small tool to manage VST / AU / LV2 plugins on Windows, MacOS and Linux. OwlPlug is an audio plugin manager. It provides a complete view of your plugin setup and simple tools to manage it. OwlPlug came from my hate of installing and managing audio plugins. The process is very annoying. I always wanted something simple that looks like dependency managers or online content store. I’ve started this just for fun… But because it was so simple to install plugins, I’ve discovered dozens of cool plugins just by using my own tool. So I realized this is not just a different way to install plugins, it’s a real opportunity to share and discover awesome free and open sourced plugins developed by the community.

All kinds of feedbacks are greatly welcomed.

Installation

Direct download (latest version)
Requirements: Windows 7 (64 bit) or later, macOS High Sierra or later.Browse binaries from the release section
Download and run the OwlPlug installer for your platform
.msi installer on Windows
.dmg file on macOS
.deb file on Linux
Run OwlPlug application
⚠️ Mac users, depending on your OS version, you may face an error mentioning that OwlPlug is damaged. You can fix this problem using a single command described on the wiki page.
Wiki page:

https://github.com/DropSnorz/OwlPlug/wiki/Troubleshooting

Features:

Plugins discovery:
OwlPlug can discover VST2, VST3 and AU Plugins. OwlPlug is compatible with all previously installed plugins as long as they are all in a specific root directory, for example C:/AudioPlugins. Additional directories can be configured if your plugin setup is fragmented on the filesystem.

After downloading Owlplug, you can still organize (add, move, delete, …) your plugins with a file explorer or with your favorite DAW without breaking anything.

Links creation:
A Link allows you to create and manage symlinks across your filesystem and plugin directories. With Links, you can access directories anywhere on your filesystem (Hard drive, USB keys, custom directories…) through a single root plugin directory. For example, you can configure a link named usb-drive in C:/AudioPlugins to target your usb hard drive D:/myPlugins. All plugins in D:/myPlugins will be accessible using C:/AudioPlugins/usb-drive. This feature may be useful for DAW that scans plugins from predefined or limited number directories. On some Windows version, symlinks creation may require admin privileges.

DAW Projects analysis:
OwlPlug can scan DAW projects to extract referenced plugins. Plugins references in project files are compared to plugins installed in configured directories. This way, users can quickly identify missing plugins required to open projects.

The list of compatible DAWs is available in the documentation

The documentation:

https://github.com/DropSnorz/OwlPlug/wiki/Projects-and-DAW-Support

Explore and download Plugins:
OwlPlug can be connected to several remote sources to download plugins. A Remote Source is a collection of downloadable plugins that can be installed locally. OwlPlug can be configured to use any compatible third-party store in Explore Tab > Sources > Add a new source….

Here are some recommended compatible sources.

OwlPlug Registry ⭐
OwlPlug official plugin registry for Free or Open Source plugins

kind: registry
url: https://registry.owlplug.com/registry.min.json
StudioRack Registry ⭐
Studiorack registry plugins for OwlPlug.

kind: registry
url: https://owlplug.github.io/owlplug-studiorack-registry/registry.min.json
Discover more plugin sources in this wiki page.

How to distribute my plugins on OwlPlug ?
(Recommended) Distribute your plugins using on the official OwlPlug Registry. You can find more information on how to proceed in the registry github repository.

Setup and host a custom remote source to distribute multiple plugins, following the registry specification.

(Deprecated) Setup and host a custom remote source to distribute multiple plugins, following the store specification. The store specification is not actively maintained, you should use the registry spec instead.

GitHub

Avatar-Foto

Bam

Musician since about 45 years(various flutes, synths) Composer since 1986 admin of the forum + blog Music-Society

Schreibe einen Kommentar

Deine E-Mail-Adresse wird nicht veröffentlicht. Erforderliche Felder sind mit * markiert