search

OwlPlug / central

[Deprecated] OwlPlug central plugin collection. Tracking repository based on git LFS.
0 stars 0 forks source link

Central json linux unknow value #4

Closed kmturley closed 3 years ago

kmturley commented 3 years ago

Think this might be a bug?

"name": "Linux VST", "targets": ["unknow"] https://central.owlplug.com/mirrors/vst4free/store

kmturley commented 3 years ago

Also this feed seems to leave out some great plugins e.g. https://plugins4free.com/plugin/3120/

DropSnorz commented 3 years ago

Hi @kmturley !

You are right, the value unknow is not on the spec. Well, here it should be linux. Even if this value is not on the spec either, it makes more sense. I will update the feed if OwlPlug is compatible.

I've indexed the data based on the old website version (which was named vst4free). The index engine is now outdated. It was more a proof of concept for large plugins collection support. In 2017, there was no information about who was the maintainer so I never asked permission to bypass the website for plugin downloads. So, maintaining this mirror (or proxy) is a grey zone and I don't put much effort into it.

I will send a mail to Ben about that.

Do you plan to use this feed as a source for studiorack ? I've seen the Owlplug central source in the codebase (It's really cool 😉 )

DropSnorz commented 3 years ago

Oops, missed the typo problem, unknow should be unknown 😅

kmturley commented 3 years ago

No problem, I hope it will help improve Owlplug for Linux users :)

I started to follow the same approach as your project, allowing different sources. For example I added Owlplug central as a source: https://github.com/studiorack/studiorack-registry/blob/main/src/sources/owlplug.ts

But then I realized that many of the plugins were built for Mac or Windows only. Also they were not always open-source. So i've commented out that functionality and I only load Github repos with studiorack-plugin topic as a source for now: https://github.com/studiorack/studiorack-registry/blob/main/src/index.ts#L29

I'm starting to be more opinionated about which plugins should be added to StudioRack. Instead of adding as many plugins as I can find, i'd rather have have a filter for which plugins get added:

This differentiates the StudioRack project from others, but I think also gives the project a focus, to help and promote open-source projects. There will be fewer plugins but they will all match these criteria. I have 20 so far and will add more over time: https://studiorack.github.io/studiorack-site/plugins

I'm planning to help plugin authors to create automated cross-platform builds. There are many repos I can contribute to make this happen.

It's going to be a lot of work, but will ensure more compatibility!

DropSnorz commented 3 years ago

I've just fixed the vst4free feed !

All plugins in central.owlplug.com/store.json are hosted on OwlPlug servers and are open source (or with a permissive distribution license) but yes, this is not the case of plugins referenced in mirrors. I think a license field would be useful for each product on the Json feed.

As you saw I've recently automated OwlPlug binaries generation using GH Actions, so I will probably release a Linux version soon.

I'm really happy to see studiorack growing ! 🙂

kmturley commented 3 years ago

Yes I was thinking the same thing. StudioRack should display the license in the feed as well as the app/site.

That would make it easier to audit and ensure no plugins are added that violate the license!

Feed looks fixed to me, thanks for the quick turnaround. Merci!

Edit: I added a Projucer Github Workflow building cross-platform here: https://github.com/studiorack/studiorack-plugin-juce/blob/main/.github/workflows/release_projucer.yml