Camomile VS vst-rs

Camomile is (still) the only thing that will do what you want. https://github.com/pierreguillot/Camomile

I think the first project of this kind was pdvst~ (https://github.com/jyg/PdVst). A more recent effort is Camomile (https://github.com/pierreguillot/Camomile).

PlugData seems to be much more extensive and flexible, though!

You can compile to vst with camomile as well, I wanted to mention.

https://github.com/pierreguillot/Camomile

You want Camomile: https://github.com/pierreguillot/Camomile

I have a different suggestion

you should definitely check Camomile by Pierre Guillot, i managed to run relatively complex patches as audio plugins through it on several DAWs just fine, with midi mapping and preset saving capabilities, however when running my synths as instrument plugins i found a couple of inconsistencies that made them kind of unreliable... i hope it gets better with future updates, if i ever get good at c++ i'd like to help with its development because it truly is an amazing work

There is a project called camomile where you can run a Pd patch as a VST with built in support for building a GUI within the patch and integration with basic DAW stuff like BPM sync.

Camomile - fairly easy way to get Pure Data patches in plugin form; incredible rabbit hole to potentially fall down if you want total control

https://github.com/RustAudio/vst-rs this what you mean?

I hate to "uhhmm ackchyually" this, but unless you need native VST3 support* (which uses the C++ ABI directly) other options are available, a favourite of mine would be Rust!

VST2 bindings exist (https://github.com/RustAudio/vst-rs) but the VST3 and AU situation is rougher around the edges. There is work being done on abstracting over different plugin standards and easing parameter handling, notably https://github.com/wrl/baseplug and https://github.com/robbert-vdh/nih-plug, but nothing completely stable yet.

One limitation that they mention is "Only one GFX and one LFX APO can be registered for an output device and only one LFX APO can be registered for an input device." which could be a problem for people who are already using one like Equalizer APO. What you could do is make a VST version of your limiter using vst-rs and use Equalizer APO to handle the APO part.

I agree with the first half. For the second half, I think for beginners, the examples are very important. From this perspective, many Rust projects comes with examples:

https://github.com/RustAudio/vst-rs

Once following the readme, it is very easy to get it work in your own machine. Then beginners can edit things while learning new stuffs with books or online resources.

Rust audio has also got a very helpful Discord community where beginners can always ask questions.

For the GUI part, I am not an expert, but there are more and more Rust GUI libraries (egui, iced, druid, rui): among them, egui-rs and iced-rs can all be used for VST. Still, there are some examples to get started with.

https://youtu.be/yFKH9ou_XyQ

If you want your own vst (with your name on the author and you can sell),you can start with vst-rs:

https://github.com/RustAudio/vst-rs

Wanna some GUI, here is a template:

When I came across the vst-rs, I realised that I could try out writing an audio plugin. Since I was already familiar with FM synthesis from Elektron Monomachine and FM8, I decided to go with it. It has worked out pretty well.