You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
this also begs the question what to do if a plugin falls into multiple categories. maybe one could symlink or copy the plugin to multiple locations.
The text was updated successfully, but these errors were encountered:
she11sh0cked
changed the title
[feat] generate a folder structure based the plugins information
[feat] generate a folder structure based on the plugin information
Jan 1, 2022
Thank you for this feature suggestion. I have a feature idea in mind that may fit this one.
A user could create a Set, and each Set contains a plugin hierarchy. It can be customized by the user or automatically generated based on metadata (creator, tags, etc...). For example :
A manually created Set called live containing only plugins for live performance.
Original plugin files (.vst, .dll, docs, etc...) are never moved by OwlPlug, they stay where there are installed to avoid breaking anything. For the first example, symlinks would be created like this:
When a Set is saved/synchronized OwlPlug creates a hierarchy of symlinks from the Set configuration. All symlinks are referencing the base install path for plugin files and directories.
OwlPlug tracks changes for plugins referenced in a Set if the original plugin has been moved or deleted.
one could select multiple plugins and generate folder structures for them.
i imagine there are two types of folder structures most people want:
manufacturer-based:
category-based:
this also begs the question what to do if a plugin falls into multiple categories. maybe one could symlink or copy the plugin to multiple locations.
The text was updated successfully, but these errors were encountered: