SoundFont

The newest version of the SoundFont file format is 2.04 (or 2.4). It is based on the RIFF format.[2]

The original SoundFont file format was developed in the early 1990s by E-mu Systems and Creative Labs. A specification for this version was never released to the public. The first and only major device to utilize this version was Creative's Sound Blaster AWE32 in 1994. Files in this format conventionally have the file extension of .SBK.

SoundFont 2.0 was developed in 1996. This file format generalized the data representation using perceptually additive real world units, redefined some of the instrument layering features within the format, added true stereo sample support and removed some obscure features of the first version whose behavior was difficult to specify. This version was fully disclosed as a public specification, with the goal of making the SoundFont format an industry standard. All SoundFont 1.0 compatible devices were updated to support the SoundFont 2.0 format shortly after it was released to the public, and consequently the 1.0 version became obsolete. Files in this and all other 2.x formats (see below) conventionally have the file extension of .SF2.

Version 2.01[3] (or 2.1) of the SoundFont file format was introduced in 1998,[4] with an E-mu sound card product called the Audio Production Studio. This version added features allowing sound designers to configure the way MIDI controllers influence synthesizer parameters. It is bidirectionally compatible with 2.0, which means that synthesizers capable of rendering 2.01 format will also by definition render 2.0 format, and synthesizers that are only capable of rendering 2.0 format will also read and render the new format, but just not apply the new features.

SoundFont 2.04 was introduced in 2005 with the Sound Blaster X-Fi. The 2.04 format added support for 24-bit samples. The 2.04 format is bidirectionally compatible with the 2.01 format, so synthesizers that are only capable of rendering 2.0 or 2.01 format would automatically render instruments using 24-bit samples at 16-bit precision.

MIDI files do not contain any sounds, only instructions to play them. To play such files, sample-based MIDI synthesizers use recordings of instruments and sounds stored in a file or ROM chip. SoundFont-compatible synthesizers allow users to use SoundFont banks with custom samples to play their music.

A SoundFont bank contains base samples in PCM format (the audio data format most commonly used in WAV containers) mapped to sections on a musical keyboard. A SoundFont bank also contains other music synthesis parameters such as loops, vibrato effect, and velocity-sensitive volume changing.

SoundFont banks can conform to standard sound sets such as General MIDI, or use other wholly custom sound-set definitions like Roland GS and Yamaha XG.

Several .sf2 editors are available:

• Vienna from Creative Labs, requiring a particular sound card (such as Sound Blaster)
• Viena[5] (with a single "n"), created in 2002
• Swami[6] is a collection of free software for editing and managing musical instruments for MIDI music composition, used mainly under Linux
• Polyphone,[7] free editor for Windows, Mac OS X and Linux created in 2013

• DLS format – file format usually associated with MIDI dataPages displaying wikidata descriptions as a fallback
• FluidSynth – Software synthesizer
• General MIDI – Standard for MIDI-based music synthesizers
• Gravis Ultrasound – Sound card for IBM PC compatiblesPages displaying short descriptions of redirect targets
• List of music software
• SFZ (file format) – Plain text file format for storing instrument data for software synthesizers
• Software synthesizer – Computer program that generates audio
• TiMidity++ – Software synthesizer
• WildMIDI – Software synthesizer

• SoundFont 2.04 specification