Steinberg VST Sampler HALION 4 Operation Manual

							51
Common Editing Methods
Using Key Commands
Key commands can be assigned to most operations that 
can be performed via the standalone panel of HALion. The 
Key Commands dialog contains a list of all available com
-
mands, arranged in a hierarchical way. When you open a 
category folder by clicking the “+” sign beside it, the items 
and functions it contains are displayed with the assigned 
key commands.
•To open the Key Commands dialog, open the Options 
editor, and click the corresponding button in the Edit sec
-
tion.
Setting Up Key Commands
1.In the Commands list on the left, select a category.
2.Click the “+” sign to open the category folder.
You can also click the global “+” and “-” signs in the top left corner to 
open and close all category folders simultaneously.
3.Select the item to which you want to assign a key 
command.
Assigned key commands are shown in the Keys column and in the Keys 
section in the top right corner.
4.Click in the “Type in Key” field, and enter a new key 
command.
You can choose any single key or a combination of one or several modi-fier keys plus any key.
5.Click the Assign button above the field to assign the 
key command to the function.
The new key command is displayed in the Keys list.
6.Click OK to close the dialog.
ÖYou can set up several key commands for the same 
function.
Searching for Functions
•To search for a specific function, enter its name in the 
search field at the top of the dialog, and click the search 
button.
Removing Key Command Assignments
•To remove a key command assignment, select the cor-
responding command in the Commands list, select the 
key command in the Keys list, and click the Delete button 
(trash icon).
Working with Presets
HALion offers two types of presets: Firstly, there are sec-
tion and module presets that allow you to store and recall 
the setup of a specific user interface component. Sec
-
ondly, there are VST presets that allow you to store and 
recall the settings relating to a program. During the setup, 
HALion installs its factory presets in a dedicated folder 
and creates a user folder for your own presets. The han
-
dling of presets is the same throughout HALion.
ÖFactory presets are write-protected, but may be over-
written when a software update is executed. Presets in 
your user folder are never changed by the software.
Section and Module Presets
MIDI and effect modules as well as many sections in the 
Sound editor, such as the LFO and the Step Modulator 
sections, come with their own preset controls.
Loading Presets
The available presets can be selected from the presets 
pop-up menu at the top right of the section module.
Load PresetSaveDelete 
						

							52
Common Editing Methods
Saving Presets
1.Click the Save button (disk icon) to open a file dialog.
2.Name the preset and click Save to save the parameter 
set as a preset.
ÖYou can modify a factory preset and save it under the 
same name in your user folder.
Deleting Presets
You can only delete user presets.
1.Click the Delete button (trash icon).
2.Click Yes to confirm.
VST Presets
Loading VST Presets
When you load a VST preset, the current program is re-
placed. Proceed as follows:
1.On the Program Tree toolbar, click the Load icon.
2.Select a VST preset and click OK.
Inserting VST Presets as Layers
1.Right-click the program or layer for which you want to 
insert the VST preset, open the “Load/Save” submenu, 
and select “Load to new Layer”.
2.Select a VST preset and click OK.
The program is inserted as an additional layer.
Alternatively, drag the VST preset from the MediaBay or 
file browser into the Program Tree, and drop it on a layer.
Replacing Programs and Layers with VST Presets
1.Right-click the program or layer you want to replace.
2.Open the “Load/Save” submenu, and select “Replace 
Program” or “Replace Layer”.
3.Select a VST preset and click OK.
Alternatively, drag the VST preset from the MediaBay or 
file browser into the Program Tree, and drop it on a pro
-
gram or layer.
Reverting to the Last Saved Program
•To revert to the last saved version of a program, open 
the context menu for the program, choose the Load/Save 
submenu, and select “Revert to last Saved Program”.
Using Automation
You can automate any program that is loaded into a slot. 
Each slot has its own set of automation parameters, i.e., 
Mute, Solo, Level, and Pan. In addition, you can automate 
the Quick Controls of the program. You can access the 
automation parameters from the automation track of your 
sequencer software.
Automation Parameters
Each slot offers the following pre-assigned automation 
parameters:
ParameterDescription
MuteThis automates the Mute button of the corre-sponding slot.
SoloThis automates the Solo button of the correspond-ing slot.
LevelThis automates the loudness of the corresponding 
slot.
PanThis automates the panorama position of the cor-responding slot.
Quick Controls 1-8This automates the Quick Controls 1 to 8 of the 
program that is loaded into the slot. 
						

							53
Common Editing Methods
Using Effects
HALion features AUX busses that can be used to realize 
classical send effects. All slot, program, and layer busses 
as well as zones can send signal portions to these busses. 
Each bus hosts up to eight insert effects, which allows 
you to set up complex effects. The busses are then routed 
to either the main plug-in output or to one of the individual 
outputs. Furthermore, the Mixer provides access to the 
master output bus. These can be used to add a global EQ 
or compressor to the signal chain, for example.
In the Mixer, you can set up insert effects for AUX busses.
Using the Insert Effect Slots
All busses, including the master bus, have eight slots for 
insert effects. The handling is the same for all slots:
•To assign an insert effect, click the effect slot, and se-
lect an effect from the pop-up menu.
•To remove an insert effect, click the effect slot, and se-
lect None from the pop-up menu.
The effect is removed, including its settings.
•To bypass an insert effect, click the bypass button in 
front of the effect name.
The bypass is active when the button lights up yellow.
•To edit an insert effect, click the “e” button of the corre-
sponding slot.
You can edit only one effect at a time. The parameters of the correspond-ing insert effect are displayed in the bottom section.
Changing the Output Assignments
•To change the output assignment of an AUX bus, open 
the Output pop-up menu, and select a different output.
Adjusting the Output Levels
•Move the fader of the AUX bus.
•Alternatively, double-click the value in the field below 
the fader, and enter a new value.
Muting AUX Busses
•To mute an AUX bus, click the Mute icon.
The icon turns yellow.
The Master Effect Bus
The master bus works similar to the AUX busses. The only 
difference you will find is that the master bus has no bus 
output selector since it is “hard-wired” to the main plug-in 
output (1/2).
Multi-Channel Effects
HALion comes with a large number of effects that are 
mainly intended for use on stereo busses. However, most 
of them can also be used on surround busses. In this case 
the effect is processed on all channels. When a bus 
changes from stereo to surround, the effect follows. For 
effects with level meters, the number of meters is adapted 
accordingly. 
						

							54
Common Editing Methods
Using MIDI Modules
The MIDI modules available in HALion range from stan-
dard modules like an Arpeggiator (the so-called Flex-
Phraser) to more dedicated modules that trigger specific 
events or deliver special modulation signals, e.g., to con
-
trol articulations of sampled instruments. In general, MIDI 
modules process the stream of MIDI events inside a pro
-
gram. In addition, they are able to produce monophonic 
modulation signals, which can be used as sources in the 
modulation matrix. MIDI modules can be assigned to the 
whole program or just a single layer. This way, you can 
process the MIDI stream of the whole program or just 
parts of it. To cover more complex tasks, multiple MIDI 
modules can be assigned in series.
Inserting a MIDI Module
1.In the Program Tree, select the program or layer where 
you want to insert the MIDI module.
2.Right-click to open the context menu, open the New 
submenu, and select “MIDI Modules”.
3.Select the MIDI module that you want to insert.
4.Repeat steps 2 and 3 to insert multiple modules in 
series.
Changing the Order of MIDI Modules
The order of the MIDI modules in the Program Tree has 
great influence on the processing of the MIDI events.
•To change the order, drag the MIDI modules to new po-
sitions in the Program Tree. The routing between the MIDI 
modules changes accordingly.
Deleting a MIDI Module
1.In the Program Tree, select the MIDI modules that you 
want to delete.
2.Open the context menu and select Delete. Alterna-
tively, press Delete on your computer keyboard.
Bypassing a MIDI Module
Any MIDI module can be bypassed. This way, you can play 
the layer without the FlexPhraser or the conditions that 
have been set with the MegaTrig module.
•To bypass a MIDI module, click the crossed out speaker 
icon in the upper right corner of the caption of the MIDI 
module.
Assigning MIDI Modules in the Modulation 
Matrix
Some MIDI modules, like the FlexPhraser, directly process 
the MIDI events. Other MIDI modules like True Pedaling, 
produce modulation signals, which you must assign in the 
modulation matrix before you can use them.
To assign a MIDI module as source or modifier in the mod-
ulation matrix:
1.In the Program Tree, select the zones you want to edit. 
Make sure that the zones are part of a program or layer 
with a MIDI module that produces modulation signals, e.g. 
True Pedaling.
2.Open the Sound editor and scroll to the Modulation 
Matrix section.
3.On the pop-up menu of the Source/Modifier column, 
open the Modulation Module submenu.
The submenu lists only the MIDI modules that belong to the same layer or 
that are higher up in the hierarchy.
4.On the submenu, select a MIDI module. 
						

							8
Importing and Exporting Samples 
						

							56
Importing and Exporting Samples
Importing Samples
HALion offers convenient functions to import samples and 
map them automatically on import. You can specify how 
the samples are mapped and also extract mapping infor
-
mation from sample file and folder names.
You can import samples into HALion using the Import 
submenu of the Program Tree context menu. In the Import 
Samples dialog, you can select the samples to import and 
make mapping settings for them.
The lower section of the Import Samples dialog contains 
the Mapping Options.
ÖOnly values between 0 and 127 can be extracted as 
MIDI note numbers for any of the parameters described in 
the following sections (e.
 g. “Number from Sample”). The 
smaller value is used as the lower limit and the higher 
number as the upper limit (e.
 g. “Sample_Name_76-121”). 
Setting the Key Range
On the Key Range pop-up menu, the following options are 
available:
ÖThe Chromatic, White Keys and Black Keys options 
alter the root key. All other options map the root key ac
-
cording to the settings you make on the Root Key menu.
OptionDescription
From Sample FileThe samples are mapped to the key range that is 
saved in the file header of the sample. If this does 
not contain any key range information, the settings 
for Start and End Key are used instead.
Text from Sample 
NameThe samples are mapped to the key range that is 
extracted from the name of the sample. This func-tion searches for a key range that is defined in text 
form, for example “Sample_Name_B2-C#3”.
Number from Sample 
NameAs above, but instead of searching for text infor-mation, this function searches for MIDI note num-bers, for example “Sample_Name_59-61”.
From Sample Name 
PatternThe samples are mapped to the key range that is 
extracted from the name of the sample according 
to the name pattern you set.
Root Key Only Each sample is mapped to its root key only.
Root Key Fill 
CenteredThe samples are mapped to their root key. The 
zones expand to the left and right from the root key 
to fill empty spaces.
Root Key Fill UpThe samples are mapped to their root key. The 
zones expand from the root key upwards to fill 
empty spaces.
Root Key Fill DownThe samples are mapped to their root key. The 
zones expand from the root key downwards to fill 
empty spaces.
ChromaticThe samples are mapped chromatically to the 
white and black keys in ascending order, starting 
at the key specified with the Start value. The root 
key is set accordingly.
White KeysThe samples are mapped to white keys in ascend-ing order, starting at the key you set with the Start 
Key parameter. The root keys are set accordingly.
Black KeysThe samples are mapped to black keys in ascend-ing order, starting at the key you specify with the 
Start Key parameter. The root keys are set accord-ingly.
FixedThe samples are mapped to the key range that you 
specify with the Start and End Key parameters. 
						

							57
Importing and Exporting Samples
Setting the Root Key
The Root Key menu and settings allow you to specify how 
the root key for the samples is obtained. The following op
-
tions are available:
ÖIf no root key information is found, the fixed root key is 
used.
Specifying the Velocity Range
You can specify the velocity range for the imported sam-
ples using the Vel Range parameters in the Import dialog. 
The following options are available:
ÖIf no information on the velocity range is found, the 
samples are mapped to the Start and End Velocity set
-
tings instead.
Obtaining Information from File and Folder 
Names
Depending on the mapping settings, the information for 
root key, key range, and velocity range is retrieved differ
-
ently for file and folder names.
Using Name Patterns
Usually, names of sample files follow a certain naming 
scheme, for example, “Sample_C3_Key_59-61_Vel_80-
100”. You can extract all this information from the sample 
file name by selecting the “From Sample Name Pattern” 
option on the Key Range, Root Key, or Vel Range pop-up 
menus and defining a pattern in the lower part of the Map
-
ping Options section.
You can use the Pattern field to manually edit your pattern 
and select variables from the pop-up menu to the right. 
For the Name Pattern to work, your files and folders must 
be named exactly as defined in the pattern, including un
-
derscores, hyphens, etc.
The following variables are available for building name 
patterns:
ÖSamples can only be mapped correctly on import if all 
samples follow the same name pattern. If no matching pat
-
tern is found, the samples use the settings for Root Key, 
Start and End Key and Start and End Velocity instead.
OptionDescription
From Sample FileThe root key is read from the file header.
Text from Sample 
NameThe root key is extracted from the file name. This 
function searches for root key information in text form, 
for example “Sample_Name_C#3”.
Number from  Sample NameThe root key is extracted from the file name, as above, 
but instead of searching for text information, this func-tion searches for MIDI note numbers, for example 
“Sample_Name_61”.
From Sample  Name PatternThe root key is extracted from the sample file name 
according to the name pattern you set.
FixedThe root key is set to a fixed key, specified in the field 
to the right.
OptionDescription
From Sample  FileThe samples are mapped to the velocity range saved in 
the file header.
From Sample 
NameThe samples are mapped to the velocity range that is 
extracted from the file name.
From Sample 
Name PatternThe samples are mapped to the velocity range that is 
extracted from the file name according to the defined 
name pattern.
From Folder 
NameThe samples are mapped to the velocity range that is 
extracted from the sample’s folder name. 
Velocity LayersThe samples are layered, that is, distributed evenly over 
the velocity range.
Fixed Velocity 
Range The samples are mapped to the velocity range speci-fied with the Start and End key values.
OptionDescription
Key Low Number $(KeyLow) The MIDI note number is extracted and is used as 
the lower limit of the key range.
Key High Number $(KeyHigh) The MIDI note number is extracted and is used as 
the upper limit of the key range.
Key Low Text $(KeyLowText) The name of the note is extracted and is used as the 
lower limit of the key range.
Key High Text $(KeyHighText)The name of the note is extracted and is used as the 
upper limit of the key range.
Velocity Low  $(VelLow)The number for the velocity value is extracted and is 
used as the lower limit of the velocity range.
Velocity High  $(VelHigh) The number for the velocity value is extracted and is 
used as upper limit of the velocity range.
Root Key Number  $(RootKey)The MIDI note number is extracted and is used as 
the root key.
Root Key Text  $(RootKeyText)The name of the note is extracted and is used as the 
root key. 
						

							58
Importing and Exporting Samples
Using the Position Setting
The Position setting determines the position in the file 
name at which the program searches for the information.
•When this is set to “0”, the entire file name is searched.
•When you select a number from the pop-up menu, the 
program starts searching after this number of characters. 
Every character is taken into account, including spaces.
The Tune and Gain Settings
The file header of the sample can contain information on 
the tuning and the gain of the sample. On import, this in
-
formation is retrieved as well.
To switch off reading the Tune and Gain information dur-
ing import, deactivate the corresponding options below 
the Pattern field.
Listening to Samples before Import
You can listen to the samples before importing them. The 
corresponding controls can be found above the Mapping 
Options section in the Import dialog.
The following controls are available:
Sample Zone Presets
When importing samples, HALion uses a “Default” zone 
preset. This sets all zone parameters to default values, but 
excludes sample-specific parameters (Sample Start, 
Sample End, Loop Start, Loop End, etc.). You can modify 
this preset in the Sound editor for a zone and save it as 
“Default” to your user preset directory. HALion then uses 
this preset instead.
Importing Folders
Usually, sample collections are organized in folder struc-
tures, where each velocity layer or each key group is 
saved in a separate folder. In HALion, you can import 
complete folders, including their subfolders.
Proceed as follows:
1.In the Program Tree, right-click the selected program 
or layer.
2.On the context menu, open the Import/Export sub-
menu, and select “Import Folder…”.
3.In the Import Folder dialog, click the button to the right 
of the Folder field, navigate to the folder that you want to 
import, and click OK.
4.Activate “Include Subfolders” to import samples from 
deeper hierarchy levels too.
5.To create layers that correspond to the hierarchy of 
the subfolders on disk, activate “Create Layers from Sub
-
folders”.
6.Set up the Mapping Options as needed.
They are identical to the options in the Import Samples dialog.
7.Click OK.
Finding Missing Samples
There might be situations where loaded programs cannot 
find the samples they use. This can happen if the refer
-
enced samples are located on a different drive and the 
drive name has changed, or because the program was 
created on a different computer system.
When this happens, the “Find Missing Sample” dialog 
opens, showing a list of all samples that are missing, with 
additional information about the format, size, and creation 
date. The list groups all samples that are located in the 
same subfolder.
Entering a Search Path
Below the list you can enter the search path to find the 
missing samples. 
ÖAll the subdirectories are searched before the results 
are displayed, therefore the search takes longer if you 
specify entire drives.
OptionDescription
PlayClick the Play button to play back the focused sample.
StopClick the Stop button to stop playback of the sample. The play 
locator jumps back to the sample start.
PauseClick the Pause button to stop playback of the sample, click 
again to continue playback.
LoopActivate the Loop button to play back the sample repeatedly.
Auto PlayActivate Auto Play to automatically start playback of the se-lected sample.
LevelThis fader adjusts the playback level.
PositionThe position slider displays the playback position within the 
sample. To select another position for playback, click on the 
slider or drag the handle to the new position. 
						

							59
Importing and Exporting Samples
Start the Search
•Once you have specified the search path, click the Start 
Search button to start the search process.
If the search only finds a single result for each missing 
sample, the sample path is automatically corrected in the 
program and the sample disappears from the “Missing 
Files” list. If all samples are found, the dialog is closed.
Using Favorite Paths
If a path might be helpful for future searches, you can add 
it to the search path list. The next time the dialog opens, it 
allows you to select one or multiple predefined paths to 
specify which places to include in the search. 
•To add a path, click the “+” sign.
Multiple Results
It can happen that samples are found in several places. If 
this is the case, an additional “Found File” list appears be
-
low the “Missing File” list. This shows the available sam-
ples and their file locations.
•To select a sample or a complete folder that is to be 
used to resolve the missing samples, double-click on it in 
the “Found Files” list. 
Each sample or folder that is resolved this way disappears from the 
“Missing Files” list. 
Once all samples are resolved the dialog closes.
Search Options
By default, HALion searches for samples that do not only 
have the same file name, but also correspond in terms of 
time, size and format information. Only if all of the informa
-
tion are identical, a sample is considered “found”. How-
ever, you can exclude this information by activating the 
“Ignore File Time and Size” and “Ignore Audio Format” op
-
tions.
Exporting Samples
Samples can be exported together with the correspond-
ing program or layer as VST presets, or on their own. In 
both cases, you use the “Export Samples…” option on the 
Program Tree context menu. For VST presets, the corre
-
sponding dialog has additional preset options.
•To export a VST preset, select the program or layer in 
the Program Tree. On the context menu, open the Import/
Export submenu, and select “Export Samples…”.
This opens the Export Preset with Samples dialog.
•To export samples without a preset, select the samples 
in the Program Tree. On the context menu, open the Im
-
port/Export submenu, and select “Export Samples…”.
This opens the Export Samples dialog.
ÖSamples loaded from HSB files or protected VST 
sound files cannot be exported.
Creating Folders using Variables
You can automatically create folders when exporting sam-
ples using variables for the Sample Path.
Proceed as follows:
1.In the Sample Path field, set the cursor at the position 
where you want to insert the variable.
2.On the pop-up menu next to the field, select a variable. 
						

							60
Importing and Exporting Samples
3.Where necessary, complete the file path by typing in a 
back-slash (Win) or a slash (Mac). 
You can combine several variables, separating them with hyphens, 
spaces, etc.
The resulting sample path is displayed in the Example 
Name field.
The following variables are available:
Renaming Samples
You can also rename the samples automatically on export 
using sample name variables. You can combine several 
variables.
Proceed as follows:
1.In the Sample Name field, set the cursor at the posi-
tion where you want to insert the variable.
2.On the pop-up menu next to the field, select a variable. 
3.If needed, add further variables. You can combine sev-
eral variables, separating them with hyphens, spaces, etc.
The resulting sample name is displayed in the Example 
Name field.
The following variables are available:
Example Name Field and Status Messages
The Example Name display informs you about the sample 
path and name resulting from your settings. 
Below, a status message informs you how many samples 
are saved and if duplicate names are created. For example, 
if two zones in the Program Tree have the same name, and 
you use the variable “$(Zone)”, this results in duplicate file 
names. However, file names must be unique. Therefore, 
the duplicate file names are automatically numbered. 
Samples loaded from HSB files or protected VST Sound 
files cannot be exported. The status message informs you 
if such protected files exist.
OptionDescription
Sample Folder $(SampleFolder)Creates a folder with the name of the folder of the 
original samples.
Layer Structure  $(Structure)Creates folders following the structure of the se-lected program or layer.
Layer Name  $(Layer) Creates a folder with the name of the layer.
Program Name  $(Program) Creates a folder with the name of the program.
Sample Rate  $(SampleRate)Creates folders that are named according to the sam-ple rate of the samples.
Bit Depth  $(BitDepth) Creates folders that are named according to the bit 
depth of the samples.
Date  $(Date) Creates a folder with the name of the current system 
date (in the format yymmdd).
Time  $(Time)Creates a folder with the name of the current system 
time (in the format hhmm).
OptionDescription
Sample Name 
$(Sample)This variable uses the file name of the original sam-ple. Use it if you do not want to modify the sample 
file names. 
Sample Folder 
$(SampleFolder) The name of the folder of the original samples is 
used in the file name.
Zone Name 
$(Zone)The name of the zone is used in the file name.
Layer Name 
$(Layer)The name of the layer is used in the file name.
Program Name 
$(Program)The name of the program is used in the file name.
Key Low Number 
$(KeyLow)The MIDI note number of the lower limit of the key 
range is used in the file name.
Key High Number 
$(KeyHigh)The MIDI note number of the upper limit of the key 
range is used in the file name.
Key Low Text  $(KeyLowText)The name of the note of the lower limit of the key 
range is used in the file name.
Key High Text  $(KeyHighText)The name of the note of the upper limit of the key 
range is used in the file name.
Velocity Low  $(VelLow)The number of the lower limit of the velocity range is 
used in the file name.
Velocity High  $(VelHigh)The number of the upper limit of the velocity range is 
used in the file name.
Root Key Number  $(RootKey)The MIDI note number of the root key is used in the 
file name.
Root Key Text  $(RootKeyText) The name of the root key is used in the file name.For example, $(Sample)_$(RootKeyText) appends 
the name of the root key to each sample file name.
Sample Rate  $(SampleRate)The sample rate of the samples is used in the file 
name.
Bit Depth  $(BitDepth)The bit depth of the samples is used in the file name.
Date  $(Date) The system date (in the format yymmdd) is used in 
the file name.
Time  $(Time) The system time (in the format hhmm) is used in the 
file name.
Option Description