Audio Codec

Use the bitrate calculator to size the workload, or build your own licence with Callaba Self-Hosted if the workflow needs more flexibility and infrastructure control. Managed launch is also available through AWS Marketplace.

Why codec policy matters

Many incidents attributed to video quality are actually audio-profile mismatches or unstable transcoding paths. A codec policy prevents drift between operators, encoders, and playback clients.

Decision model

1. Define target devices and playback constraints.
2. Choose primary codec for compatibility and secondary codec for special cases.
3. Set fixed sample rate, channel layout, and bitrate tiers.
4. Validate end-to-end behavior under packet loss and jitter.
5. Monitor transcoding errors and loudness consistency.

Relevant products: Player and embed, Video platform API, 24/7 streaming channels.

Practical defaults

• AAC-LC for broad browser and mobile compatibility.
• Stable sample rate across ingest and output profiles.
• Conservative bitrate for speech-first channels, higher tiers for music-heavy events.
• Single source of truth for profile presets in CI/config repository.

Low-latency considerations

Codec selection should be aligned with packetization and buffer strategy. Better results come from end-to-end tuning than from bitrate increases alone.

Reference materials: bitrate guide, codec basics, low latency SRT transport.

Operational checks

• Track audio-video sync drift on long sessions.
• Alert on sudden channel-layout changes and decode failures.
• Keep fallback transcode profile ready for unstable sources.

Common mistakes and fixes

• Mistake: different sample rates per channel. Fix: enforce one standard profile.
• Mistake: codec changes during events. Fix: lock configuration per event window.
• Mistake: no monitoring of decode errors. Fix: add codec-level observability.

Next step

Continue with audio track strategy, transcoding architecture, and Video platform API.