Using chromaphone 3 as a plug-in, Audio and midi configuration, Automation – Applied Acoustics Systems Chromaphone 3 Upgrade Acoustic Object Synthesizer Plug-In (Download) User Manual

Page 75: Multiple instances, Midi program change, Saving projects, Using, Chromaphone 3, As a plug-in, 9using chromaphone 3 as a plug-in

Advertising
background image

Using

Chromaphone 3

as a Plug-In

75

9

Using

Chromaphone 3

as a Plug-In

Chromaphone 3

is available in VST2, VST3, AAX and Audio Units formats and integrates seam-

lessly into the industry’s most popular multi-track recording and sequencing environments as a
virtual instrument plug-in.

Chromaphone 3

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 3

.

9.1

Audio and MIDI Configuration

When

Chromaphone 3

is used as a plug-in, the audio and MIDI ports, sampling rate, buffer size,

and audio format are determined by the host sequencer.

9.2

Automation

Chromaphone 3

supports automation functions of host sequencers. All parameters visible on the

interface below the

Utility

section and related to the synthesis engine can be automatized, in other

words parameters from the

Home

and

Editor

views.

9.3

Multiple Instances

Multiple instances of

Chromaphone 3

can be launched simultaneously in a host sequencer.

9.4

MIDI Program Change

MIDI program changes are supported in

Chromaphone 3

. When a MIDI program change is re-

ceived by the application, the current sound used by the synthesis engine is changed to that having
the same index, in the currently loaded pack, as that of the MIDI program change message.

In order to use MIDI program changes, make sure the

Enable Program Changes

option is

selected in the

Settings

view as explained in section 6.1.

9.5

Saving Projects

When saving a project in a host sequencer, the currently loaded sound 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 packs 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 pack you are using in your
project still exists on your disk when you reload the project. The sounds must also exist and be in
the same order as when the project was saved.

Advertising