User Manual

Library Creator
Consistency Check
420
•
Replace All: Replaces the text for all search results.
•
Case Sensitive: Activate this option to make the search case sensitive.
•
Search in all Attributes: Activate this option if you want to search for text in
all attribute columns. Otherwise, only the name column is searched.
Show Issues
Click here to open a list of issues that have been detected in the added presets
during a consistency check.
Click the button to redo the consistency check. This can be useful if the check has
detected missing MediaBay tags, for example.
Refresh
Refreshes the list. Use this if you have added tags to the presets in the MediaBay.
Consistency Check
To avoid incomplete or nonfunctional libraries, the Library Creator performs several
automatic checks when building libraries. As a first step, all presets are checked when they
are added to a VST Sound container. If any issues are found, a red warning sign is shown in
the Issue column of the corresponding preset and a global warning sign is shown in the list
of unassigned samples/VST Sound containers. Existing issues will not prevent the Library
Creator from building the VST Sound container, however. They should be understood as an
information about what Steinberg would consider an issue to be fixed before releasing the
library.
Checks are performed for the following:
•
HALion Sonic and HALion Sonic SE presets for which no macro page is assigned
•
HALion Sonic and HALion Sonic SE presets for which no quick controls are assigned
•
the used audio formats (file type, sample rate, bit depth, channels)
•
Sample markers that exist beyond the sample file end
•
Sample markers that exist beyond the sample end in a zone
•
Sample end markers that are placed before the start marker
•
Empty sample, grain, and wavetable zones
•
Samples that are not referenced by any presets
•
Missing information for Author, Category, and Sub-Category
•
Character tags that are not set
•
Only one of the parameters Signature and Tempo is set
•
Presets with the same name (case sensitive)
•
An incorrect size for the macro page if it is to be used in HALion Sonic and HALion
Sonic SE
When starting the library build process, the Library Creator may encounter additional issues
which can stop the build process. If that happens, a report window opens that informs you
why the process could not be executed. The reasons could be that you did not fill out one of
the mandatory fields in the library properties, or that required samples, presets, or macro
page resources could not be found, because they were removed from your file system after
the library file was created, for example.