Organization ideas

[JohnKesko]

Just found out about the Owl, this is exactly what I have been looking for.

A few feature requests/ideas:
Add a few static or be able to dynamically add text boxes in the information panel when you click on the plugin for the user to add text in.
This is useful to organize for example licenses/serial numbers and which website they are from.

Next thing would be able to export all invented plugins, the information about each one into .csv, .xlsx. Useful to get an overview of what plugins you want to use when you upgrade or install a new computer.

[DropSnorz]

Hello @JohnKesko , thank you for your post here.

I've already thought to implement custom metadata (description, field, tags...) to users' plugins. But I have difficulties implementing it. The main problem is how to track plugin moves and deletions outside Owlplug. Custom user-defined properties at the plugin level are done on PluginFootprint which is based on the absolute plugin path on the filesystem. For example, custom metadata will be bound to a specific path, like /path/myPlugin.vst. If you move the plugin using a file explorer to /new/path/myPlugin.vst and resync, OwlPlug will see 2 actions:

• Addition of new Plugin on path /new/path/bar/myPlugin.vst, and bind metadata from PluginFootprint(/new/path/myPlugin.vst)
• Deletion of Plugin on path /path/myPlugin.vst

OwlPlug should resolve PluginFootprint(/path/myPlugin.vst) here, but I can't guarantee that's it's truly a move and that the user expects metadata to follow. So... re-organizing all your plugins may break all your custom descriptions and fields 😢

For the export feature, I agree, it would be great to export a plugin set up in a structured format. This may come soon, I've already worked on something like this with the current work done on draft PR #61.