Alex Zywicki

Seems to be a great start at an example! It will be important to find a way to make it platform agnostic though. The most obvious approach in that case...

I think this would be worth implementing. It would enable support for side-chain processing.

The word “strong” should be “stdout”

We would have to test and find out. I don’t think we have come across this issue before, but many vst hosts force you to reload the program to detect...

We may need to manage a static pool of plugin instances from within the lib and clean up the memory when the host notifies us before destruction. (Which I think...

@PhilStem there is now a more up to date for of this repo that is under active development and improvement here https://github.com/rust-dsp/rust-vst Have you verified that your DAW’s are pointing...

Going with that solution I would opt for a buffer size somewhere in the range of 512-2048 depending on the amount of traffic expected. I have some concern as to...

Ideally it would be a Lock Free Implementation of some kind.

In that case would a Vec actually be the correct data structure to use? what advantages would we gain from using a Vec that is supposed to be fixed sized...

An article worth reading on the topic: http://www.rossbencina.com/code/real-time-audio-programming-101-time-waits-for-nothing