Thanks for your reply! Faust is a great project, and it is really versatile.

However, I have checked some generated Rust code from Faust and found it relies on some unsafe blocks there. My concern is if one wishes to use Rust for audio, it doesn't make a lot of sense not to control all the details and make sure of the safety in detail.

The other concern is the incompatibility of license. In Rust community, MIT or Apache are more popular for further usage.

For VST, Glicol can run in vst and support sample-level control: https://youtu.be/yFKH9ou_XyQ

Still a POC for now, and I need to make the input working. But I am not very optimistic for many use cases in VST. I think two main goals for Glicol is collaborative live coding in browsers and quick prototyping on Bela.

thanks for the write-up, now i get that you're trying to build Sonic Pi of Rust!

btw., feel free to share on Rust Audio forum: https://rust-audio.discourse.group

also the VST integration is fire, i think people would build amazing stuff with it

I would say in terms of abstraction, Glicol is more comparable to Chuck, SuperCollider or Csound, yet written in Rust, with some priority towards collaboration, syntax ergonomics from music interaction perspective, following the trend of Algorave and Web Audio. These languages' audio engine has all been contributing as an audio lib. And for example, Sonic Pi relies on the audio engine of SuperCollider.

Thus, Glicol's audio engine will soon be published as a Rust crate: https://github.com/chaosprint/glicol/tree/main/rs/synth

Still, for the VST, I kinda feel that users may find it easier to use Max4Live or PD-VST (e.g https://github.com/pierreguillot/Camomile) rather than a text-based language, since VST is already a graphic interface :)