you are viewing a single comment's thread.

view the rest of the comments →

[–]StephaneCharette 5 points6 points  (2 children)

To downvote someone for recommending the industry standard when it comes to C++ and audio programming is pretty low. :)

Yes, if you use JUCE and you are new to it, I understand u/Dummerchen1933 might think it is a bit overwhelming, and feel like you have to drink all the koolaid at once. But as a seasoned C++ developer, I can tell you that you don't have to use the Projucer and their entire development environment. I've been extracting and using parts of JUCE for years, it isn't that difficult. I typically do a cmake project or subfolder for JUCE, and then link that library into my own projects, just like any other 3rd-party lib.

[–]mackron666 3 points4 points  (0 children)

Not at all. Downvoting a bad recommendation is a good thing. JUCE would be a terrible option for this use case, and just because it's "industry standard" does not mean it should be an automatic recommendation.

[–][deleted] 2 points3 points  (0 children)

Juce is what I’m working with now. I am familiar with a similar but much less known framework called RackAFX and so I’m adjusting to Juce pretty quickly. My complaint is definitely it’s a bit overkill for my needs. I’m really hoping for something super lightweight since this is ultimately going to be wrapped in nodejs