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 path elements, 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.