Operation Manual

Using Chromaphone as a Plug-In 39
6 Using Chromaphone as a Plug-In
Chromaphone is available in VST and AudioUnit formats and integrates seamlessly into the in-
dustry most popular multi-track recording and sequencing environments as a virtual instrument
plug-in. Chromaphone works as any other plug-in in these environments so we recommend that
you refer to your sequencer documentation in case you have problems running it as a plug-in. We
review here some general points to keep in mind when using a plug-in version of Chromaphone.
6.1 Audio and MIDI Configuration
When Chromaphone is used as a plug-in, the audio and MIDI ports, sampling rate, buffer size, and
audio format are determined by the host sequencer.
6.2 Automation
Chromaphone supports automation functions of host sequencers. All parameters visible on the
interface can be automatized except for the polyphony settings, the bank, program and history
commands
6.3 Multiple Instances
Multiple instances of Chromaphone can be launched simultaneously in a host sequencer.
6.4 Saving Projects
When saving a project in a host sequencer, the currently loaded program is saved with the project
in order to make sure that the instrument will be in the same state as when you saved the project
when you re-open it. Note that banks of programs are not saved with the project which implies that
if you are using MIDI program changes in your project, you must make sure that the bank you are
using in your project still exists on your disk when you reload the project. The programs must also
exist and be in the same order as when the project was saved.
6.5 MIDI Program Change
MIDI program changes are supported in Chromaphone. When a MIDI program change is received
by the application, the current program used by the synthesis engine is changed to that having the
same number, in the currently loaded bank, as that of the MIDI program change message.