baseview VS vst-rs

For instance, I ended up contributing a large part of the macOS implementation of https://github.com/RustAudio/baseview for plugin window handling, since nothing filling the need existed (baseview works pretty well now, though.)

I have been working in Rust for about 4 years, mainly as the developer of aquatic and OctaSine and as a contributor to baseview. I have prior experience in web development using technologies such as actix-web, TypeScript, React, Django and PostgreSQL.

I eventually decided that I wanted a GUI. The Rust GUI situation is not very mature and special considerations required for vst plugin windows complicate the situation further. I discovered baseview at some point. With the mentoring of wrl and others, I was able to contribute code to get it working on macOS.

For context, I am working on/contributing to a cross-platform windowing library, and the situation is the same with the Windows and macOS platform APIs. I don't really need or want a safe abstraction over any of these, because what I am working on is the safe abstraction.

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.