Introduction to ESP FOURCC
FOURCC (Four Character Code) is a widely used identifier in the multimedia domain, typically employed for the rapid identification of audio and video codecs, container formats, pixel formats, and more. Espressif Systems defines a comprehensive FOURCC encoding standard, called ESP FOURCC, which is specified in the open-source project ESP-GMF, specifically in the esp_fourcc.h header file. This standard covers audio, video, image, container formats, and various pixel formats. This article provides an in-depth overview of the background, significance, definition principles, implementation methods, and advantages of ESP FOURCC.
Background and Significance of FOURCC
The history of FOURCC can be traced back to the 1980s with the OSType mechanism in the Macintosh system, where four-character identifiers were used to represent file types. In the 1990s, QuickTime adopted this approach in the audio-video domain, which later became a core identification method in MP4 containers, FFmpeg, and other mainstream frameworks.
In embedded systems, where resources are constrained and memory and computational efficiency are crucial, using compact identifiers is essential. Defining unique enumeration values or constants for each module to represent data formats often leads to the following issues:
Lack of standardization: If different modules define their own format identifiers independently, the same data format may have different enumeration values across different modules, increasing interface adaptation complexity.
High conversion overhead: When transferring data between modules, inconsistencies in format identifiers require additional conversion operations, leading to unnecessary runtime overhead.
Difficult debugging: When different modules use different identification methods, it becomes challenging to intuitively confirm the actual data format during debugging, increasing the complexity of issue resolution.
In contrast, the FOURCC mechanism resolves these issues by using a unified 32-bit identifier. This not only ensures consistency in data formats across modules but also allows for compile-time constant generation, facilitating quick comparisons and lookups, thereby significantly enhancing overall system performance and maintainability.
Fundamental Principles and Implementation of FOURCC
1. Core Mechanism of FOURCC
FOURCC is a compact encoding scheme based on ASCII characters. The core principle is to generate a 32-bit unsigned integer (uint32_t) from four consecutive characters. For example, the string “H264” corresponds to the hexadecimal value 0x48323634, where each character’s ASCII code is combined in sequence:
‘H’ → 0x48
‘2’ → 0x32
‘6’ → 0x36
‘4’ → 0x34
2. Implementation of ESP FOURCC
In ESP-GMF, FOURCC definitions are primarily found in the esp_fourcc.h header file, which includes the following components:
Macro Definition
ESP-GMF defines the macro
ESP_FOURCC_TO_INT(a, b, c, d), allowing developers to generate FOURCC values at compile time. This macro converts four input characters into a 32-bit integer. For example:#define ESP_FOURCC_H264 ESP_FOURCC_TO_INT('H','2','6','4') // 0x48323634
Helper Functions
The esp_fourcc.h header provides a macro
ESP_FOURCC_TO_STR(fourcc), which callsgmf_fourcc_to_str. This function converts auint32_tFOURCC value into a string representation. For example:printf("Format: %s\n", ESP_FOURCC_TO_STR(0x48323634)); // "H264"
FOURCC Definitions
ESP FOURCC v1.0.0 defines commonly used types in multimedia applications for embedded devices, including audio and video codecs, container formats, and pixel formats. For specific details, refer to esp_fourcc.h .
Multimedia FOURCC Formats
The esp_fourcc.h file defines multimedia formats covering video and audio codecs, containers, and image codecs. Below is a list of commonly used formats:
Category |
FOURCC Example |
Character Representation |
Encoding Standard/Technical Features |
|---|---|---|---|
Video Codecs |
|
|
H.264/AVC (with start codes) |
|
|
H.264 (without start codes, MP4 compatible) |
|
|
|
HEVC/H.265 (high compression efficiency) |
|
Container Formats |
|
|
MPEG-4 Part 14 (multi-track support) |
|
|
Ogg Container |
|
|
|
Flash Video (optimized for streaming) |
|
Image Codecs |
|
|
Lossless compression (supports transparency) |
|
|
Lossy compression (high compression ratio) |
|
|
|
Hybrid lossy/lossless compression (size optimized) |
|
Audio Codecs |
|
|
MPEG Layer III (widely compatible) |
|
|
Advanced Audio Coding (efficient compression) |
|
|
|
Low-latency dynamic bitrate (optimized for real-time communication) |
FOURCC Pixel Formats
esp_fourcc.h defines various FOURCC pixel formats, including RGB, YUV, grayscale, and special formats. Each format’s data storage method is also specified. The following table lists some commonly used formats:
Category |
FOURCC Example |
Character Representation |
Technical Features |
|---|---|---|---|
RGB Formats |
|
|
RGB-5-6-5 little-endian, 16-bit compression (low bandwidth) |
|
|
RGB-8-8-8 packed, 24-bit true color |
|
YUV Formats |
|
|
YUV 4:2:0 semi-planar (Y plane + interleaved UV) |
|
|
YUV 4:2:2 packed (Y-U-Y-V interleaved) |
|
|
|
YUV 4:2:0 planar format (Y + U + V planes) |
|
Gray |
|
|
8-bit single-channel grayscale |
Special Formats |
|
|
16-bit raw data (little-endian storage) |
Practical Application Cases
In the ESP-GMF framework, various modules (such as video decoders, audio processors, and image filters) utilize FOURCC codes for capability declaration and interface matching. For example, a video decoder may declare its supported FOURCC formats for input and output. The upper-layer scheduler uses FOURCC codes to ensure correct data flow between modules. This mechanism enhances system robustness and facilitates the expansion of new functionalities.