Very hyper-specific audio programming fag question here: I'm working my way up to making my own VSTs and whilst they will just be for my own personal use, I hope to sell some eventually.Is there any way to avoid JUCE and is it worth it to do so? From a technical perspective the framework is great, but:> costthe licensing for commercial use a bit annoying, but it helps fund dev support> Similar alternativesthe support for JUCE seems to be based mostly on marketing and the idea that it just simply is *the* standard despite me hearing very compelling reasons to use alternatives like QT or iPlug2. I suspect the difference between JUCE and its competitors is not nearly as big as I've been told; I could be wrong.
>>106958722>the licensing for commercial use a bit annoyingjust follow the AGPLv3? it's not hard anon
>>106958739It isn't, but they are also the only framework other than Steinberg to do this.Honestly that's not really my main concern, I just want to know if the other options have something going for them too. I'll most likely still use JUCE anyway.
> rainbow shit Take your tranny shit somewhere rlse
>>106958763OP literally said he wants to avoid using picrel
>>106958722>avoiding jews
>>106958722>Avoid C++ CodingFTFY
>>106960163VSTs require good performance so you're kind of stuck with C++
>>106960171Whenever you can use Sepples, you can use C.
>>106960171>VSTs require good performanceLmao if this were true then SoundToys would be bankruptHalf of the people using your VST pirated it, the other half are on Macs way too strong for what they're doing in their DAW anyways
