Repository navigation
Replies: 1 comment
|
Hi @jterrain Thanks for using OwlPlug, and for taking the time to write this up! 🙏 I completely agree with the pain point: every DAW has its own plugin manager, and redoing your folders/favorites in each one is tedious. Such a feature would be great, but I'm not gonna lie, it looks very hard to implement. Each DAW stores its plugin organization (folders, collections, tags, favorites) in its own format, and most of them are undocumented and change between versions. Some are plain text files, others are internal databases or binary preferences. Writing into them would mean reverse-engineering and maintaining a separate integration per DAW (and per DAW version), with a real risk of corrupting a user's setup when a DAW updates. A more DAW-agnostic approach is tracked in #123: letting OwlPlug generate a folder structure on disk (by manufacturer, category, etc.) from your plugin information. Some DAWs (mostly for VST2) show plugins following their folder layout, so organizing the files themselves can carry over without touching each DAW's own settings. It won't cover every DAW or plugin format, but it's probably the closest realistic option to what you describe. |
Uh oh!
There was an error while loading. Please reload this page.
Thanks for producing the OwlPlug software - it's really cool!
What would make this super-useful for many users: Currently, each DAW (Cubase, WaveLab, Ableton, Bitwig, etc.) has its own plugin management utility, which requires the user to re-organize the plugins manually for each system.
If OwlPlug could enable the user to manually organize all plugins once (in OwlPlug, with arbitrary groups such as developer, audio category, etc.)... and then this organization would be presented to all the DAWs, this would be a game-changer. Then the user could just organize plugins once and all the DAWs would be ready to go.
All reactions