RIFF

RIFF
Name	RIFF
Extension	.wav, .avi, .rf64
Mime	audio/vnd.riff, video/vnd.riff
Owner	Microsoft, IBM
Released	1991
Genre	container format
Container for	WAV, AVI, MIDI)

RIFF

RIFF is a binary container file format developed for storing tagged chunks of multimedia data. It provides a simple, extensible mechanism for encapsulating audio, video, and ancillary metadata used in widely distributed digital media on platforms associated with Microsoft, IBM, Intel, Apple Inc., and other technology firms. The format underpins many legacy and contemporary media artifacts including audio recordings, video streams, and professional broadcasting files.

Definition and Overview

RIFF is defined as a tagged chunked file structure that sequences labeled data blocks for interpretation by parsers associated with particular codecs and applications. The specification was formalized to enable interoperability among implementations from Microsoft, IBM, Creative Technology, Sonic Foundry, and chipset vendors like Intel and AMD. Common container types nested within RIFF include formats standardized by organizations such as IEC, ISO, and proprietary schemes employed by companies like Avid Technology, Adobe Systems, and Apple Inc.. RIFF files typically begin with a four-character identifier followed by size fields and chunk identifiers recognized by multimedia frameworks like DirectShow, QuickTime, GStreamer, FFmpeg, and VLC media player.

History and Origin

RIFF originated as an extension of earlier interleaving concepts and chunked-file approaches used by systems developed at companies such as IBM and standards groups including Microsoft Research teams. The design was influenced by earlier formats and proposals coming out of initiatives at Bell Labs, Xerox PARC, and platform efforts around MS-DOS, Windows 3.1, and early Windows 95 multimedia subsystems. The formal adoption and promotion of RIFF occurred alongside the rise of Windows Media Player, the WAVE audio standard, and the widespread use of Multimedia PC (MPC) specifications. Industry pressure from broadcasters and studios using products from vendors like Panasonic, Sony, JVC, and post-production houses such as Avid Technology reinforced RIFF’s role as a de facto standard for chunked media.

File Format and Structure

The RIFF layout is based on a four-byte signature (e.g., "RIFF") followed by a 32-bit little-endian size and a four-byte form type (e.g., "WAVE" or "AVI "). Within the form, data are organized into discrete chunks identified by four-character codes (FourCC) assigned by entities including Microsoft, IBM, and media consortiums. Typical chunk types referenced in implementations from Nero AG, Sonic Foundry, and Fraunhofer IIS include "fmt ", "data", "LIST", and "cue ". Parsing libraries like those used in FFmpeg, GStreamer, libavcodec, and libsndfile rely on explicit offsets and size fields to locate codec payloads such as PCM, MP3, AC-3, and frame sequences for codecs developed by DivX, Xvid, H.264/MPEG-4 AVC, and MPEG-2. Container-aware tools from Adobe Systems and Apple Inc. handle nested LIST chunks to store metadata specified by standards bodies like ID3-adjacent schemes and industry registries.

Common Uses and Applications

RIFF-based files serve in audio production workflows at studios using equipment from Yamaha, Roland, Focusrite, and SSL; in video editing projects employing workstations from Avid Technology, Adobe Systems, and Grass Valley; and in broadcast distribution where systems from CBS, BBC, NBCUniversal, and Sky Group manage asset interchange. Consumer applications include playback in Windows Media Player, encoding with LAME, and authoring in tools such as Adobe Premiere Pro, Sony Vegas, and Audacity. In game development, engines like Unreal Engine and Unity (game engine) often import RIFF-encapsulated audio for use with middleware from FMOD and Wwise. Archivists at institutions like the Library of Congress and broadcasters use RIFF derivatives for long-term preservation workflows coordinated with standards from SMPTE and EBU.

Related Formats and Compatibility

Related chunked or container formats include AIFF, AVI, WAVE, BWF, RF64, and MPEG-4 Part 14 (MP4), each associated with different standards bodies and vendors such as Apple Inc., Microsoft, and Fraunhofer. Backwards-compatible extensions and large-file variants like RF64 were proposed and implemented by consortia involving European Broadcasting Union and vendors including Dolby Laboratories and Sony Professional Solutions. Interoperability layers exist in multimedia frameworks maintained by projects like FFmpeg, GStreamer, libav, and VLC media player, which map FourCC identifiers to codec libraries developed by xiph.org, Fraunhofer IIS, and codec vendors such as DivX and x264.

Technical Specifications and Implementation

Implementations parse RIFF by reading the initial chunk header, verifying form types such as "WAVE" or "AVI ", and iterating chunk headers to extract payloads. Tools and libraries from Microsoft Visual Studio, GNU Compiler Collection, MinGW, and open-source projects like FFmpeg and libsndfile provide reference code for handling little-endian 32-bit size fields, alignment padding, and nested LIST constructs. Developers integrate RIFF support in applications targeting platforms including Windows NT, Linux, macOS, and embedded systems from ARM Holdings and Intel by mapping FourCC values to codec handlers like PCM, ADPCM, AAC, and legacy codecs supported by Microsoft DirectX. For high-precision or broadcast-grade workflows, specifications from SMPTE, EBU, and ITU inform timestamping, sample rate handling, and metadata encapsulation used by broadcasters and post-production vendors.

Category:Computer file formats