2: Efficient development

If you’ve used code::blocks to create a stand-alone application, you’ll appreciate that the application runs immediately after each recompile, accelerating the testing process. You also have to option to use the code::blocks debugging support and have the ability to profile your code for efficiency using the code::blocks plugin for gprof.

Doing this kind of thing with your fresh VST plugins is a bit more of a chore. The dll file you create has to be reloaded into the host each time you make a change to the source and recompile. This becomes a complete headache after a while. Debugging and profiling is not so straight forward either. The goal of this tutorial is to iron out these glitches in your workflow.

This tutorial is currently under construction but . . .
see this forum topic for the time being.

Advertisements
  1. KunzHerman
    December 24, 2009 at 01:37

    Hey, I would be interested (for practical purposes this would be an ideotical question) how to extend the so-called “AGain” example with a Dry/Wet control?

    Or in general: How to add a second or N-th control to a VST Plug?

  2. mister helpful
    February 2, 2010 at 16:41

    I’m still a n00b but I think I can help with this one…

    again.h, line 46: add other protected variables to represent other controls (or ‘parameters’ in VST speak)

    again.cpp, line 23: the second ‘1’ means 1 parameter so increase this

    again.cpp, line 31: set default values for all parameters

    again.cpp, lines 54: the ‘setParameter’ function ignores the ‘VstInt32 index’ argument because AGain has only one parameter. If your plugin has more than one it will need to do something different depending on the value of ‘index’, for example:

    if (index == 0)
    fWet = value;
    else if (index == 1)
    fDry = value;

    etc.

    All the functions with ‘Parameter’ in the name will need to be changed in a similar way. Also the extra parameters will presumably be referenced in the processing functions if they do anything…

  3. JorgeGarcia
    March 12, 2010 at 09:17

    Hello there,

    I’ve been googling to find a proper explanation of how to debug a VST dll using codeblocks under windows, and found your website. Do you have any clue or list of must-do things for dummies to make it work properly? I can launch the host, but I am not able to add watches and see any variable…

    Thanks a lot

    • March 12, 2010 at 13:34

      If you’re using VST host by Hermann Seib, check out his website for a debug version of the host. I seem to remember that there is a version of the host available compiled with debugging info. Sorry I can’t be of more use right now. Thanks for looking.

  1. No trackbacks yet.

Leave a Reply

Fill in your details below or click an icon to log in:

WordPress.com Logo

You are commenting using your WordPress.com account. Log Out / Change )

Twitter picture

You are commenting using your Twitter account. Log Out / Change )

Facebook photo

You are commenting using your Facebook account. Log Out / Change )

Google+ photo

You are commenting using your Google+ account. Log Out / Change )

Connecting to %s

%d bloggers like this: