AudioKit VS JUCE

You should also check out AudioKit. The latest release should have an audio engine completely rewritten purely with Swift iirc.

I' just installed Xcode 13 and try to run a playground that uses a package (https://github.com/AudioKit/AudioKit). To add it I'm supposd to select "File -> Add Packages...", but when I do this absolutely nothing happens. No window appears, no error message, just nothing. What could be the reason for this?

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)

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

AudioKit - Audio synthesis, processing, and analysis platform for iOS.

Maybe check out AudioKit, it’s great for audio stuff.

There are open sources synthesizers projects for iOS in swift. I would recommend giving it a look and see if it fits your needs. https://github.com/AudioKit/AudioKit

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.

If you are on macOS, AudioKit is a nice simplified layer on top of CoreAudio and CoreMidi: https://github.com/AudioKit/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: 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/