Editing Ambisonics (section)

=== Data exchange ===

Transmitting Ambisonic B-format between devices and to end-users requires a standardized exchange format. While ''traditional first-order B-format'' is well-defined and universally understood, there are conflicting conventions for higher-order Ambisonics, differing both in channel order and weighting, which might need to be supported for some time. Traditionally, the ''Furse-Malham (FuMa) higher order format'' in the <code>.amb</code> container based on Microsoft's WAVE-EX file format.<ref name=".AMB">Richard Dobson [http://people.bath.ac.uk/masrwd/bformat.html ''The AMB Ambisonic File Format''] {{Webarchive|url=https://web.archive.org/web/20140422234520/http://people.bath.ac.uk/masrwd/bformat.html |date=22 April 2014 }}</ref> It scales up to third order and has a file size limitation of 4GB.

The current B-format standard format is AmbiX<ref>Christian Nachbar, Franz Zotter, Etienne Deleflie, and Alois Sontacchi: [https://www.researchgate.net/publication/266602800_AMBIX_-A_SUGGESTED_AMBISONICS_FORMAT ''AmbiX - A Suggested Ambisonics Format''] Ambisonics Symposium 2011, Lexington (KY) 2011</ref> proposal, which adopts the <code>.caf</code> file format and does away with the 4GB limit. It scales to arbitrarily high orders and is based on SN3D encoding. SN3D encoding has been adopted by Google as the basis for its YouTube 360 format.<ref>YouTube Help, [https://support.google.com/youtube/answer/6395969?hl=en-GB Use spatial audio in 360-degree and VR videos]</ref>
{{Details|Ambisonic data exchange formats}}