Hi psynical, thank you for this feedback and ideas. This really helps me to keep motivated to work on OwlPlug.
how's the development coming along?
Well... I'm extremely busy with my full-time job and some personal stuff. So unfortunately, Owlplug's development has slowed since July 2019. It's really hard for me to grant time for this project which is very frustrating because I'm still determined to work on it.
It seems "Native Discovery" feature is not stable. I don't know if the problem is caused by a system compatibility issue or a corrupted plugin.
- Does the native discovery fails when executed on an empty directory? Does it fail when executed on a directory with only one plugin from a "trusted" company like Steinberg, NI ?
I'll try to add more logging in the next release.
Is there any way to add multiple VST2 directories? I have some in program files/vst and others in steinberg/vst, for instance.
Not really, but you can define a root VST2 directory and creates links (a bit like shortcuts) from OwlPlug UI to another directory on your file system. Something like this:
Code: Select all
├── steinberg -> C:/Program Files/Steinberg
└── others -> C:/Program Files/VSTPlugins
What if you were to base the organization and activation using a shortcuts directory? Like don't uninstall plugins, just remove their shortcut from the Owlplugs re-org'd folder? Does that make sense?
I think I get the point. Owlplug will have to work with two directories, let's say an install
directory where all plugins are stored and a workspace
directory for the current active plugins. In the workspace
directory plugins are just shortcuts to the install
folder. When the user deactivates a plugin, only the shortcut is removed and DAWs only use the workspace
folder to retrieve plugins.
This is a really great idea. It's a bit complex because I've designed OwlPlug to work with an existing plugin setup no matter how it's organized. In any case, this is a very elegant way to handle plugin enabling/disabling.
There could also be a great opportunity for a steam-like community which would be used for doing meta-data tagging of all the plugins, so that clicking on any plugin in the app would give the user a tag-cloud, which they could then use to create their organized vst shortcut directory.
I agree, community tools for at least reviewing and tagging would be great. It's on the roadmap. I also want to work on a dynamic OwlPlug main store. A place where all developers can submit their plugins for being available on OwlPlug.
I'm currently working on a minor update this month. It will add few fixes and some analytics features that will help me to understand how OwlPlug is used in practice.
I will keep this thread updated with the latest Owlplug news.