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 indicator of the issues that you might want to fix 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.