@dreamer @ugurcan @sramsay @SouthFresh @alisynthesis @shanesemler @klangverstromung Should I list any of you under Linux Musicians Spotlight at https://linuxaudio.dev/
I'm getting good feedback from potential Linux Audio #vendor (s), but want to make sure I haven't forgotten anyone (also for the Linux Audio Developers Spotlight section, by the way).
So if you have any input, I'd love to hear from you. 🙌
@amadeus DISTRHO is missing from the list, which has, among other things, Cardinal and Ildaeil.
https://github.com/DISTRHO/DPF/ could be shown as alternative to JUCE.
It is what pretty much all my plugins use.
I guess this means I really need to make my projects more visible...
@falktx Thanks! 🙌 I am adding it now. This is to make Linux only plugins, right? Or is it possible to make plugins for other platforms (macOS, Windows, etc.) as well?
@amadeus all platforms, including those that other platforms typically dont care about - like BSD and Web/wasm. It should work on any regular Linux/Unix/Posix-like system with X11. Very little code there is Linux specific.
Someday the GUI side will work on HaikuOS too, but not really rushing for that.
@falktx Oh wow, that sounds amazing. 🤓 I asked because when I looked through the documentation, I could not find any mention of Windows or macOS, for example. However, for a developer (which I am not) it might be obvious that DPF is cross-platform. What does DISTRHO or DPF stand for, if I may ask?
@falktx Just to be sure, I am adding DISTRHO under the Developers Spotlight section and also as one of the frameworks that can be used to develop plugins for Linux. And for the latter, I list that DISTRHO is capable of building plugins for Linux, macOS, Windows, iOS and Android, correct? Those are all the operating system options I currently list for the frameworks platform support.
@amadeus I think it matters for developers seeing the site, as it means there is source code that can be used/seen as reference.
By that I mean, if a developer sees an issue with their Linux builds but some other random plugin X does not have those issues, seeing that X plugin as opensource is very helpful as then its source code can be studied to understand what it is doing differently.
It also helps in the case of "how do I do X and Y on Linux?" if other devs did it before
@falktx I added open source labels now but need to go through the list again to make sure I catched all of the OS developers. Thanks again for the suggestion! 🙌
@amadeus by the way there are several issues regarding the licenses of the frameworks, critical ones at that.
LV2 is liberally licensed https://gitlab.com/lv2/lv2/-/blob/main/COPYING
It is not under GPL as the page states, please correct it.
Also VST3 SDK is not free for non-commercial. it is GPLv3+ alike JUCE where you can use it on GPL projects but proprietary software needs a license. (*)
Anyone can make a commercial + open-source VST3 plugin, no limitations there.
* VST3 has a GPL-incompatible clause
@falktx Thank you so much, I am correcting this now! 🙌
@dreamer @falktx Hmm, maybe I made a mistake then. It says "This project is licensed under the BSD Zero Clause License. Learn more" at https://gitlab.com/lv2/lv2/-/blob/main/COPYING
So, should I just change it to ISC then?
Apparently Gitlab automatically recognizes the ISC text as BSD0 even though you can see that the commit says "Use standard ISC license text".
@dreamer I see. Fixed it now.
@falktx Very good point! 🙌 Thanks a lot. I will think about how to make that visible.