JUCE VS audiogridder

Personally, I started by writing externals for Pure Data, then started to contribute to the care. Later I took the same path for SuperCollider.

The more typical path, I guess, would be to start with simple audio plugins. Have a look at JUCE (https://juce.com/)!

Realtime audio programming has some rather strict requirements that you don't have in most other software. Check out this classic article: http://www.rossbencina.com/code/real-time-audio-programming-...

Check out https://juce.com in the meantime

You can definitely start putting C++ into your embedded projects, and get familiar with things in an environment in which you're already operating. A lot of great C++ code can be found with motivated use of, for example, the platformio tooling, such that you can see for yourself some existing C++ In Embedded scenarios.

In general, also, I have found that it is wise to learn C++ socially - i.e. participate in Open Source projects, as you learn/study/contribute/assist other C++ developers, on a semi-regular basis.

I've learned a lot about what I would call "decent C++ code" (i.e. shipping to tens of thousands, if not hundreds of thousands of customers) from such projects. I would suggest finding an open source C++ project, aligned with your interests, and study the codebase - as well as the repo history (i.e. gource) - to get a productive, relatively effortless (if the interests align) boost into the subject.

(My particular favourite project is the JUCE Audio library: https://juce.com/ .. one of many hundreds of great projects out there from which one can also glean modern C++ practices..)

Respect for the others here who recommend C but I think they’re possibly masochists. If anything JUCE, which uses C++ is in my opinion far more approachable.

Here's a link to their website: https://juce.com/

It seems like most audio plug-ins are built in C++ inside an audio coding program called JUCE, so maybe if I could open up the exisiting code inside that and then output it as an AU instead of a VST that could work.

C++ has https://juce.com/, I think.

Open source rule https://juce.com/

Yeah this might be what you're looking for plus it's open source https://audiogridder.com/

Check out https://audiogridder.com/

I fully appreciate that a compressor will react very differently with group material, or that a reverb might put things in the same space intentionally. I understand that creative value but I am wondering where the line is drawn between efficacy and value - in a world where there were no limits (quickly approaching with tools like Audiogridder) - what ideas really deserve group processing? This question is pushed even further by tools like KSHMR Chain that allow you to synchronize settings across tracks.

CPU as fast as possible. 16 GB, preferrably 32 GB RAM. Always remember you can offload VST's work over the network to some other machine with https://audiogridder.com/.

Check this amazing stuff that works: https://audiogridder.com/