VST 2.0 Spec Adds MIDI Control

(Click for a close-up)

Steinberg are very happy to announce availability of the VST 2.0 PlugIn Specification: Now the number of Parameters used by a PlugIn has been increased to 16, these parameters are MIDI-controllable and it is even possible to create Software Synthesizers and Samplers as a PlugIn.

Understanding VST

Generally the VST Protocol defines a simple method for implementing DSP algorithms for host CPU based audio systems. It allows signal processes to be very quickly developed avoiding much of the OS dependent issues or very specific DSP chip programming schemes. The result is that both writing and using a VST Plug-in is very easy compared with other systems.

Who can create a VST Plug In?

Anyone can download the software development kit to create a VST plug-in. This has fuelled an explosive growth in the availability and diversity of plug-ins, more than 160 VST Plug-ins are now available from all leading DSP Plug-in vendors, and the Internet has become a rich source of free and shareware plug-ins, ranging from the simple to the bizarre.

Who can host VST Plug-ins?

VST Plug-ins were initially used in Steinberg's Cubase VST program, but after the successful implementation of VST-Host technology in Emagic's Logic Audio, and Opcode's Vision Software on the Macintosh, Steinberg opened up the host-side VST support. Particularly for the Windows platform, where VST automation and ease of implementation, and true real-time control characteristics gave it a clear advantage over existing Windows solutions, there is an ever increasing number of applications that are supporting VST Plug-Ins.

What's new in VST 2.0?

Shortly after its first introduction, the VST Plug-in group was a rich source of ideas on how the VST-Plug-In specification could be extended. When other companies started to host VST Plug-Ins, the ideas for extensions on the host side grew too. The VST 2.0 Specification is the result of combined consultation, and builds on the VST 1.0 spec to bring about some exciting new possibilities.

VST Plug-ins gain a MIDI port.

With VST 2.0 it is possible to send any MIDI data to a plug-in. Similarly, a VST 2.0 plug-in can generate MIDI data and send it back to the host application. This offers the possibility to coordinate the audio processing with other musical tasks.

For instance, it would be possible for MIDI clock information to control the audio process' task in a tempo orientated way, enabling beat-matched echoes etc. Events could be used to trigger certain processes, such as re-triggering a LFO cycle, or an envelope generator, etc. Controller streams could control any variable parameter etc. Having an Active MIDI port also means that providing comprehensive real-time control over the effect process becomes a simple task for a generic external MIDI controller. But Plug-ins can generate MIDI data if they wish; the result of an analysis Plug-in can then be sent back to the host, and then onto other Plug-ins, or be recorded on MIDI tracks; Pitch tracking programs could send their MIDI data to a format sensitive Pitch Shifter etc.

VST 2.0 Hosts Soft Synth Modules.

With the addition of the MIDI port, that can also receive time-stamped MIDI from the host application, a VST 2.0 Plug-in, it could contain a complete Software Synthesizer, controlled from the incoming MIDI data. It can generate its synth signal however it pleases and then send the result direct to the host applications mixing environment for further processing.

VST 2.0: A Maturing Specification.

The Plug-in can now inquire in what context it is used. This enables a single Plug-in to adapt itself for insert or buss operation, or adapts whether it's got stereo input or outputs. The user gets just one plug-in, and uses it wherever they want. Now the user can enter values generically by double-clicking a text field and directly typing a text string in, VST 2.0 offers a new mechanism where this text input is passed to the Plug-In to see if it can interpret it as a value.

Release of the User Interface Library.

The VST 2.0 Software Development Kit now includes the Steinberg User Interface Library. Previously Plug-ins either provided no interface of their own and used the generic handling in the host application, or they provided their own interface mechanism. With the library functions provided in the VST 2.0 SDK, custom user interfaces can be implemented for any VST Plug-in, without the pitfalls of resource & window management.

The VST 2.0 specification is downwardly compatible with existing applications and Plug-ins that supports the VST 1.0 protocol. For an application to take benefit from these new features, both host application and plug-ins needs to conform to the VST 2.0 protocol.

For developers the SDK, application forms and release dates are available at: http://service.steinberg.de/webdoc.nsf/show/development_e