<html xmlns:o="urn:schemas-microsoft-com:office:office" xmlns:w="urn:schemas-microsoft-com:office:word" xmlns:m="http://schemas.microsoft.com/office/2004/12/omml" xmlns="http://www.w3.org/TR/REC-html40">
<head>
<meta http-equiv="Content-Type" content="text/html; charset=windows-1257">
<meta name="Generator" content="Microsoft Word 15 (filtered medium)">
<style><!--
/* Font Definitions */
@font-face
{font-family:"Cambria Math";
panose-1:2 4 5 3 5 4 6 3 2 4;}
@font-face
{font-family:Calibri;
panose-1:2 15 5 2 2 2 4 3 2 4;}
@font-face
{font-family:"Segoe UI";
panose-1:2 11 5 2 4 2 4 2 2 3;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
{margin:0cm;
margin-bottom:.0001pt;
font-size:11.0pt;
font-family:"Calibri",sans-serif;}
a:link, span.MsoHyperlink
{mso-style-priority:99;
color:blue;
text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
{mso-style-priority:99;
color:#954F72;
text-decoration:underline;}
.MsoChpDefault
{mso-style-type:export-only;
font-family:"Calibri",sans-serif;}
@page WordSection1
{size:612.0pt 792.0pt;
margin:72.0pt 72.0pt 72.0pt 72.0pt;}
div.WordSection1
{page:WordSection1;}
--></style>
</head>
<body lang="LT" link="blue" vlink="#954F72">
<div class="WordSection1">
<p class="MsoNormal"><span style="font-family:"Segoe UI",sans-serif">Hm,<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-family:"Segoe UI",sans-serif"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="font-size:10.0pt;font-family:"Segoe UI",sans-serif">"Atmos presumably has it's own lossy compression</span><span lang="EN-US" style="font-size:10.0pt;font-family:"Segoe UI",sans-serif"> maybe. But what about Atmos in TrueHD
or Atmos in LPCM?</span><span lang="EN-US" style="font-family:"Segoe UI",sans-serif"><o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-family:"Segoe UI",sans-serif"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="font-family:"Segoe UI",sans-serif">Spatial audio:<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-family:"Segoe UI",sans-serif"><a href="https://developer.microsoft.com/en-us/windows/mixed-reality/spatial_sound">https://developer.microsoft.com/en-us/windows/mixed-reality/spatial_sound</a>
<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-family:"Segoe UI",sans-serif"><a href="https://developer.microsoft.com/en-us/windows/mixed-reality/spatial_sound_in_directx">https://developer.microsoft.com/en-us/windows/mixed-reality/spatial_sound_in_directx</a>
<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-family:"Segoe UI",sans-serif"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="font-family:"Segoe UI",sans-serif">There is a set of HRTF functions -
</span><span lang="EN" style="font-family:"Segoe UI",sans-serif">head-relative transfer functions</span><span style="font-family:"Segoe UI",sans-serif"><o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-family:"Segoe UI",sans-serif">There are basically 3 major formats DTS:X, Atmos and Auro 3D.<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-family:"Segoe UI",sans-serif"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="font-family:"Segoe UI",sans-serif">One of the major obstacles for VR/AR headsets is the sound and proper positioning of sound. IMHO, this is one of the reasons why Microsoft is bringing Dolby Atmos to Windows platform. And
this is one of the reasons Microsoft has implemented Windows Sonic at the same time. There are no popular mechanisms to position objects based audio in some kind unified way. Windows Sonic is now one such technology.<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-family:"Segoe UI",sans-serif"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="font-family:"Segoe UI",sans-serif">While Windows Sonic rendering exists there is now format for this kind of files, except Atmos and DTS:X. Sony does their own implementation.<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-family:"Segoe UI",sans-serif"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="font-family:"Segoe UI",sans-serif">So I thought maybe FLAC or Xiph.org has some plans for that...<o:p></o:p></span></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal">Sent from <a href="https://go.microsoft.com/fwlink/?LinkId=550986">
Mail</a> for Windows 10</p>
<p class="MsoNormal"><o:p> </o:p></p>
<div style="mso-element:para-border-div;border:none;border-top:solid #E1E1E1 1.0pt;padding:3.0pt 0cm 0cm 0cm">
<p class="MsoNormal" style="border:none;padding:0cm"><b>From: </b><a href="mailto:brianw@audiobanshee.com">Brian Willoughby</a><br>
<b>Sent: </b>2017 m. rugpjūčio 12 d., šeštadienis 12:45<br>
<b>To: </b><a href="mailto:flac@xiph.org">flac@xiph.org</a><br>
<b>Subject: </b>Re: [Flac] Spatial/Atmos on FLAC?</p>
</div>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal"><span style="font-size:10.0pt">On Aug 10, 2017, at 5:46 AM, Renatas Lau?adis <renatas@outlook.com> wrote:<br>
> are there any plans for FLAC to implement spatial audio? Or maybe Atmos on FLAC?<br>
<br>
FLAC is a multichannel audio format supporting up to 8 channels. There are advantages to compressing 2 channel (stereo) audio in terms of file size savings, but there is no compression advantage to other combinations.<br>
<br>
Atmos supports up to 128 channels, 10-channel minimum, so it cannot be directly stored in FLAC due to the 8-channel limit. In addition, Atmos presumably has it's own lossy compression, so it would be pointless to use a lossless conversion for a lossy surround
file. Atmos is also proprietary, or at least I assume we do not have the option of supporting it anyway.<br>
<br>
I do not see any documentation of Spatial - is that a standard format? Is it an open format? Is it even intended to be distributed as a separate digital file?<br>
<br>
In any event, archival and delivery for mastering of surround audio is generally done in individual mono files. Some surround projects are delivered on 8-channel digital audio tape with only 6 channels used in the case of 5.1 surround audio. Beyond 5.1, there
must be various methods of delivering audio. There might be some advantage with FLAC to combine pairs in surround, such as front, side, rear, but otherwise I would say that it's a bad idea to try and place more than 2 channels in a single file. The audio frames
become too large to compress well.<br>
<br>
There's a difference between formats used for recording, mixing, and mastering versus formats used for delivery of the final product to consumers. Delivery formats like Dolby and DTS generally require licensed software compression tools, making it difficult
to convert to FLAC in any case.<br>
<br>
Perhaps you could explain more about what you hope to see?<br>
<br>
Brian Willoughby<br>
<br>
_______________________________________________<br>
Flac mailing list<br>
Flac@xiph.org<br>
<a href="http://lists.xiph.org/mailman/listinfo/flac">http://lists.xiph.org/mailman/listinfo/flac</a><o:p></o:p></span></p>
<p class="MsoNormal"><o:p> </o:p></p>
</div>
</body>
</html>