![]() Then, you must export the instrument again as HALion Sonic Layer preset, load it in HALion Sonic, test it, etc. If you find issues, you need to go back to the original HALion Program preset from step 1 and correct whatever you found. In this step, you should test your instrument thoroughly. Load the exported Layer in HALion Sonic.This step makes it possible to load the instrument you created in HALion as a Layer in HALion Sonic. Export the program as HALion Sonic Layer preset.While working in HALion, the instrument is saved as Program preset. This creates a canvas with the default size for the HALion Sonic macro page. When creating the macro page, you must select Create HALion Sonic Macro Page. In this step, you add sublayers and samples, adjust the mapping, write scripts, build the macro page, etc. To build a library that works in HALion Sonic, proceed as follows: Library Creation Process Library Creation Workflow The macro page can be of any reasonable size. The versions 3.2 and higher do not have this restiction. ❕ In previous versions of HALion Sonic (< 3.2) the maximum size of the macro page was limited to 595 x 390 pixels. See HALion Sonic Program Structure for details. The number of instrument layers is limited to four and certain MIDI modules are always needed. HALion Sonic libraries have restrictions regarding the program structure. HALion Sonic is freely available for download on the Steinberg website. Most often, you will probably want to build your library so that it works with HALion Sonic, which means that it can be used by everybody. However, this limits the number of potential users. You could build a library that only HALion users can use, which gives you the freedom to build a program with a different structure, for example. HALion libraries are only compatible with HALion. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |