» VST
This site relies heavily on Javascript. You should enable it if you want the full experience. Learn more.

VST

this is a pretty old vst integration, a newer one which also works with 64 bit vvvv is here: vvvv.audio-pack-alpha

Introduction

VST-Plugins (Virtual Studio Technology) are either audio-effects or instruments that can be used with vvvvs modest directshow/audio capabilities.

VVVV is not shipping with any vst-plugin. See below for a listing of some free effects or get any other and put the files (or a directory that contains .dll plus possibly associated files such as soundbanks etc.) into

 \lib\nodes\vst

Start vvvv and the plugin should now be available among the VST category in the nodebrowser. There is no generic vst-node, every vst-node is a wrapper for a specific vst-plugin and is named after it. Click on the plugin in the list and a node is created, which has an associated window showing the GUI of the plugin. This window can be closed/opened as usual by pressing Alt+1 or Alt+3.

Per default the plugin shows two input pins and one output pin. The input pin must be connected to an audiosource-node (Waveplayer/Sourcebuffer/Filestream) or another vst-plugin (but still with an audiosource-node at the beginning of the chain). Vst-instruments must have an audio-input too. As vst-instruments overwrite the audiostream completely, it has no use to chain a vst-plugin before the vst-instrument. Vst-effects can be chained arbitrarily.

Plugins typically have a large list of parameters, so they are all hidden by default and you have to activate them individually via the Inspektor. Clicking twice on the button left to the value of the parameter makes the pin show up on the node. In most cases these parameters are associated with a knob, slider or toggle on the GUI. If the value of the pin is changed, it can be seen and vice versa. If an Input-Node is connected to the vst-parameter-pin it dominates over the GUI. All parameter-pins range from 0 to 1 in vvvv and are mapped to the parameters range inside the plugin.

Most Effects have two input-channels (stereo), but there are some, which have more. This property can be seen in the Inspektor as Channel In Count and Channel Out Count. You may have to prepare the source-node to the vst-plugin by changing its amount of channels accordingly (see the helpfile of the sourcebuffer or waveplayer).

Controlling VST plugins with MIDI

Vst-Instruments can receive midi-notes and transform them into sound. Midi-Notes can be provided either directly from input-data created in vvvv or the MidiNote-Node can be used to receive the midi-notes coming from an external device such as a midi-keyboard. There are more midi-msgs which can be sent to the plugin, have a look inside the inspector.

Latency when controlling VST plugins with midi is an issue which is mainly due to vvvvs internal framerate not being really suitable for audiooperation.

If you want to see demopatches to this topic download polykeys, Synth1 VST, SupaPhaser (see list below) and put the demopatches and the plugins in the vst-folder.

Tutorial

Download the Synth1 VST-plugin and uzip it into

 \lib\nodes\vst

Now open vvvv, doubleclick in the patch and select the Synth VST-Node from the nodebrowser. Open the inspektor and enable the Midi Notes, Midi Notes Velocity and Midi Notes Send pins.

Connect the IOBox to the Midi Notes-Pin, the Toggle-Node to Midi Notes Velocity-Pin and the TogEdge-Node to the Midi Notes Send-Pin. Everytime you press the button in the IOBox, the midi-note 49 with the velocity of 1.0 is send.

The next patch shows the use of the MidiNote-Node to be able to receive midi-notes from external midi devices. Download the Polykeys-plugin, put it into

 \lib\nodes\vst

and open vvvv. Select the Polykeys-Node from the nodebrowser, open the inspektor and enable the Midi Notes,Midi Notes Velocity and Midi Notes Send pins. Open the I-Node and MidiNote-Node. Put a IOBox with the value of 127 into the To-Pin of the I-Node. A spread ranging from 0..127 is now the output of the node, this corresponds to the 0..127 possible midi-notes. Connect the I-Nodes output to the Midi Notes-Pin of the Polykeys-Node and to the Note-Pin of the MidiNote-Node.

Now put the Enable-Pin to 1 and select a midi-device in the Midi Input Port of the MidiNote-Node, then connect the Output-Pin to the Midi Notes Velocity-Pin of the Polykeys-Node and the On Data-Pin to the Midi Notes Send-Pin. The midi-notes of your device should now be send to the Polykeys-Synthesizer.

VST Plugins tested to work with VVVV

Nice free instruments

Nice free effects

If you find problems with any vst-plugin in vvvv please report them to MEanimal

Links

  • Wikipedia about VST
  • Start developing your own VST-plugins.
  • VSTHost is an amazing open source VST-Host.
  • KVR Audio is a huge database of vst-plugins and related stuff.
  • Voxengo - free VST Plugins
  • The sourcecode (licence: LGPL) of DSVSTWrapper.ax: a directshow filter wrapping a VST host enabling the use of VST-plugins within any directshow graph.
  • Voxengo Recorder is a VST plugin which allows you to record the output of the channel or bus into a stereo WAV file.Routing to MME (multimedia extensions) soundcard is also supported.
  • Wormhole Wormhole2 is for audio professionals and musicians, allowing routing of audio between machines on a network.Wormhole2 is available for Mac VST + Audio Unit and Windows VST.

anonymous user login

Shoutbox

~1d ago

id144: AIR OpenCall: Artists and researchers from DE, working with the issues connected with digital culture. http://www.kair.sk/open-call-for-german-artists-2/

~1d ago

velcrome: @mrboni check noodles pack

~2d ago

catweasel: bezier match not doing it for you? Or do you need GPU specifically?

~2d ago

mrboni: I meant a gpu version of B-Spline (3D Surface). I only found an approach using bicubic filtering on a texture (dx9 gpuparticles)

~2d ago

joreg: @mrboni that would be splinesgpu

~2d ago

microdee: @mrboni: ye olde GPU particles from DX9 times ;)

~2d ago

mrboni: is there some kind of gpu spline surface shader around?