Contact emails [email protected], [email protected]
Explainer https://github.com/SyedAbuTalib/iamf-explainer/blob/main/explainer.md Specification https://aomediacodec.github.io/iamf/latest-approved.html Design docs https://docs.google.com/document/d/1G4Km3hxEnXonvgiZo7got_DWIatBrpYbyzk3yIpaV6A/edit?usp=sharing&resourcekey=0-rS2fUcQM7tcKNDoQmk7Tmg Summary Adds support for decoding and playing back the Immersive Audio Model and Formats (IAMF) container within HTML media elements via Media Source Extensions (MSE). IAMF is an open, royalty-free spatial audio format that supports channel-based, scene-based, and object-based audio presentations. Supporting this standard allows web developers to deliver consistent, immersive 3D audio experiences across different devices without relying on proprietary formats or managing complex discrete audio channel routing in JavaScript. Blink component Blink>Media>Audio <https://issues.chromium.org/issues?q=customfield1222907:%22Blink%3EMedia%3EAudio%22> Web Feature ID Missing feature Motivation Currently, delivering high-quality, immersive 3D audio on the web relies heavily on proprietary formats (like Dolby Atmos) or complex custom JavaScript audio rendering. IAMF provides a standardized, royalty-free container that allows web developers to deliver rich, consistent spatial audio experiences across devices for use cases like gaming, AR/VR, and streaming media. Adding IAMF support to Chromium's media pipeline aligns with the open web ecosystem and ensures a baseline for spatial audio interoperability. Risks Interoperability and Compatibility Low interoperability risk. IAMF is an open, royalty-free spatial audio format maintained by AOMedia. Initial support in Chromium focuses on IAMF streams backed by the Opus codec in MP4 containers delivered via Media Source Extensions (MSE). Support can be detected by existing web APIs such as canPlayType or media capabilities. Gecko: No signal, https://github.com/mozilla/standards-positions/issues/1437 WebKit: No signal, https://github.com/WebKit/standards-positions/issues/700 Web developers: No signals, N/A Other signals: Strong interest from external partners. Debuggability Exposed via chrome://media-internals and DevTools Media panel. Will this feature be supported on all six Blink platforms (Windows, Mac, Linux, Chrome OS, Android, and Android WebView)? Yes Supported on all platforms where Chromium media audio decoding is supported. Is this feature fully tested by web-platform-tests <https://chromium.googlesource.com/chromium/src/+/master/docs/testing/web_platform_tests.md> ? https://github.com/web-platform-tests/wpt/blob/master/media-source/mediasource-iamf-playback.html https://wpt.fyi/results/media-source/mediasource-iamf-playback.html?label=experimental&label=master&aligned Flag name on chrome://flags None Finch feature name IamfAudioDecoding Requires code in //chrome? False Tracking bug https://crbug.com/535279329 Estimated milestones Shipping on desktop 153 Shipping on Android 153 Shipping on WebView 153 Requesting approval to ship? Yes. -- You received this message because you are subscribed to the Google Groups "blink-dev" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To view this discussion visit https://groups.google.com/a/chromium.org/d/msgid/blink-dev/CAOVddLZFjhByA0TCwpKxjkTAo%2BHgeF8Wrt0KcjWjbh%2BnTpJw1Q%40mail.gmail.com.
