Update: Things are moving on nicely with my first main attempt at wrapping the AGain demo included in the VST sdk to python using nothing but the standard python C API. So far I have everything implemented but the main process, for which I’ll need to do a bit more reading on the numpy C API. Most of this was possible thanks to an easy tutorial by Jun Du over at codeproject.com.
More updates (and source code of course) to follow soon.
Ok, pyvst is stil chugging along but the python C API is pretty massive and has a lot of functions to get my small brained head around. I’ve got the again demo supplied in the vst sdk returning random numbers to the fader label after each buffer, which is useless on its own but another step forward. Watch this space. I’m still chugging along and coming up with some cool feature ideas.
Interpreted languages are an awsome way of realising ideas very quickly, even if you eventually want to hard code your projects in C. I’ve been looking into python more and more recently (since using SCons as my C++ build tool), and have been having some luck with the numPy package for efficient matrix and array mathematics (gives MATLAB type functionality, but for free). Python is also very easy to integrate with C code.
I’ll try to get something up and running in the near future where you have a pre-compiled dll (and eventually the equivalents on other os) which acts as the gateway between your vst host and Python. This is intended to be a very similar project to jVST, enabling python programmers to achieve similar ease of development. I’m sure it is much better to worry about the DSP and sound quality of your plugin at first without the faff involved with the C++ language and constant compile, recompile cycles.
Keep watching this space and I’ll keep reading up in my spare time and eventually start a source forge project or something similar. Should be fun!
I’ve been using an interpreted scripting language called Matlab to do my research work for some time now. I often type short commands straight into a command window to test the output before adding those commands to the main script. This really accelerates my development time. Now that I’m learning c++, I have become frustrated with having to recompile each time I want to test a small change to a calculation, or check my syntax. This is where Ch comes in. It is a freeware (for the standard edition) c++ interpreter which supports many functions and allows rapid checking of code fragments. The following screenshot is just me having a little play, while Ch seems to allow you to do so much more. I recommend you download and have a play!