@graves501 @mosgaard @nielso @ercanbrack @macberg @prokoudine @markus @ohmrun @Venn @ambientspace @x42 @mitscherdinger @wvi @samuelFRDE @bshankar 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. 🙌
BTW, your FAQ mentions that LV2 does not have mac/Windows support, which is not true.
LV2 works on all those platforms (and *BSD) as well. It's also ISC licensed.
As for OS to use. An older one is preferable. When compiling a plugin on a recent system it may not run on older ones (libc compat). The OS should not matter much since (as with other platforms) plugins must be statically linked.
And yes, I have helped some vendors in the past to sort thing out. e.g. elephantdsp.com
@x42 Windows and macOS for LV2 is now added. Just to be sure I understand you: plugins that I helped optimize often had problems with libcurl-gnutls.so.4 vs libcurl.so.4. Most providers were able to solve these problems. Is there a way to completely avoid such problems from the developer's point of view? This is especially important in relation to Flatpak hosts in my experience.
@amadeus that sounds like they just need to "lazy load" libcurl instead of linking to it.
JUCE supports this for example https://github.com/juce-framework/JUCE/blob/develop/modules/juce_core/juce_core.h#L155
But not all developers even know it's an option. 🤷
@falktx OK, I see. Thanks for the background information.