CONCEPTS - Introduction
The Trilian Total Bass module, based on the Spectrasonics STEAM™ Engine, has been designed as a flexible and expressive bass instrument, specifically for performing and composing using Acoustic, Electric and Synth Bass sounds.
The interface has been designed to allow a wide range of operation, from basic interaction with Factory Patches, to comprehensive and complex sound modification and performance tools. Overall, the Trilian interface provides an accessible and intuitive workflow, but it also offers as much depth and flexibility as a User needs for their desired application.
The "STEAM Engine" is Spectrasonics latest core software technology, created by the company"s in-house development team. The STEAM engine was developed from the ground up to be used as the basis of all future Spectrasonics performance instruments, just as its core S.A.G.E. technology is used for groove-based instruments like the popular Stylus RMX.
STEAM is important to Spectrasonics future because it completes the technology transition from earlier performance virtual instruments that were based on the licensed UVI Engine.
Virtual instruments built with the multitimbral STEAM Engine offer many development possibilities into a variety of hybrid synthesis and control capabilities including high-resolution Streaming Sample Playback, Integrated FX, Variable Waveshape synthesis, Granular synthesis, FM synthesis, polyphonic Ring Modulation, Timbre Shifting, and a comprehensive Flex-Mod™ modulation routing system, to name a few.
"The STEAM Engine core technology gives us the ability to respond to other technology changes like 64-bit computing, or a major new operating system," said Eric Persing, Founder and Creative Director of Spectrasonics. "This new in-house technology will allow us to create instruments that we can fully support across industry changes and allow us to make innovations and future transitions faster. For example, just as Stylus RMX being based on our S.A.G.E. technology made possible the early compatibility with Apple's Intel-Macs, new instruments based on STEAM technology will make transitions like this easier on our customers."
In the past, Spectrasonics has licensed its core technology to create some of its virtual instrument products. Now with STEAM, new products are being created from the ground up that support our long-term vision of the highest-quality sounds and the most musically intuitive user experience. Virtual instruments powered by STEAM also have unlimited expansion possibilities. The new core software is flexible and open - allowing patches to be shared across hosts and computer platforms. Spectrasonics can also add new patches and sounds to the core library giving the user an ever-expanding sonic palette. In addition, all Spectrasonics virtual instruments based on S.A.G.E. and STEAM technologies can interact in musically useful and innovative ways for a smoother workflow and new creative possibilities.
Currently, Omnisphere and the Trilian Total Bass Module are powered by STEAM.
The MULTI is at the top of Trilian’s hierarchy and consists of up to eight Parts, together with four Aux FX Racks and a Master FX Rack.
The Multi Section contains four pages: MIXER, FX, LIVE and STACK. These allow access to a full-featured MIXER, the Multi FX, and two flexible performance modes: LIVE MODE and STACK MODE, which provide interactive environments for both composition and live performance. These sections are covered in detail in their respective sections of the Reference Guide.
Saving a MULTI is like saving the entire state of the plug-in for future recall. A MULTI stores all of the settings from the MIXER page, the Multi FX, the LIVE MODE and STACK MODE pages, all MIDI Learn assignments, and all of the settings (including any unsaved edits) for each of the eight Parts.
All of Trilian’s settings are saved and recalled with a project in your plug-in host software.
Saving an individual MULTI lets you recall the entire saved state of the plug-in and load it at a later time into new instances of Trilian (or new projects) by loading the MULTI from the MULTI Browser.
Trilian is a multi-timbral instrument, allowing up to eight different Parts to be played at the same time within a single instance of the plug-in.
Each of the eight Parts can be thought of as an entire instrument, complete with its own Soundsources, modulation routings, and FX, and each Part can be played on a different MIDI channel.
The settings of all eight Parts are saved with a MULTI, or with your project. Everything will be recalled by loading that specific MULTI or project. The settings of a Part can also be individually saved as a Patch.
A Patch contains all the settings that make up a sound, and can be individually loaded into any of the eight Parts.
Each Part has two Layers (A and B), and each Layer has its own set of parameter controls.
Each Layer uses its own polyphonic Soundsource as a primary sample-based oscillator.
To learn more, please refer to the extensive Soundsource section of the Reference Guide.
NOTE: It isn’t necessary to use both Layers when creating sounds. In fact, very complex sounds can be achieved using only one Layer.
.....
Each Layer has an independent set of parameter controls, and there are many parameters that will only affect the individual Layer. However, there are also a number of Common parameters that are shared by both Layers in a Part.
If a parameter is numbered, then it’s a Common parameter that applies to both Layers (ex: LFO 1 ~ 6, Mod Env. 1 & 2). If it isn’t numbered, then it’s specific to the Layer (ex: Amp Env., Filter Env.).
Common parameters include the six LFOs (LFO1 ~ LFO6) and the two Modulation Envelopes (MOD 1 & MOD 2).
In addition, each Layer has its own FX Rack, and there is a Common FX Rack that is shared by both Layers. FX Architecture
CONCEPTS - Soundsources
Soundsources in Trilian are typically quite large, and can be made up of thousands of samples. A Soundsource can include chromatically sampled, velocity-switched multi-samples mapped across the full range of the keyboard, multiple channels for Mic and Direct Pickup Input (DI) sources, plus Round Robin samples, Legato samples, and articulations such as Release Noises, Slides, and other performance effects. All of these can be included when you load a single Soundsource!
Soundsources are based on a ‘map’ of audio samples stored in Trilian’s ‘Core Library’ in the proprietary Spectrasonics STEAM format. Each Soundsource was carefully prepared and optimized by the Spectrasonics Sound Development team.
Larger and more complex Soundsources take a bit longer to load, but still load relatively quickly, since the STEAM Engine includes “streaming” technology to allow for playback of very large multi-samples.
Streaming allows for the samples to buffer off of the computer’s hard drive in real time, instead of all of the samples having to be loaded into the computer’s physical RAM first.
Still, very large Soundsources can demand a great deal of a system’s Memory resources. Trilian includes useful controls for memory management and “sample thinning”, which allow you to reduce the number of samples that will load with a Soundsource, giving you just the sound you need while allowing conservation of system resources.
Soundsources in Trilian are somewhat similar to “programs” in some samplers, but there are some key differences:
1. A Soundsource contains not only all of the raw samples and mapping information, such as pitch, velocity, zones, and loop points – but also Soundsource images, notes and tags.
2. Soundsources do not include envelopes, filters, LFOs, FX or any modulation settings (which are stored in the Patch instead).
For this reason, you can load a new Soundsource into a Layer without changing any of the Layer’s parameter settings. This is extremely useful because you can take any Patch you like and create countless variations on it simply by changing the loaded Soundsource! This is something like changing waveforms on an analog hardware synth, but with far more possibilities.
Spectrasonics is constantly improving and adding to the Factory Soundsource Library, so make sure you stay up to date with the “Check for Updates” feature.
The top area of the Trilian interface is the Header. The Header is visible from any page in Trilian, and is the primary navigation area of the interface.
The Header contains the Utility Menu, Multi Information including the Multi Name Display and access to the MULTI Browser, indicators for when LIVE MODE or STACK MODE are enabled, and Navigation Buttons for selecting any of the 8 Parts, the MULTI Section or the SYSTEM Page. Finally, there is a Master Volume Control for adjusting the overall output level.
The Utility Menu has three sections. The first is a MIDI Learn sub-menu. The second provides various Clear, Save, Copy & Paste functions for Multis, Patches, Parts and Layers. The third section provides direct access to the Trilian Reference Guide.
The Utility Menu provides the MIDI Learn and Automation options that apply to the whole plug-in. These include MIDI Learn Templates, Unlearn All, and access to a ‘Current Assignments’ Report. See the MIDI Learn & Automation section for details.
The Utility Menu provides options to Initialize or Clear Multis, Patches and Layers, and to Save Multis and Patches. There are also functions that allow Part and Layer settings to be copied and pasted.
Initialize vs Clear (Multi, Patch & Layer)
When you select Initialize (Initialize Multi, Initialize Patch or Initialize Layer), all synthesis parameters for the Multi, Patch or Layer, including FX and Modulation routings will be restored to an unedited 'default' state, including a default Soundsource loaded as a starting point.
When you select Clear (Clear Multi, Clear Patch or Clear Layer), all existing parameters for the Multi, Patch or Layer will be completely cleared, using no sounds or memory.
In all cases, the Mixer settings are retained
NOTE: When using the Clear function, no sounds are loaded, so no sound will be heard from the Multi, Patch or Layer until a Soundsource is loaded.
Initialize Multi
Initializes all current Multi settings, including all Parts and FX. The Multi is returned to an unedited ‘default’ state, including default sounds.
Clear Multi
Clears all current Multi settings, including all Soundsources, Parts and FX. This will result in a completely empty Multi.
Save Multi
Selecting the Save Multi option will open a File Save dialogue. After naming and saving the MULTI, the EDIT TAGS interface will open, allowing you to assign various Attribute Types and Assignments, add custom Assignments, and add your own Keywords and Notes to the MULT
Once you have finished editing the tags, click the SAVE button to finish saving the MULTI. You may also cancel the save process by clicking the CANCEL button.
When saving a MULTI, the entire state of the plug-in is saved. This includes the MIXER, LIVE MODE and STACK MODE settings, Multi FX, MIDI Learn assignments, as well as all Part settings. Even if a Part has been modified but not yet saved as an individual Patch, its settings will also be saved with the MULTI.
Initialize Patch
Initializes all current Patch settings, including all Modulation routing and FX. The Patch is returned to an unedited ‘default’ state, including the default sound
Save Patch
Selecting the Save Patch option will open a File Save dialogue. After naming and saving the Patch, the EDIT TAGS interface will open, allowing you to assign various Attribute Types and Assignments, add custom Assignments, and add your own Keywords and Notes to the Patch.
NOTE: Patches must be saved into a Category folder in the STEAM folder. This can be either an existing folder, or a user-created folder inside the Patches folder
Once you have finished editing the tags, click the SAVE button to finish saving the Patch. You may also cancel the save process by clicking the CANCEL button.
Save Patch Quick
When editing an already saved Patch, the new changes can be saved without having to bring up the save dialogue and Tag Editor. Save Patch Quick will simply overwrite the previous version. A confirmation dialogue will pop-up to confirm the save.
Copy Part
This command is used to copy the settings from a single Part. These settings can then be pasted to another Part using the Paste Part command. To copy a Part, select the Part using the Navigation Buttons in the Header, and then select the Copy Part command from the Utility Menu.
Paste Part
After a Part has been copied using the Copy Part command, it can be pasted to another Part. To paste a copied Part, select the destination Part using the Navigation Buttons in the Header, and then select the Paste Part command from the Utility Menu.
Initialize Layer
Initializes all settings for the selected Layer, including Modulation routing and FX. The Layer is returned to an unedited ‘default’ state, and includes the default sound.
Clear Layer
Clears all settings for the selected Layer, including all Soundsources, Modulation routing and FX. This will result in a completely empty Layer.
Copy Layer
This command is used to copy the settings from a single Layer. These settings can then be pasted to another Layer using the Paste Layer command. To copy a Layer, select it using the Layer tabs in the Edit Page, and then select the Copy Layer command from the Utility Menu.
Paste Layer
After a Layer has been copied using the Copy Layer command, it can be pasted to another Layer. To paste a copied Layer, select the destination Layer using the Layer tabs in the Edit Page, and then select the Paste Layer command from the Utility Menu.
NOTE: Modulation Routings are not included with the settings that are copied and pasted using the Copy/Paste Layer commands.
Selecting this option from the Utility Menu will open this HTML Reference Guide for Trilian. The Reference Guide will be displayed using your default Web Browser.
The Reference Guide is indexed, so you can search the Guide, print chapters (click the Print Icon next to any chapter to load printable pages), or save it as a PDF. Refer to your system guide for how to create PDFs.
The Guide is in HTML format, so is portable and can be opened with any Web Browser. This makes it easy to keep up to date, and is very convenient for users. For example, it can be copied to a mobile computer for reference, separate from the plug-in.
The Reference Guide files are found inside the STEAM/Trilian folder, under Documentation.
Windows:
C:\Program Files\Spectrasonics\STEAM\Trilian\Documentation\Reference Guide\index.html
Mac:
Macintosh HD/Users/Username/Application Support/Spectrasonics/STEAM/Trilian/Documentation/Reference Guide/index.html
When either LIVE MODE or STACK MODE is enabled, you’ll see “LIVE MODE” or “STACK MODE” displayed on the left side of the Trilian header.
This part of the Header contains the Multi Name Display, Multi Steppers, and a Folder icon for access to the Multi Browser.
Selecting the Folder icon, or anywhere inside the Multi Name Display, will open the Multi Browser. After a MULTI has been loaded, the name of the MULTI will be displayed in the Multi Name Display.
The Multi Stepper buttons (up/down arrows) will load the next or previous MULTI from the Library, based on the current filtered results in the Multi Browser. The buttons step through the available MULTIS one at a time.
The Navigation Buttons in the header are used to select and view any of the eight Parts, the Multi Section or the System Page. Only one button can be selected at a time.
Part Select Buttons (1 ~ 8)
Buttons 1-8 are Part Select Buttons. Selecting a Part lets you access and view any of the pages for that Part, including the MAIN page, EDIT page, Patch FX pages, and the Arpeggiator Page.
MULTI Button
Selecting the MULTI button gives you access to any of the pages in the Multi Section, including the MIXER, Aux/Master FX, and the LIVE MODE and STACK MODE pages.
SYSTEM Button
Selecting the SYSTEM button opens the System page, which contains preferences and settings for the entire plug-in.
The Master Volume slider controls the output of the whole plug-in, and includes a meter, which provides a reference to the output signal. The range of the Master Volume slider is –inf dB ~ 9.54 dB.
A downward facing arrow indicates that a drop-down menu is available. There are numerous drop-down menus in the Trilian interface, which provide access to settings, Presets, MIDI Learn, Automation and other functions.
Contextual Menus are an important part of the Trilian interface, and provide convenient access to many important functions.
Right/Control-clicking almost anywhere in the Trilian interface will bring up a contextual menu. The contents of the menu will depend on where the cursor is placed when the contextual menu is opened.
For example, Right/Control-clicking over a blank area of the Trilian Header will reveal the Utility Menu. Right/Control-clicking a knob or slider will typically reveal a menu of MIDI Learn, Modulation & Automation options.
....
Steppers (up/down arrows) are located throughout the Trilian interface, and are used to step through values or load saved settings, incrementing or decrementing one at a time. In the picture on the left, clicking the arrows will step through the different LFO waveforms available.
One of the features of Trilian’s interface design is that it only reveals its depth and complexity on an as-needed basis. The Zoom Icon Buttons provide access to Zoom Views, where you can view expanded information or interact with Trilian’s more advanced features.
A magnifying glass icon next to a function indicates that a Zoom View is available. Selecting the icon with a ‘+’ inside it opens the Zoom View for that function. When a Zoom View is open, selecting the magnifying glass icon with a ‘-‘ inside it, closes the Zoom View.
Zoom Views are available for Modulation, Filters, Envelopes, Velocity Curves, Soundsource Edit and Info, Patch Info, MULTI Info and LIVE MODE settings.
There are also Zoom Buttons in the Browsers that access Browser settings, Lite Version options, the Tag Editor, and Multi, Patch or Soundsource Info.
There are three Browsers built in to Trilian, one each for Multis, Patches, and Soundsources. All three Browsers have identical functions, but access different parts of the Core Library.
Anywhere that you see a Folder icon, you will be able to access a Browser by clicking on the Folder. If there is a Name Display next to the Folder icon, you can also click inside the Name Display to open the Browser.
Multi Browser
The MULTI Browser can only be accessed from the main Header, but is always visible and available from any page in Trilian.
Patch Browser
The Patch Browser is accessed from the Patch Name Display, and when a Part is selected (using the Part 1 ~ 8 Buttons) is always visible and available from any of the Part pages.
The Patch Browser can also be accessed from the Mixer page (Patch Name Displays), and from the LIVE MODE page when Mixer Controls are enabled.
Soundsource Browser
The Soundsource Browser is accessed from either the Main Page or the Edit Page.
To learn more about the Browsers in Trilian, please see the Browser section of the Reference Guide.
Using a mouse, Knobs and Sliders (vertical and horizontal) are adjusted by clicking and dragging. Shift-click and drag for more precise adjustments. Most Knobs and Sliders in Trilian can be MIDI Learned for direct control from a MIDI device.
Knobs
Vertical Sliders
Horizontal Unidirectional Slider
Horizontal Bidirectional Slider
Mini Sliders
Adjusting Knobs and Sliders will display their current setting or value in a floating display above the controls. Holding down the SHIFT key while adjusting Knobs and Sliders allows for more precise adjustments.
Buttons are used for choosing sections or selecting from among multiples of a single type. When selected, Buttons will be highlighted in blue. For example, there are 6 LFO Buttons. When one of them is highlighted it means it is selected, and that LFO’s settings are displayed.
Page Buttons (raised button)
Sub-Page Buttons (smaller raised buttons select sub-pages)
Switches let you toggle certain parameters on and off or switch between multiple options. When a parameter is enabled or selected, the switch will be highlighted. For example on the Main Page, Switches toggle between IMAGE and INFO views, toggle LFO Sync on and off, or select between Velocity Curve settings. Power Buttons are also a type of Switch, an example being the FILTERS On/Off Button.
Mode Switches (flat buttons that are side-by-side are Mode Switches)
Switches (flat buttons which are separated are On/Off Switches)
Power Switches
Indicator Switches are both a status indicator and a toggle. A good example of an Indicator Switch is found on the Edit Page, below each of the Soundsource sub-page Buttons; MAIN, FM & MULT. These indicate whether the feature is enabled or not, and double as a toggle to enable/disable them.
There are a number of Trilian functions that are modified by combining a mouse-click (or click and drag) with one of three Key Modifiers; the Command/Control key, Shift key, or the Option/Alt key. In the manual these are referred to as:
Control-Click (Mac users, use Command-click)
Sliders & Knobs: resets the slider or knob to a neutral or default position.
Browsers: allows selection of multiple Attributes.
Envelopes (editing): Control-click and drag to engage the Lock function.
Shift-Click
Sliders & Knobs: Shift-click and drag allows finer and more precise adjustments to values.
Envelopes (editing): Shift-click and drag to engage the Zoom X/Y function.
Option-Click (PC users, use Alt-click)
Envelopes (editing): Option-click to engage the Snap function.
Knobs: temporarily switches from linear mode to circular mode.
In linear mode, clicking on the knob and dragging vertically or horizontally with the mouse moves the knob. In circular mode, option-clicking on the knob and dragging in a circle around the knob will move it.
To switch to circular mode, hold down the Option/Alt key then click and drag the knob. You can then release the Option/Alt key.
The knob will remain in circular mode until you release the mouse button. The knob will then automatically revert to linear mode.
NOTE: Trilian defaults to linear mode. Your host may determine a different default mode, but you can still temporarily switch to the alternate mode by using Option-click.
CONCEPTS – Parameter Control
Understanding Parameter Control
There are three ways to control parameters in Trilian: Modulation, MIDI Learn and Host Automation.
Deciding which type of Parameter Control to use depends on a number of factors including which host you use, which parameters you want to automate and what type of physical controller (if any) you wish to use to control the parameters. Here are some guidelines:
Modulation
Modulation offers the most sophisticated method of controlling Trilian’s parameters. This method allows scaling, can use almost any MIDI Message (Wheel, Pitch Bend, Aftertouch, Notes, etc.), and is saved/recalled with each Patch.
To learn more about Modulation, please refer to the Modulation section.
Host Automation
With Automation messages, changes made to parameters using the mouse can be recorded in the host software. Parameter adjustments are typically written to an automation track, and in some hosts, you can draw the automation curves directly into the track. This method is most useful for mixing and fine tuning parameter changes over time on an existing performance in your host.
MIDI Learn
MIDI Learn enables full remote control of Trilian’s parameters from MIDI Devices. Almost any parameter in Trilian can be MIDI Learned. MIDI Learn assignments are saved with the Multi or with your project. This method is ideal for live performance or recording MIDI-controlled changes into your host on the fly. Parameter adjustments using MIDI Learn are typically written to a MIDI Track in the host software. MIDI Learn assignments for the plug-in can also be separately saved and loaded as Template Presets.
Right/Control-clicking a parameter in Trilian opens a contextual menu that offers options for all three methods of Automation: Modulation, MIDI Learn and Host Automation.
Host Automation and MIDI Learn give you the ability to control almost any of the parameters of Trilian and to record and edit any adjustments in your host.
NOTE: After setting up all of your MIDI Learn and Host Automation assignments, you can save a Default Multi, which will load all of your custom assignments each time you open a new instance of Trilian.
All MIDI Learnable parameters in Trilian can also be automated using the Host Automation feature. Each host handles Host Automation differently, so it’s important to understand how your specific software will interact with Trilian.
Enabling Host Automation
To make a Host Automation assignment for a parameter in Trilian, Right/Control-click a parameter to open its contextual menu, and then select the Enable Host Automation option.
The parameter will be assigned the next available Host Automation ID number, from lowest to highest. Once assigned, changes made to the parameter using the Trilian interface can be recorded in real time in the host software.
NOTE: If your host doesn’t display Host Automation assignments by name, use the MIDI Learn Report to display the parameter names along with their corresponding Host Automation ID numbers.
All Host Automation assignments are stored with the Multi, saved with the host project file, and can also be saved with a MIDI Learn Template.
NOTE: You can enable up to 128 Host Automation parameters. If you need more than 128 assignments, consider using MIDI Learn together with Host Automation.
Technical Considerations
There are 128 parameter slots in Trilian that can be automated, numbered from 0 to 127. These slots correspond to the list of parameters that can be automated in the host or on your control surface. For example, slot 0 is the first parameter in the host or on the control surface, the next one is number 1, etc. You can assign any parameter in Trilian to one of these slots using “Enable Host Automation”. The parameter will be assigned to the next available slot and may then be automated from the host or control surface. Automation ID numbers correspond to the ordered list of parameters that can be automated in the host or on a control surface.
Parameter automation is capable of two-way communication. If your host and control surface support it, your control surface can display the names of the parameters controlled by each knob or fader, and each control can automatically update to show the current value of a parameter. For example, Mackie Control displays and automatically updates parameter names in real time. Motorized faders can move to show the current values of parameters, which is very useful when opening songs that contain plug-ins controlled by the surface.
Some hosts have a limit on the number of parameters that are available to be Host Automated. For example, some only permit the first 128 parameters of a plug-in to be automated. In others, the limit is 1024 parameters. By comparison, Trilian has nearly 20,000 parameters!
If you’re working in a host that limits the number of automation parameters, you can also use the MIDI Learn feature of Trilian to automate Trilian’s parameters. The combination of Host Automation and MIDI Learn gives you powerful real-time control of virtually every parameter of Trilian.
Host-Specific Notes
• Ableton Live - After Enabling Host Automation for a specific parameter, it is necessary to also move that parameter in the Trilian interface to complete the assignment. With Live 8, Ableton also offers a new “Configure” mode, which allows you to assign host automation directly from within the host.
• Logic - After setting up all of your MIDI Learn and Host Automation assignments, you can save a Default Multi, which will load all of your custom assignments each time you open a new instance of Trilian. Users of Logic 8 and above will see all learned Host Automation parameters by name upon load.
MIDI Learn is an immensely powerful feature that allows you to remote control virtually any on-screen parameter with a MIDI controller. It is a very flexible system that can adapt to the MIDI device you use and allows changes made to any learned parameter to be recorded by the host application.
While Host Automation support varies widely among hosts, almost all hosts have the ability to record and edit MIDI messages received from a MIDI controller.
The basic process of pairing a physical control to an Trilian parameter using MIDI Learn is extremely simple:
- Right/Control-click an Trilian parameter.
- Select MIDI CC Learn (or MIDI Note Learn) from the contextual menu.
- Move a physical control (or play a note) on the MIDI device that is connected to Trilian.
The Trilian parameter will be instantly paired, and can then be controlled using that physical control. All MIDI Learn assignments are stored with the MULTI, saved with the host project file, and can also be saved as a MIDI Learn Template.
Key MIDI Learn Concepts
There are a few key MIDI Learn concepts that will help to understand how flexible the system is:
All Learnable parameters can be controlled using MIDI Learn, and are also available for use with Host Automation.
A single physical control can be paired with multiple parameters in Trilian. For example, a single physical knob could be setup to control both Cutoff and Resonance.
A single parameter in Trilian can be controlled by multiple physical controls. One useful way to use this is to create sub-mixes using the Mixer. You can ‘gang’ different groups of Part levels in the Mixer, each controlled by a single physical fader. For example, Parts 1 ~ 4 controlled by one fader, and Parts 3 ~ 6 controlled by a second fader. In this example, two different physical faders would control Parts 3 & 4.
A MIDI device sending on any MIDI channel can control MIDI Learned parameters on any of Trilian’s Parts/MIDI Channels. This means that you can use a MIDI device with all of its controls assigned to a single channel, but still control any parameter on any of Trilian eight parts.
Assignments can be made to receive in MIDI Omni mode so that when a sequencer’s track is changed, all of the controls are still active regardless of the incoming MIDI channel assignment.
MIDI Control Change, Notes and Program Change messages are supported, but Pitch Bend and Aftertouch messages are not currently supported in the MIDI Learn system.
Utility Menu
The Utility Menu provides MIDI Learn options that affect the entire plug-in. These include MIDI Learn Templates, Unlearn All, and the MIDI Learn & Automation Report (Show Current Assignments). The Utility Menu is opened from the Header, or by Right/Control-clicking any empty area of the Trilian interface.
MIDI Learn Template
All MIDI Learn & Automation assignments are saved with a MULTI, but there are times when it makes sense to save a MIDI Learn & Automation configuration for use with another project or environment.
MIDI Learn & Automation Templates allow custom setups to be saved and easily recalled whenever they’re needed.
Select ‘Save Template’ from the MIDI Learn & Automation sub-menu, to store all current MIDI Learn & Automation assignments for later recall. Selecting this option will open a File Save dialogue, allowing the Template to be named and saved.
Select ‘Load MIDI Learn Template’ to load a previously saved Template. Any existing MIDI Learn assignments will be replaced with the assignments stored in the Template. Selecting this option will open a File Load dialogue, allowing a saved Template to be loaded.
NOTE: Before saving a MIDI Learn Template, you can use MIDI Learn Report (see below) to preview the assignments that will be saved with the Template. This is also a convenient way to verify assignments after a MIDI Learn Template has been loaded.
Unlearn Next MIDI Device
When a physical controller has been MIDI Learned, you can use this option to Unlearn it. To accomplish this, select Unlearn Next MIDI Device from the menu, then move the physical controller on your MIDI Device.
Using MIDI Learn, a single controller can have more than one parameter assigned to it. This option is especially convenient if you are controlling more than one parameter with a single physical controller. It allows you to clear all assignments for the specific controller, without having to Unlearn each parameter individually.
Unlearn Next Parameter
When a parameter in the Trilian interface has been MIDI Learned, you can use this option to Unlearn it. To accomplish this, select Unlearn Next Parameter from the menu, then select and move the parameter that you wish to Unlearn.
This is a useful feature when you have more than one parameter assigned to a single physical controller. A single parameter can be Unlearned, while the rest will remain assigned to the physical controller.
Make Controls Omni
Assignments can be made to receive in MIDI Omni mode so that when a sequencer’s track is changed, all of the controls are still active regardless of the incoming MIDI channel assignment.
Trilian is MIDI input channel sensitive when MIDI Learning. This means that it can distinguish between a button transmitting Ch 1 and the same button transmitting Ch 2.
Selecting this option allows all non-cloned MIDI Learn settings to respond to any incoming MIDI channel (e.g. MIDI Omni mode reception). This is very useful when you want Trilian to respond to an external control regardless of the current incoming MIDI channel.
Unlearn All
Selecting this option will clear all existing MIDI Learn and Automation assignments.
Clone Part 1 Learns
Use this option to clone all non-omni Part 1 MIDI Learn assignments to all other Parts in the Multi, and across all other MIDI channels.
Show Current Assignments
Show Current Assignments displays all existing MIDI Learn & Automation assignments as a formatted report. The information will be displayed using your default Web Browser.
This is especially useful for checking existing MIDI Learn & Automation assignments before saving a MULTI or a MIDI Learn & Automation Template, or to verify assignments after loading a MIDI Learn & Automation Template.
NOTE: If your host doesn’t display Host Automation assignments by name, use Show Current Assignments to display the parameter names along with their corresponding Host Automation ID numbers.
Ignore Assignments When Loading Multi (Toggle)
When loading a MULTI, this option determines whether Trilian will ignore or load the MIDI Learn assignments that were saved with the MULTI.
When the Ignore Assignments option is enabled (indicated by a checkmark displayed next to it in the menu), Trilian will ignore any MIDI Learn assignments that were saved with the MULTI. Instead, all existing assignments will be retained.
When the Ignore Assignments option is disabled (no checkmark next to it in the menu), Trilian will replace all existing assignments with the MIDI Learn assignments that were saved with the MULTI.
NOTE: The Ignore Assignments option retains its setting across sessions. If you find that MIDI Learn assignments aren’t behaving as expected after loading a MULTI, please verify that the Ignore Assignments option is properly set.
CONTEXTUAL MENU
Contextual Menus provide parameter-specific MIDI Learn options, and include Modulation and Host Automation options as well.
If a parameter can be MIDI Learned, the following MIDI Learn options will be available when you Right/Control-click directly on the parameter:
MIDI CC Learn
Select this option, then move or press a control on your MIDI controller. The control will then be paired with the Trilian parameter.
MIDI CC Learn Inverted
When you select this option, then move or press a control on your MIDI controller, the control will be paired with the Trilian parameter. However, the values will be inverted. For example, as you increase the value of the physical control, the value of the Trilian parameter will decrease.
MIDI Note Learn
Select this option then play a note on your MIDI controller. That Note will then control the assigned Trilian parameter. Once a Note has been MIDI Learned it will no longer trigger a sound when Trilian receives Note On messages from that Note, it will only control the assigned parameter.
MIDI Note Learn Inverted
When you select this option, then play a note on your MIDI controller, that Note will then control the assigned Trilian parameter. However, the values will be inverted. Once a Note has been MIDI Learned it will no longer trigger a sound when Trilian receives Note On messages from that Note, it will only control the assigned parameter.
NOTE: When you MIDI Learn a variable range parameter (such as a knob or slider) using MIDI Note Learn, the Note On/Off messages will toggle the parameter to its maximum and minimum positions respectively. When using MIDI Note Learn Inverted, the values are reversed, so Note On would toggle to the minimum value, Note Off would toggle to the maximum value.
Unlearn
Select this option to clear all MIDI Learn assignments, including Host Automation assignments, for this parameter.
Show Learns
Use this option to show all MIDI Learn assignments for this parameter. A pop-up dialogue will open showing all CC and/or Note numbers assigned, or will notify you if there are no current assignments.
Soundsources in Trilian can be extremely large, some are many Gigabytes in size, and can contain over 10,000 samples! So it’s to be expected that Patches in Trilian will use more system memory than the average Patch in most other plug-ins.
For this reason, we have included a number of memory management features that you can enable in Trilian to help manage memory resources.
Generally speaking, using Trilian under regular circumstances doesn’t use a lot of CPU power. For those circumstances where CPU and memory conservation are necessary, the following detailed tips and techniques will be especially useful.
64-bit Instruments & Hosts
If you are using a 64-bit host (such as Logic 9.1), it can access all available system memory without the usual 3Gb limit. This means that you are less likely to run out of memory when loading very large instruments, or a large number of instances. If you find yourself running low on memory, you should add as much physical RAM as possible to get the most from your 64-bit software.
All Spectrasonics instruments are 64-bit, on both Mac and PC.
Sample File Server (Mac only)
For Macs running 32-bit host software, the Sample File Server allows you to load large sounds into physical RAM, bypassing the usual 32-bit System Memory limit. It is recommended to have a minimum of 6Gb of RAM installed when using the Sample File Server.
Windows users should use 64-bit host software.
NOTE: If you are running a 64-bit host (such as Logic 9.1), the Sample File Server is unnecessary, and you may get better performance with it disabled.
Sample Thinning
Sample Thinning is a very important concept in Trilian, and allows Soundsources, Patches, and Multis to load with fewer samples when selected, so that less system memory is used.
Trilian provides Thinning options from the System Page, the Edit Page (Soundsource Zoom Edit View), and from the Patch & Multi Browsers (Lite Version Options Zoom).
There are four types of Sample Thinning available; Round Robin samples, Legato samples, Velocities, and Pitch Thinning.
Using Thinning can make a huge difference in overall system memory demand, and these can be used in combination to balance between the best sound possible, and the conservation of resources.
Host Buffer Size
Performance and CPU load with all virtual instrument plug-ins are sensitive to the host's audio buffer size - particularly with an instrument as powerful as Trilian. If you experience performance issues with Trilian such as audio drop-outs, you can gain further Performance headroom by raising your host's audio buffer setting. A setting of 256 is usually a good compromise between good performance and acceptable latency, but you may wish to increase the buffer size if you need more CPU power. Trilian will also work with larger buffer sizes, so you can try adjusting this setting in your host.
Host Sample Rate
Trilian has been designed for optimal playback at 44.1k or 48k sample rate. If a host's project sample rate is higher than this, (88.2k, 96k, 192k, etc) it can have a significant impact on reducing Trilian's performance, without any real sonic benefit to Trilian. In fact, certain patches may not sound correct at higher sample rates. We recommend keeping your host's sample rate at 44.1KHz or 48KHz for the optimal experience with Trilian.
Multi-Instance vs Multi-timbral
On single and dual-core systems, it's best to load multiple Parts (on different MIDI channels) within a single instance of Trilian, before opening any additional instances of the intrument. This is the best way to utilize the available CPU power for Trilian.
However, if a multi-core system is used, it can be beneficial to open multiple instances of Trilian to distribute the processor load between the cores. The resource handling is done by the host, so in this case it's useful to open more than one instance of Trilian. So the most efficient use on a multicore machine is to use a couple of instances multitimbrally - if assigning all Parts to a single instance is using up all the resources of a single core. Consult your host's documentation to make sure that it has support for multi-core/multi-processor systems.
Limiting Voices
Bass sounds don’t usually require a lot of polyphony, so setting the voice count to a low number can conserve CPU power.
To adjust polyphony for a Part, use the VOICES stepper on either the Main or Edit Pages.
Single Layer vs Dual Layer Patches
There’s a lot that can be done with a single Layer. If you can achieve the desired sound or complexity using one Layer instead of two, it’s likely that a significant amount of CPU power can be conserved.
Common FX vs Layer FX
Using Common FX whenever possible is a great way to save CPU power. Instead of loading separate delay units into each Layer FX Rack, try sharing a single unit in the Common FX Rack.
Unused Modulation Routings
Modulation routings sometimes use CPU power, so be sure to remove any unused routings. For example if you are modulating FM Depth with a Mod Envelope, but then decide to turn FM off, remove the modulation routing to further reduce demand on the CPU.
Bypass Unused FX
When Bypassed, FX Units do not consume CPU power. To conserve CPU power, Bypass any loaded FX when they are not in use. This especially applies to Aux Send FX, since the entire Aux Send system is enabled even if you are only using one Send.
EZ-Verb vs. PRO-Verb
EZ-Verb doesn’t necessarily use less CPU power than PRO-Verb. PRO-Verb has a variable CPU Power parameter, where EZ-Verb’s CPU Power is fixed. This parameter changes the number of reflections in the reverb signal, and a higher setting is not always a “better” sound -but more reflections require a higher amount of power to achieve. Sometimes lower CPU settings will produce a more desirable result. If PRO-verb is set to maximum CPU, it takes much more power than EZ-Verb - while lower PRO Verb CPU settings (like the default settings) can actually require less power than EZ-Verb.
Sharing FX with Aux Racks
When using FX like reverbs, it’s often better to use the reverb on an Aux Rack, instead of as an Insert. There are times when several sounds need reverb, and instead of inserting 6 reverbs into 6 individual Parts, you could instead place only one reverb on an Aux Rack and then use the Aux Sends to send all six sounds to the single reverb unit. This is far more efficient on the CPU.
Aux Sends
If you are not using the AUX Sends on the Mixer Page, make sure all of them are off (all knobs turned fully counter-clockwise). When all of the Aux Sends are off, the entire AUX system is disabled, which saves CPU power. If any of the Aux Sends is on, the entire Aux Send system on all Racks and Parts is enabled, even if no audio is passing through it.