request: add format and platform columns
Moth-Tolias opened this issue · 4 comments
it would be nice to know what platforms and formats a given plugin supports. several new plugins these days only support vst3 on windows while offering lv2 and vst3 on linux, for example.
see also #16
Further to this, we now have the beginnings of a data format for the plugin list. I'm now wondering what fields we need to make the list more useful. Ideally I'd like it if apps could consume the list to actually present the plugins for download AND link to the platform-specific download itself, possibly even without the user having to open a web browser.
To me that would require per platform, per architecture download links. Whether the link is to a specific plugin variant (VST etc) could be a problem as some will bundle all plugin types in one installer, others will have an installer (or just a binary) per plugin type.
Hello @webprofusion-chrisc
I'm now wondering what fields we need to make the list more useful
I personally really like the "stars" and "last updated" fields of the awesome-juce list.
I'd like it if apps could consume the list to actually present the plugins for download AND link to the platform-specific download itself, possibly even without the user having to open a web browser
You might be interested in the owlplug-registry repository. It's an effort to create a feed consumed by applications like OwlPlug to download and install audio plugins.
To me that would require per platform, per architecture download links. Whether the link is to a specific plugin variant (VST etc) could be a problem as some will bundle all plugin types in one installer, others will have an installer (or just a binary) per plugin type.
I've faced all these problems working on OwlPlug, and it's a pure nightmare 🤣
@DropSnorz thanks, that's awesome, so perhaps we could just store the owlplug registry ID for the plugin in our data to cross reference?
@webprofusion-chrisc Yes, feel free to use this API to retrieve some data 🙂
There is a latest feed with only the latest package version referenced. Make sure to not use the store.legacy files as they are deprecated.
I have to document this Package model more, but most properties comes from the legacy Store model.