vst3sdk VS JUCE

But you don't have only Linux, you have (and probably first) OSX and/or Windows and then Linux, and you need an API that works well in that case. Being an in-process dll/so plugin, while fraught with perils gets you to avoid other issues (state, health, restart, identity, etc.)

Also sometimes you don't have a choice, but have to make a dll, for example:

https://github.com/steinbergmedia/vst3sdk or https://ae-plugins.docsforadobe.dev/ and many others. Sometimes it's the only viable choice.

(I wish most have used grpc/flatbuffers/whatever to communicate, but then every RPC call have to be checked/retried/handled, and or shared memory well handled, with (?) locks, etc. - not a trivial thing for someone who is deeply specialized in making a very good effect/renderer/etc instead of dealing with this extra complexity on top).

Yeah, you can use nordaudio which wraps PortAudio which has support for every major audio back-end. As for writing a VST you may have to find a way to wrap or interface with Steinberg's SDK. MIDI support is possible by using an RtMIDI wrapper, which I haven't linked because there are a few of them out there of varying quality and I don't know which is best because I just use ALSA directly for my purposes.

You can read the VST3 SDK manual for yourself here https://steinbergmedia.github.io/vst3\_doc/vstsdk/index.html and access the source here: https://github.com/steinbergmedia/vst3sdk.

You have to use the steinberger SDK to make a vst

https://github.com/steinbergmedia/vst3sdk

But audio plugins come in many formats.

https://github.com/steinbergmedia/vst3sdk#build-the-examples-on-linux

You can do VST3 as GPL. They dual license it. Lots of legalese to read but definitely an option. https://github.com/steinbergmedia/vst3sdk/issues

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/