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

[feat] generate a folder structure based on the plugin information #123

Open
she11sh0cked opened this issue Jan 1, 2022 · 1 comment
Open
Labels
Type: Feature New Feature

Comments

@she11sh0cked
Copy link

she11sh0cked commented Jan 1, 2022

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:

VSTs/
├─ Celemony/
├─ FabFilter/
├─ IZotope/
├─ iZotope, Inc./
├─ SoundToys/
├─ Unknown/
├─ Xfer Records/

category-based:

VSTs/
├─ Analyzer/
├─ Delay/
├─ Distortion/
├─ Dynamics/
├─ Effect/
├─ EQ/
├─ Fx/
├─ Instrument/
├─ Mastering/
├─ Restoration/
├─ Reverb/
├─ Spatial/
├─ Synth/
├─ Unknown/
├─ Vocals/

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.

@she11sh0cked 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
@DropSnorz
Copy link
Owner

Hello @she11sh0cked,

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.
      .../live/Serum
      .../live/fx/Roth-Air
      .../live/fx/EQ8
      
    • An automatically generated Set called studio containing all plugins by tags.
      .../studio/Instrument/Serum
      .../studio/Synth/Serum
      .../studio/Compressor/Roth-Air
  • 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:
    .../live/Serum -> C:/Program Files/Common Files/VST3/Serum
    .../live/fx/Roth-Air -> C:/Program Files/Steinberg/VST/Roth-Air
    .../live/fx/EQ8 -> C:/Program Files/Steinberg/VST/Roth-Air
    
  • 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.

@DropSnorz DropSnorz added the Type: Feature New Feature label Jan 1, 2022
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

No branches or pull requests

2 participants