vst-rs VS duplicate

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.

Got a question, a feature request, or got a weird error message? Feel free to either drop a comment or open an issue. The changes to this crate are mostly a result of feedback from users (which is much appreciated.)

This update includes only one bugfix that I found quite interesting: duplicate's choice of edition (2018 for backwards compatibility) leaked into user code that was otherwise using edition 2021. This caused compilation errors in the code produced by duplicate, since it was using a feature of edition 2021 that isn't legal in edition 2018.

At some point, I decided that I wanted to accelerate the synthesis with SIMD. I started out with using packed_simd, but switched to simdeez to abstract over vector widths and enable runtime detection. However, I wanted more flexibility and the option of splitting SIMD code into multiple functions. My solution was to skip frameworks and instead use custom traits and the duplicate crate to abstract over Rust simd instrinsics for different instruction sets. I use sleef for fast sines.

Got a question or feature request? Feel free to either drop a comment or [open an issue](https://github.com/Emoun/duplicate/issues/new/choose).