Steinberg Halion 5 Manual

							71
Importing and Exporting SamplesFinding Missing Samples
Importing Folders
Usually, sample collections are organized in folder structures, 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 submenu, 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 Subfolders”.
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 referenced 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.
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. 
						

							72
Importing and Exporting SamplesExporting Samples
Multiple Results
It can happen that samples are found in several places. If this is the case, an additional 
“Found File” list appears below the “Missing File” list. This shows the available 
samples 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. A sample is considered 
“found” only if all of the information is identical. However, you can exclude this 
information by activating the “Ignore File Time and Size” and “Ignore Audio Format” 
options.
Exporting Samples
Samples can be exported together with the corresponding 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 corresponding 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 Import/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. 
						

							73
Importing and Exporting SamplesExporting Samples
Creating Folders using Variables
You can automatically create folders when exporting samples 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.
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 position 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 several variables, separating 
them with hyphens, spaces, etc.
The resulting sample name is displayed in the Example Name field.
The following variables are available:
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 selected 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 sample 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 sample. 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. 
						

							74
Importing and Exporting SamplesExporting Samples
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.
Files that are in use by HALion or another application cannot be overwritten. In this 
case, choose a different location for the samples.
ÖSome systems have problems with file names longer than 32 characters. Therefore, it 
is best to use file names that do not exceed this number.
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 
						

							75
Importing and Exporting SamplesReplacing Samples
Setting the File Format
You can export the samples as Wave or AIFF files and specify a sample rate and bit 
depth for them, if needed.
Including Zone Settings
You can include zone settings when saving the samples. When you import these 
samples back into HALion, they automatically get these settings.
The following settings can be written into the sample file:
Setting Up General Export Options
In the Export Options section, you can make general settings for the export. The 
following settings are available:
ÖIf a sample has several zones and these zones have different loop settings, HALion 
creates duplicates of the file.
Replacing Samples
The Replace Samples function allows you to exchange the sample that is used to play 
back one or multiple zones. The zone-specific settings like Pitch, Filter, or Amplifier 
are not modified by this.
Replacing a Single Sample
1.In the Program Tree or Mapping editor, select the zone for which you want to 
replace the sample.
2.On the context menu for the zone, open the submenu “Import/Export”, and select 
“Replace Sample”.
A file dialog opens.
3.Locate and select the new sample and click OK.
!Do not change the sample rate of looped samples, because this can cause audible 
artifacts.
OptionDescription
Key RangeSaves the Key Low and Key High settings of each zone with the 
samples.
Velocity RangeSaves the Velocity Low and Velocity High settings of each zone 
with the samples.
Root KeySaves the Root Key setting of each zone with the samples.
Loop SettingSaves the loop settings of each zone with the samples.
Sample TuneSaves the Tune setting of each zone with the samples.
Sample GainSaves the Gain setting of each zone with the samples.
OptionDescription
Trim SamplesTrims the samples to their actual length, specified with the Sample 
Start and Sample End parameters of the zone.
Use Exported 
SamplesUpdates the sample references of the zones to use the exported 
samples.
Avoid Duplicate 
Audio FilesPrevents samples that are used by several zones from being 
exported as duplicate audio files. 
						

							76
Importing and Exporting SamplesReplacing Samples
Replacing Multiple Samples
1.In the Program Tree or Mapping editor, select the zones for which you want to 
replace the samples.
2.On the context menu for one of the zones, open the Import/Export submenu, and 
select “Replace Samples”. 
3.At the bottom of the file dialog, select the method for replacing samples that you 
want to use.
The following methods are available:
4.Locate the new samples. 
The info text in the lower right section shows you how many samples are replaced 
in how many zones. If no samples are found, you have to select another method for 
finding matching samples.
5.Click OK.
Auditioning Samples before Replacing Them
To listen to the samples before replacing the old ones, activate the Prelisten Sample 
option and use your MIDI keyboard.
Detecting the Root Key
To listen to the samples with the correct pitch, you have to select how to detect the 
root key of the new sample. The following options are available:
OptionDescription
Replace Identical NamesThe samples are only replaced by new samples if their names 
are identical. 
Typically, this is the case if you processed the samples and 
saved them under the same name in a different location on 
your hard disk.
Replace by Root KeyThe samples are replaced by new samples that have a 
matching root key, regardless of the file name.
Replace by Search PatternThis method can be used if only parts of the sample name 
have changed, for example, due to processing or saving. 
Enter the part of the name that has changed in the text field. 
Samples are replaced if the remaining parts of the sample 
name are identical. 
For example, if the name “Sample_Mix_1_C3.wav” has 
changed to “Sample_Mix_2_C3.aiff”, enter “*Mix_2*.aiff” in 
the text field. 
OptionDescription
Root Key from 
Sample FileThe root key is read from the file header of the sample file.
Root Key Text from 
Sample NameThe root key is extracted from the sample file name. This function 
searches for the root key in text form, for example 
“Sample_Name_C#3”. 
						

							77
Importing and Exporting SamplesImporting Third-Party Sampler Programs
The “Change Sample Folder” Option
The “Change Sample Folder” option on the Import/Export submenu of the Program 
Tree context menu allows you to relocate samples. This is useful if you processed the 
samples and saved them in a new location without changing their names.
Importing Third-Party Sampler Programs
HALion allows you to import a wide range of sampler formats from third-party 
manufacturers. When importing those formats, HALion translates as many parameters 
as possible. This is described in detail in the chapter 
“Using the Browser” on page 80.
Importing Sliced Loops
HALion features a Slice Player that can play back sliced audio loops. You can import 
sliced loops in the common REX1 and 2 formats or drag and drop sliced events 
directly from Cubase.
Importing REX Loops
The import process for REX files includes several steps. First, the slice information is 
used to create a sample zone per slice. These sample zones are then mapped to the 
keyboard. The range starts with C3 and uses as many zones as slices are defined in 
the loop. The slice information is also used to create a MIDI phrase that is loaded into 
a Slice Player module.
To import REX files, you have the following options:
•Drag a REX file from the Windows Explorer or Mac OS Finder to the Program Tree 
and drop it on a program or layer.
•Open the context menu for a program or layer, open the Import/Export submenu, 
select “Import Samples…”, and select the file via a file dialog.
ÖWhen working with REX1 files, HALion can directly play audio from these files. For 
REX2 files HALion first extracts a WAV file and saves it in the same folder as the REX 
file.
Importing Sliced Audio Events from Cubase
You can directly import sliced audio events from Cubase by drag and drop. When 
dropping a sliced audio event in the Program Tree, HALion recognizes that the event 
contains positional information for the different slices. In the Import Samples dialog, 
the button “Create Sliced Loop” becomes available. If you click this button, HALion 
creates a sample zone for each slice and adds a Slice Player containing the required 
MIDI information. Any further mapping options are ignored.
ÖYou can also drag selected audio events (from multiple tracks) from a Cubase project 
into the Program Tree to create a sliced loop.
Root Key Number 
from Sample NameThe root key is extracted from the sample file name. This function 
searches for the root key as a MIDI note number, for example 
“Sample_Name_61”.
Keep Zone Root 
Key Instead of using the root key of the new sample, the root key of the 
zone is used.
This option is only available when replacing a single sample.
Option Description 
						

							78
Importing and Exporting SamplesImporting Sliced Loops
Playing back Sliced Loops
After the import, you can play back the loop in its original form or in a transposed 
version. By default, the original loop is played using C2 (#48), but you can specify 
another key using the Key Follow and Center Key parameters. Pressing a key below 
C3 plays transposed versions of the original loop. The keyboard range above C3 
provides the slice sample zones, which are triggered by the slice player, but can also 
be triggered manually while the loop is playing.
Make sure that the very last event ends with the loop end and not before. Otherwise 
the generated loop will be too short and will not run in a perfect cycle.
If the REX file or Cubase audio event contains more than 128 slices, HALion 
automatically creates additional layers including MegaTrig modules preconfigured to 
use key switches. That way, you can create up to 1024 zones distributed over up to 
32 layers.
The Slice Player Controls
Most of the Slice Player controls are the same as for the FlexPhraser MIDI module. 
These are described in detail in the section 
“The FlexPhraser” on page 254. The 
controls that differ for the Slice Player are described in the following sections.
Slice Player Presets
At the top right of the Program Tree, you can load and save presets for the Slice 
Player. These presets are saved in a global folder and can be accessed from any 
project you are working in.
Restart Mode
Depending on the selected Restart mode and your playing, you can restart playback 
from the beginning of the loop.
You can select one of the following options:
Start
This parameter allows you to shift the start of the loop in steps of 1/4 notes. The 
length of the loop is shortened accordingly.
Length
This parameter allows you to shorten the length of the loop in steps of 1/4 notes.
ÖThe control range of the parameters Start and Length varies with the original length of 
the loop.
Quantize
This parameter allows you to set up a quantization grid, in fractions of beats. You can 
also specify dotted and triplet values. This way, you can force the timing of the slices 
to play back only at the selected note value.
OptionDescription
OffThe loop runs continuously and does not restart upon note changes.
First NoteThe loop restarts when a note is triggered and no other notes are 
already held.
Each NoteThe loop restarts each time a note is triggered.
Sync to HostSelect this to align the loop with the beats and measures of your 
host application. The loop aligns to the beats and measures each 
time you start the transport. 
						

							79
Importing and Exporting SamplesImporting Sliced Loops
Amount
This parameter defines how much of the quantization grid is applied. A value of 100 % 
means the slices play back only at the Quantize note value you specified. Smaller 
values move the notes only partially towards the next Quantize note value. With a 
value of 0
 % no quantization is applied at all.
Key Follow
Here you can adjust the pitch modulation by note number. Set this parameter to 
positive values to raise the pitch with notes above the center key. Use negative values 
to lower the pitch with notes above the center key. At +100
 %, the pitch follows the 
played note exactly.
ÖThe Key Follow parameter is limited to the keys that trigger the entire loop. It does not 
affect the keys that play the single slices.
Center Key
This parameter determines the MIDI note that is used as the central position for the 
Key Follow function.
Random
You can shuffle the playing order of the slices randomly, by activating the Random 
button. To play the slices with their original order, deactivate the Random button.
The overall timing does not vary through this. Only the playing order of the slices is 
affected.
•Use the Depth parameter to adjust how much the playing order of the slices is 
shuffled. Lower this value to keep the playing order of slices on the main beats. 
Raise this value to vary the playing order of slices on the offbeats as well. 
•Click the Trigger button to trigger a new shuffle. Note that this changes the pattern 
number. 
•Use the Pattern option to recall a certain random pattern, by entering its pattern 
number in the value field.
Exporting the Loop Sequence
You can export the loop sequence as a MIDI part for your host sequencer.
Proceed as follows:
1.Click the MIDI connector icon (to the right of the Random options) and drag it into 
the Project window of your host sequencer application.
This creates a MIDI part at the drop position, on an existing or a new MIDI track.
2.Assign the MIDI track to the corresponding slot in HALion.
Using Variations
By activating Random and by adjusting the Tempo, Tempo Scale, Swing, Gate Scale, 
Quantize, Amount, Start, and Length parameters, you can save your settings as up to 
eight variations. For further information, see 
“Working with FlexPhraser Variations” on 
page 258.
The Loop, Sync, Hold, Trigger Mode, Restart Mode, Key Follow, and Center Key 
parameters are not part of the variations. 
						

							80
Using the Browser
Introduction
In the Browser, you can search and load samples and zones, either from the file 
system or from loaded programs. This also includes program formats from other 
software and hardware samplers. In addition, you can load programs, layers, and 
sublayers.
The Path Section
This section offers the following controls:
•The “Previous/Next Location” buttons step through the recent locations.
•The “Browse Containing Folder” button navigates to the folder one level up in the 
location tree.
•The path field shows the current location. You can specify a new location by 
entering or copying a new path.
Path section
Location tree
Preview and 
File Info section
Results 
list
Previous/Next 
Browse LocationBrowse Containing FolderLocation History pop-up menu