JUCE VS AudioKit

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:... - Source: Hacker News / 6 days ago

Check out https://juce.com in the meantime. Source: 5 months ago

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: Hacker News / 5 months ago

Https://juce.com Maybe that's what you want? - Source: Hacker News / 7 months ago

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. Source: 10 months ago

It seems to be the industry standard at least. I have played around with iPlug2 and AudioKit a little bit but not enough to really form an opinion. (iPlug2 is described by the authors as "not production ready" and AudioKit is mac / ios only). Source: over 2 years ago

You’re up for a lot of work, but I would start with AudioKit which is an abstraction over AVFoundation. Source: over 2 years ago

I can’t help with that, but I would suggest looking at AudioKit. Even if it doesn’t help you replace that dependency, it might give you pointers for doing it yourself. Source: almost 3 years ago