A VST® plug-in is an audio processing component that is utilized within a host
application. This host application provides the audio or/and event streams
that are processed by the plug-in's code. Generally speaking, a VST plug-in
can take a stream of audio data, apply a process to the audio, and return the
result to the host application. A VST plug-in performs its process normally
using the processor of the computer. The audio stream is broken down into a
series of blocks. The host supplies the blocks in sequence. The host and its
current environment control the block-size. The VST plug-in maintains the
status of all its own parameters relating to the running process: The host
does not maintain any information about what the plug-in did with the last
block of data it processed.
From the host application's point of view, a VST plug-in is a black box with
an arbitrary number of inputs, outputs (Event (MIDI) or Audio), and associated
parameters. The host needs no implicit knowledge of the plug-in's process to
be able to use it. The plug-in process can use whatever parameters it wishes,
internally to the process, but depending on the capabilities of the host, it
can allow the changes to user parameters to be automated by the host.
VST 3 is a general rework of the long-serving VST plug-in interface. It is
not compatible with the older VST versions, but it includes some new features
and possibilities. We have redesigned the API to make it not only far easier
and more reliable for developers to work with, but have also provided
completely new possibilities for plug-ins.
VST is a registered trademark of Steinberg Media Technologies GmbH.
This package contains the vst3moduleinfotool and vst3validator tools. Note
that both tools have a "vst3" prefix to prevent name clashes.
Paths come from the repository package-file index for the observed builds. They describe archive/package associations, not every file that will exist on a running system after maintainer scripts, alternatives, generated state, diversions, or installation choices.
OpenFactory peut démarrer ce système d'exploitation dans une machine virtuelle du navigateur, ou lancer une construction qui inclut le nom natif du paquet de cet enregistrement.
Chaque ligne est une métadonnée d'index pour une version, une architecture, une suite et un dépôt. Noms, URL et tailles viennent de la source ; un lien est un emplacement de récupération mutable, pas une redistribution OpenFactory.
