elementary VS vst3sdk

I don't know which library you're using, but I use Elementary Audio for my audio projects. This looks like a great fit.

Well I m a js dev in life, I recently discovered this library https://www.elementary.audio/, which at first stable release does a pretty good job, I did little experiments and it seems pretty promising

And check out this new native audio implementation with JS !!! https://www.elementary.audio/

Great recommendations in here, and I'm happy to see this thread getting such attention!

This is totally a shameless self-plug, but I think it could be interesting for you:

I'm working on a project called Elementary Audio [1] which is a javascript runtime + framework for writing native audio software. It's like the Web Audio API in that it's javascript+audio, but unlike Web Audio in that it aims to target true native audio apps, like plugins for your DAW or hardware projects.

The API that it offers feels to me very much like thinking and working in analog synths, which is why I think you might find it interesting. You can describe and wire up signals and just see what they sound like without having to worry about what needs to happen under the hood for you to hear it.

I put together a guide for dipping your toes into making sound [2] and you'll find there a bunch of other resources that I recommend for getting into the topic.

I should note too that it's currently in beta and only supports macos and linux (windows coming soon!)

[1]: https://www.elementary.audio/

Funny you should say that :) I'm currently building a small drum synth, will share it as soon as its ready.

In the mean time, check out https://github.com/nick-thompson/elementary for some examples that you can `npm install && npm start` to hear

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