Audio Frame Header Library
A Rust library implementing a compact and efficient binary frame header format for audio data. The header format supports multiple audio encodings, sample rates, and channel configurations while maintaining a small footprint.
Features
- Compact 32-bit header format with optional 64-bit ID
- Support for multiple audio encodings (PCM, Opus, FLAC, AAC)
- Efficient bit-packed fields for maximum space utilization
- WASM compatibility with special ID handling
- Comprehensive validation of audio parameters
- In-place header modification capabilities
- Field extraction without full header parsing
Header Format
The header uses a 32-bit format with the following bit layout:
[31-23] Magic Word (9 bits) = 0x155
[22-20] Encoding Flag (3 bits)
[19-18] Sample Rate (2 bits)
[17-14] Channels (4 bits)
[13-2] Sample Size (12 bits)
[1] Bits Per Sample (2 bits)
[0] Endianness (1 bit)
[0] ID Present Flag (1 bit)
[Optional] 64-bit ID
Supported Parameters
- Encodings: PCM (Signed/Float), Opus, FLAC, AAC, H264
- Sample Rates: 44.1kHz, 48kHz, 88.2kHz, 96kHz
- Channels: 1-16
- Bits Per Sample: 16, 24, 32
- Endianness: Little/Big Endian
- Sample Size: Up to 4095 samples
- Optional ID: 64-bit identifier
Usage
Creating a Header
use ;
let header = new?;
Encoding/Decoding
// Encode to bytes
let mut buffer = Vec new;
header.encode?;
// Decode from bytes
let decoded = decode?;
Modifying Headers
// Patch individual fields
patch_sample_size?;
patch_encoding?;
patch_sample_rate?;
patch_channels?;
patch_bits_per_sample?;
Quick Field Extraction
// Extract specific fields without full header parsing
let sample_count = extract_sample_count?;
let encoding = extract_encoding?;
let id = extract_id?;
Validation
The library performs extensive validation:
- Magic word verification
- Valid sample rates check
- Channel count limits (1-16)
- Supported bits per sample (16, 24, 32)
- Maximum sample size (4095)
- Header size validation
- Encoding flag validation
WASM Support
The library includes special handling for 64-bit IDs in WASM environments:
- IDs are serialized as strings in WASM
- Custom serialization/deserialization implementations
- Maintains compatibility across platforms
Performance Considerations
- Bit-packed format minimizes memory usage
- Field extraction without full parsing
- In-place modification capabilities
- Efficient binary operations
License
MIT