vst-rs VS trust-dns

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.

If you don't know what is Trust-DNS / Hickory DNS, this seems to be the repo: https://github.com/bluejekyll/trust-dns

IO is not a part of the async runtime contract (I don't know if this is good or bad), and Tokio & futures famously have different `Async{Read,Write}` traits. I once had to do this [0] to adapt between them.

This means that any crate that uses IO will be bound to a limited number of Runtimes. Everything being Tokio-only is pretty bad (though Tokio itself is great), but here we are...

[0] https://github.com/bluejekyll/trust-dns/pull/1373#issuecomme...

I need a cert.pem and privkey.pem for https://github.com/bluejekyll/trust-dns but even using the extractor to get a cert.pem and privkey.pem from the acme.json file it seems invalid.

You might be interested in Trust DNS - "A Rust based DNS client, server, and Resolver, built to be safe and secure from the ground up."

It looks like you need to reach for a separate crate for that: https://github.com/bluejekyll/trust-dns/blob/7dcb7b983f5407d95d93b800af13caeee975aaa8/crates/async-std-resolver/src/lib.rs

You might be interested in new alternative to dig called dns https://github.com/bluejekyll/trust-dns/blob/main/util/src/dns.rs . I found out about it from https://twitter.com/benj_fry/status/1513269287229657091

I've found the Trust-DNS Resolver crate and it does the job! Now the binary seems to not use any dynamic library to look up the ip of a host.