Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Support for multiple directories? #38

Closed
bmcclure opened this issue Jul 25, 2020 · 6 comments · Fixed by #115
Closed

Support for multiple directories? #38

bmcclure opened this issue Jul 25, 2020 · 6 comments · Fixed by #115
Labels
Type: Feature New Feature

Comments

@bmcclure
Copy link

Most of my VST plugins are under a single directory, but some of them have installers which don't allow reconfiguring the directory or are in other places for various reasons.

Is there some way I can specify multiple VST2 and VST3 directories to scan?

@DropSnorz
Copy link
Owner

Hi @bmcclure ! Thank you for using OwlPlug and sharing your feedbacks.

The Link feature is here for your use case. You can create Symlinks with OwlPlug UI to "merge" all your folders into a single root directory. Here is an example for mounting x86 and x64 VST folders on Windows: https://github.com/DropSnorz/OwlPlug/wiki/Configuration

Most plugin hosts can handle Symlinks. This way, you can also configure one global plugin folder in your DAW preferences.

@DropSnorz DropSnorz added the Type: Question Further information is requested label Jul 28, 2020
@bmcclure
Copy link
Author

Oops, completely missed your response until I saw it was closed.

While using symlinks sometimes works, not all plugins work this way--when loaded via symlink, some plugins get confused about their installation directory and either complain or fail to load.

While symlinks are an ideal solution, multiple directories would still allow for more flexible configuration options supporting all use cases, especially in combination.

@DropSnorz
Copy link
Owner

Hi @bmcclure

There is only one directory per plugin type to support plugin download in one click from the "Store" tab.
We can imagine a primary directory used for installation by default and multiple optional directories picked for the scan. When installing a plugin, if a primary directory is not configured, a target directory can be chosen from the list.

@bmcclure
Copy link
Author

Ah, that reasoning makes sense in the context of the store. Having a primary directory and then optional scan directories sounds like a good solution!

@DropSnorz DropSnorz reopened this Jan 11, 2021
@DropSnorz DropSnorz added Type: Feature New Feature and removed Type: Question Further information is requested labels Jan 11, 2021
@DropSnorz
Copy link
Owner

Hi @bmcclure

I've implemented this feature on OwlPlug 1.18.0
Now, no extra symlinks are needed for this use case 🙂

@DropSnorz DropSnorz linked a pull request Nov 22, 2021 that will close this issue
@bmcclure
Copy link
Author

Thanks so much, this is awesome news!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Type: Feature New Feature
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants