E.2 CONTROL OPCODES
APPENDIX E: SFZ SUPPORT > E.2 CONTROL OPCODES · PDF 第 123 · OS 1.3.3
# E.2 CONTROL OPCODES APPENDIX E: SFZ SUPPORT APPENDIX E: SFZ SUPPORT The primary and best-supported method of specifying multi-sampled instruments for the Multi player machine and the sample sets for the Subtracks machine on Tonverk is the native mapping format, which is found in the .eldrum and .elmulti files included in the factory library. However, a subset of the SFZ format can be loaded by Tonverk. This document describes the capabilities and limitations of that subset. E.1 HEADERS Tonverk supports the following headers. Note that all headers besides <region> are optional. • <control> • <global> • <master> • <group> • <region> All of the above, aside from <control>, support the same opcodes but have different scope and override semantics (see https://sfzformat.com/headers for more information on headers). E.1.1 OTHER HEADERS • <curve> headers are allowed to be present, but are ignored. • <effect>, <midi>, and <sample> headers are not supported, and files containing them will fail to load. E.2 CONTROL OPCODES Under the <control> header, the following opcodes are supported: • default_path sets the path where files are loaded relative to. Please note that the behavior of some players, which allows file-name prefixes in addition to distinct pathelements, is not supported. • note_offset transposes all regions by a number of semitones. • octave_offset transposes all regions by a number of octaves. For more information about opcodes, please see https://sfzformat.com/opcodes/ E.2.1 IGNORED CONTROL OPCODES For convenience, the following opcodes are ignored and will not cause an error if they are present: • hint_load_method • label_cc_* • set_cc_* Any other opcodes provided under the <control> header will result in an error. E.3 REGION OPCODES Headers <global>, <master>, <group>, and <region> all support the same set of opcodes. Pitch values can be specified as numeric MIDI key values or in IPN, where MIDI note 0 is called “C-1” (and consequently, middle C is C4). E.3.1 REQUIRED OPCODES A region (or a group, master, or global header preceding it) must minimally specify a sample (sample=...) and a pitch (via either key=... or pitch_keycenter=...). Regions that fail to meet this criterion will be ignored. The sample opcode is a file path, relative to the location of the SFZ file. Use UNIX-style paths (with forward slashes) for best results. Special rules for file names. • Space (blank) characters are allowed. • Equals (=) and balanced angle brackets (e.g. My<Sample>.wav) are not allowed. • Comment-opening tokens (// or /*) are forbidden. • Any trailing blank characters are ignored.
章节与相邻小节共享 PDF 页面；标题之前/之后的文本属于相邻小节。