<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=utf-8">
</head>
<body text="#000000" bgcolor="#FFFFFF">
<p>Dear Kevin: We are all aware of the conflicts involved. I
occasionally read the AGOTTV5 reports but got lazy about it, my
bad. <br>
</p>
<p>Since this is primarily intended for OTT boxes and portable has
not been mentioned, I hope there is not a big conflict. Music will
be turned down to -23 in the OTT boxes. Sooner or later we will
have to address this, but until metadata is standardized it's
putting the cart before the horse. I'm concentrating on helping us
get music streaming services in line, and then eventually we'll
have to reconcile things, but until metadata is standardized I
doubt we can solve the conflict with a document other than
recognizing that a conflict exists.</p>
<p><br>
</p>
<p>Bob</p>
<p><br>
</p>
<br>
<div class="moz-cite-prefix">On 6/3/18 5:17 PM, Kevin Gross wrote:<br>
</div>
<blockquote type="cite"
cite="mid:CALw1_Q1ts5TmyCr-pMKQCszWnvp5MAtPbAPaO+vJErYrU-Wpvw@mail.gmail.com">
<div dir="ltr">I don't know if any of you have been following or
working in the AES's AGOTTVS initiative. This group is working
on loudness for over the top (OTT) and online video distribution
(OVD). They have produced a standards document that will come
out for public comment soon as AES71. The recommendations are
reasonable - produce, transmit and use metadata where possible,
use BS.1770 with -23 or -24 LUFS target.
<div><br>
</div>
<div>There is, however, a large portable aspect to these topics
and the line between OVD and music loudness is not very crisp
(YouTube is everyone's favorite music streaming service). In
these cases the -23 LUFS is at odds with the -16 LUFS
recommendation in the AES TD1004 recommendation. -16 LUFS does
appear in the AES71 draft in what appears to be a "not to
exceed under any circumstances" specification.</div>
<div><br>
</div>
<div>Aside from the potential problems connecting these
recommendations, I see problems with a -23 LUFS target for
portable applications. We've discussed limitations of portable
devices and environments here and I know we don't all agree
but we have seen evidence that this is not loud enough for
certain hardware and situations and regulations. </div>
<div><span
style="color:rgb(34,34,34);font-family:arial,sans-serif;font-size:small;font-style:normal;font-variant-ligatures:normal;font-variant-caps:normal;font-weight:400;letter-spacing:normal;text-align:start;text-indent:0px;text-transform:none;white-space:normal;word-spacing:0px;background-color:rgb(255,255,255);text-decoration-style:initial;text-decoration-color:initial;float:none;display:inline"><br>
</span></div>
<div><span
style="color:rgb(34,34,34);font-family:arial,sans-serif;font-size:small;font-style:normal;font-variant-ligatures:normal;font-variant-caps:normal;font-weight:400;letter-spacing:normal;text-align:start;text-indent:0px;text-transform:none;white-space:normal;word-spacing:0px;background-color:rgb(255,255,255);text-decoration-style:initial;text-decoration-color:initial;float:none;display:inline">AGOTTVS<span> did
do some experiments on this and the findings were that
were that -23 didn't work for everyone in all scenarios
and that more testing was needed. I don't know how they
got from this to a -23 recommendation, but they did.</span></span></div>
<div><span
style="color:rgb(34,34,34);font-family:arial,sans-serif;font-size:small;font-style:normal;font-variant-ligatures:normal;font-variant-caps:normal;font-weight:400;letter-spacing:normal;text-align:start;text-indent:0px;text-transform:none;white-space:normal;word-spacing:0px;background-color:rgb(255,255,255);text-decoration-style:initial;text-decoration-color:initial;float:none;display:inline"><span><br>
</span></span></div>
<div><span
style="text-align:start;text-indent:0px;background-color:rgb(255,255,255);text-decoration-style:initial;text-decoration-color:initial;float:none;display:inline">As
an officer in AES standards, I have reviewed the draft and
submitted some comments to clean up some definitions and
other inconsistencies and underspecification. I'm not sure
how to broach the subject of an unrealistic target level
recommendation. I was hoping someone here could talk me
through or talk me down from this.</span></div>
<div>
<div><br clear="all">
<div>
<div class="gmail_signature"
data-smartmail="gmail_signature">
<div dir="ltr">Kevin Gross - AVA Networks</div>
</div>
</div>
</div>
</div>
</div>
<!--'"--><br>
<fieldset class="mimeAttachmentHeader"></fieldset>
<br>
<pre wrap="">_______________________________________________
MLA mailing list
<a class="moz-txt-link-abbreviated" href="mailto:MLA@grimmaudio.nl">MLA@grimmaudio.nl</a>
<a class="moz-txt-link-freetext" href="http://grimmaudio.nl/mailman/listinfo/mla_grimmaudio.nl">http://grimmaudio.nl/mailman/listinfo/mla_grimmaudio.nl</a>
</pre>
</blockquote>
<br>
<div class="moz-signature">-- <br>
<meta http-equiv="content-type" content="text/html; charset=utf-8">
<div class="moz-signature">
<div class="moz-signature">
<div class="moz-signature">
<title></title>
<div class="moz-signature">
<div class="moz-signature">
<div class="moz-signature">
<pre class="moz-signature" cols="80"><font face="Courier">
If you want good sound on your album, come to
Bob Katz 407-831-0233 </font><font face="Courier">DIGITAL DOMAIN MASTERING STUDIO
Author: <b>Mastering Audio </b></font><font face="Courier">
<a href="http://www.digido.com/">Digital Domain Website</a>
No trees were killed in the sending of this message. However a large number
of electrons were terribly inconvenienced.<font color="#ff0000">
</font></font></pre>
</div>
</div>
</div>
</div>
</div>
</div>
</div>
</body>
</html>