More updates (and source code of course) to follow soon.

The examples are C extensions for a python script but what I’m aiming to do with pyVST, is get the plugin dll to start up the python engine and then pass each frame of the data buffer to a python script for processing. The C extension code will make a useful starting point for passing the data between the plugin dll and python. The aim is to make the plugin aware of its file name and then call a python script with the same filename to do the processing. This will eventually alow a user to make plugins without having to touch any C code. I’ve got a bit of time off at the end of this month, so maybe pyVST will get moving a bit more.

There is no documentation on the numpy extensions page for building on a Windows platform, so here is what I did:

• Download the tarball and extract
• Include the C source and header in your poject
• Include the numpy headers directory
• Link to the python library
• Add this missing line to the header file “static PyObject *rowx2_v2(PyObject *self, PyObject *args);”
• In the main source file, ptrvector() allocates n*sizeof(double), but should really allocate pointers to double; so: n*sizeof(double *)
• Set your compiler to build a dll
• Name the output file “_C_arraytest.pyd
• Put the output file in the same dir as C_arraytest.py and run

Hope this helps anyone googling C extensions for numpy under Windows

Build again in code::blocks . . .

1) Make new EMPTY project and call it “again” – you can save this anywhere on your system

2) Assuming you have put the sdk at c:\vstsdk2.4, then right click on the project you have just created, select build options, got to the ‘search directories’ tab and add c:\vstsdk2.4 to the list.

3) Right click on the project and select add files. Add the following:
C:\vstsdk2.4\public.sdk\source\vst2.x\audioeffect. cpp
C:\vstsdk2.4\public.sdk\source\vst2.x\audioeffectx .cpp
C:\vstsdk2.4\public.sdk\source\vst2.x\vstplugmain. cpp
C:\vstsdk2.4\public.sdk\samples\vst2.x\again\sourc e\again.cpp
C:\vstsdk2.4\public.sdk\samples\vst2.x\again\sourc e\again.h

4) Right click on the project, select ‘Properties’, navigate to the ‘Build targets’ tab and select ‘Dynamic library’ from the ‘Type’ drop down list.

5) Right click the project, select ‘Build options’ go to the linker settings tab and under ‘Other linker options’ add the following:
-def C:\vstsdk2.4\public.sdk\samples\vst2.x\win\vstplug .def

6) Build the project.

The author of this tutorial recommends that you use the code::blocks IDE. I too have more recently become an advocate of using code::blocks due to its fantastic debugging capabilities and plugin support for profiling with gprof. Code::Blocks uses the same open source GNU c++ compiler which I use in the tutorials here but has its own build system built in rather than using SCons. The only reason I show the reader how to use SCons is for educational purposes, so that they have a really good idea of what they are doing with the source files in each example I present. It is just as easy to use code::blocks for VST plugin development once you want debugging and profiling support.