<div dir="ltr"><span style="font-size:small;text-decoration-style:initial;text-decoration-color:initial;float:none;display:inline">Even for systems with metadata, the standard is not very specific on what the metadata is and how to use it to control playback. </span><div><span style="font-size:small;text-decoration-style:initial;text-decoration-color:initial;float:none;display:inline"><br></span></div><div><span style="font-size:small;text-decoration-style:initial;text-decoration-color:initial;float:none;display:inline">I think we have identified important use cases where portable devices do not get metadata. The blanket AES71 recommendation in this case is for -23 LUFS target level. We know that does not square with current practice and recommendations. The recommendation is based on preliminary and incomplete testing that surfaced problems with this level. I don't think it will work. </span><div><span style="font-size:small;text-decoration-style:initial;text-decoration-color:initial;float:none;display:inline"><br></span></div><div><span style="font-size:small;text-decoration-style:initial;text-decoration-color:initial;float:none;display:inline">I think deficiencies in this work has the potential to cause implementers to lose confidence in loudness standards. I am considering putting in an official comment against AES71 to this effect.</span><br><div class="gmail_extra"><br clear="all"><div><div class="gmail_signature" data-smartmail="gmail_signature"><div dir="ltr">Kevin Gross - AVA Networks</div></div></div>
<br><div class="gmail_quote">On Fri, Jun 29, 2018 at 5:08 PM, Grimm | Eelco <span dir="ltr"><<a href="mailto:eelco@grimmaudio.com" target="_blank">eelco@grimmaudio.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div style="word-wrap:break-word"><div>Hi Kevin,</div><div><span class=""><br><blockquote type="cite"><div><div dir="ltr"><div>When you say all OTT formats require metadata, can you give some examples and do you know details about the metadata formats and systems used? </div></div></div></blockquote><div><br></div></span><div>What I meant is that most streaming services offer their own apps and have a communication channel within their own ecosystem. For streaming to a browser you are right: in that case the metadata needs to be integrated with the audio stream and so it is dependent on the format. But I’m afraid we cannot guarantee that this will never be abused (like feeding it with wrong metadata). So my recommendation would be that the OS will only offer additional gain to approved apps, not to browsers. I agree it is not a complete solution, but a large majority of users (and content providers) will profit from it. </div><div><br></div><div>It should work like this: in the browser, -16 LUFS will be the target level. Programs that are softer will sound softer. In the app -23 LUFS can be the target level and all content (soft and loud) will be normalized. </div><div><br></div><div>Cheers,</div><div>Eelco</div><div><div class="h5"><br><blockquote type="cite"><div><div dir="ltr"><div><div>If we have good support for metadata, AES71 can work. I am concerned about its default behavior when no metadata is available. AES71 is not helping its own adoption by not at least referencing any existing metadata formats or systems.</div><div><div class="gmail_extra"><br clear="all"><div><div class="m_-6926211169150109977gmail_signature" data-smartmail="gmail_signature"><div dir="ltr">Kevin Gross - AVA Networks</div></div></div>
<br><div class="gmail_quote">On Sat, Jun 16, 2018 at 2:11 AM, Grimm | Eelco <span dir="ltr"><<a href="mailto:eelco@grimmaudio.com" target="_blank">eelco@grimmaudio.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div style="word-wrap:break-word"><div>Dear friends,</div><div><br></div><div>I’m sorry I did not check my MLA mailbox the past week and did not respond more early. </div><div><br></div><div>Kevin, can you please tell me under what circumstances there will be no metadata and/or guaranteed normalization level? All OTT formats I know cannot be used without metadata. Did they specify these circumstances in AES71 more precisely?</div><div><br></div><div>Also, what does it mean ‘-23 LUFS when there is no metadata’? If the audio is measured, metadata can be added. If the audio is not measured, it could be -6 LUFS and it is dangerous to treat it as if it is -23 LUFS.</div><div><br></div><div>But perhaps we are dealing with a completely different problem. The loudness of the program at the OTT service is known, with or without metadata: -23 LUFS. The question then is: how to do playback on a portable device? The solutions is to solve it in either the app (with 7 dB extra gain and a limiter) or in the OS. I will reach out to the OTT contacts at Google and Apple that Matthieu Parmentier gave me to pitch a simple solution I came up with: let the app signal to the OS that it has turned normalization on at a certain level (let’s say -23 LUFS), and then the OS offers 7 dB (in this case) extra headroom. Buddy Judge has already checked this idea within Apple and apparently the engineers have been thinking along simiar lines. You can’t fool the OS since the app needs to comply to AppStore rules and will be tested prior to release. I want to pitch this idea to as many developers within Apple as possible so chances are higher it will be adopted.</div><div><br></div><div>Cheers,</div><div>Eelco</div><div><br></div><br><div><blockquote type="cite"><div><div class="m_-6926211169150109977h5"><div>On 8 jun. 2018, at 16:41, Kevin Gross <<a href="mailto:kevin.gross@avanw.com" target="_blank">kevin.gross@avanw.com</a>> wrote:</div><br class="m_-6926211169150109977m_-4942096243117196752Apple-interchange-newline"></div></div><div><div><div class="m_-6926211169150109977h5"><div dir="ltr">I have done some work with Dolby on this but not specific to loudness. There is a standards initiative they've started to define a network format for metadata to go along with our network formats for audio and video. There are already means to carry metadata in video and AES3 and in many of the coded audio and video formats. <div><br></div><div>I think what is mostly missing is a metadata definition for loudness. What metadata would be in a loudness dataset? I know LUFS and dBTP would be central but the devil is in the details. Are these short-term, long-term or for the entire program. If for the program, how do we know where the program starts and ends. What is needed to specify the "DRC Profile" that AES71 introduces? How does a player use all of this stuff?</div><div><div><br></div><div>Kevin Gross - AVA Networks<br></div></div><div class="gmail_extra">
<br><div class="gmail_quote">On Thu, Jun 7, 2018 at 12:10 AM, Ian Shepherd <span dir="ltr"><<a href="mailto:ian@mastering-media.co.uk" target="_blank">ian@mastering-media.co.uk</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div dir="auto"><div><br></div>Same. I suspect it was left vague in AES71 because it’s a massive can of worms, and they want to allow flexibility in actually implementing it.<div><br></div><div>Either way I don’t personally have the bandwidth, either as part of this group or for the AES directly.</div><div><br></div><div>Having said that, I think including a recognition that mobile devices may need to use a higher level as an interim measure would be a good idea.</div><span class="m_-6926211169150109977m_-4942096243117196752HOEnZb"><font color="#888888"><div><br></div><div>Ian</div></font></span><div><div class="m_-6926211169150109977m_-4942096243117196752h5"><div><br></div><div><br><div><br>On 7 Jun 2018, at 01:31, Bob Katz <<a href="mailto:bobkatz@digido.com" target="_blank">bobkatz@digido.com</a>> wrote:<br><br></div><blockquote type="cite"><div><p>I think we'd have to bring in Dolby and other experts at least as
consultants. I only understand the basics of Metadata so I'd be
shooting in the dark.</p><p><br>
</p><p>Bob</p><p><br>
</p>
<br>
<div class="m_-6926211169150109977m_-4942096243117196752m_-7954694793874134295moz-cite-prefix">On 6/6/18 5:01 PM, Kevin Gross wrote:<br>
</div>
<blockquote type="cite">
<div dir="ltr">We need to get this metadata thing sorted out.
AES71 tells you when to use metadata but it doesn't say exactly
what it is, how to transport it or what you should do with it.
Is this something that we help could flesh out?</div>
<div class="gmail_extra"><br clear="all">
<div>
<div class="m_-6926211169150109977m_-4942096243117196752m_-7954694793874134295gmail_signature" data-smartmail="gmail_signature">
<div dir="ltr">Kevin Gross - AVA Networks</div>
</div>
</div>
<br>
<div class="gmail_quote">On Wed, Jun 6, 2018 at 1:22 PM, Bob
Katz <span dir="ltr"><<a href="mailto:bobkatz@digido.com" target="_blank">bobkatz@digido.com</a>></span>
wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<div bgcolor="#FFFFFF" text="#000000"><p>I'm in favor of any solution that lowers the
recommended target! But it's always interim. <br>
</p><p><br>
</p><p>-18 LUFS is 5 dB away from -23. It ought to be safe for
the majority of program with an emergency protection
limiter, at least for portable devices. But I would NOT
recommend -18 LUFS target for set top devices playing
wide range program material on loudspeakers. There's the
rub and the need for metadata.</p>
<span class="m_-6926211169150109977m_-4942096243117196752m_-7954694793874134295HOEnZb"><font color="#888888"><p><br>
</p><p>Bob</p>
</font></span>
<div>
<div class="m_-6926211169150109977m_-4942096243117196752m_-7954694793874134295h5"><p><br>
</p>
<br>
<div class="m_-6926211169150109977m_-4942096243117196752m_-7954694793874134295m_9032733808332111012moz-cite-prefix">On
6/5/18 8:49 PM, Ian Shepherd wrote:<br>
</div>
<blockquote type="cite">
<div><br>
</div>
<div><br>
<blockquote type="cite">
<div bgcolor="#FFFFFF" text="#000000"><p>Maybe the solution for fallback in the
absence of metadata on portable devices we
recommend a gain boost of 7 dB with a
protection limiter. Since it's music it's
likely to have a PLR of less than 16 dB so
if it was normalized to -23 it would hardly
trigger the limiter. But without metadata
how do you know it's music? And if they
normalize regular program to -23 it will be
too low for many portable devices, also. <br>
</p><p>Shit (excuse my French)</p>
</div>
</blockquote>
</div>
<div>We’ve settled on around -18 LUFS for my
podcast, which is plenty loud on my (European)
iPod with stock earbuds. Anecdotally the BBC seems
to be similar, and also works works fine, for the
most part.</div>
<div><br>
</div>
<div>We should look back through our notes for the
meeting where the podcast providers joined in, Bob
- from memory most of them had also settled on -16
or -18, I think.</div>
<div><br>
</div>
<div>I assume your concern is that raising normal
program to -16 would trigger excessive limiting,
Bob. Perhaps suggesting -18 (which is the median
of the AES recommended range) for everything would
be a workable compromise, when there’s no
meta-data ?</div>
<div><br>
</div>
<div>Ian</div>
<div><br>
</div>
<div><br>
</div>
</blockquote>
<br>
</div>
</div>
<span>
<div class="m_-6926211169150109977m_-4942096243117196752m_-7954694793874134295m_9032733808332111012moz-signature">-- <br>
<div class="m_-6926211169150109977m_-4942096243117196752m_-7954694793874134295m_9032733808332111012moz-signature">
<div class="m_-6926211169150109977m_-4942096243117196752m_-7954694793874134295m_9032733808332111012moz-signature">
<div class="m_-6926211169150109977m_-4942096243117196752m_-7954694793874134295m_9032733808332111012moz-signature">
<div class="m_-6926211169150109977m_-4942096243117196752m_-7954694793874134295m_9032733808332111012moz-signature">
<div class="m_-6926211169150109977m_-4942096243117196752m_-7954694793874134295m_9032733808332111012moz-signature">
<div class="m_-6926211169150109977m_-4942096243117196752m_-7954694793874134295m_9032733808332111012moz-signature">
<pre class="m_-6926211169150109977m_-4942096243117196752m_-7954694793874134295m_9032733808332111012moz-signature" cols="80"><font face="Courier">
If you want good sound on your album, come to
Bob Katz <span id="m_-6926211169150109977m_-4942096243117196752gc-number-11" class="m_-6926211169150109977m_-4942096243117196752gc-cs-link" title="Call with Google Voice"><span id="m_-6926211169150109977gc-number-61" class="m_-6926211169150109977gc-cs-link" title="Call with Google Voice"><span id="gc-number-28" class="gc-cs-link" title="Call with Google Voice">407-831-0233</span></span></span> </font><font face="Courier">DIGITAL DOMAIN MASTERING STUDIO
Author: <b>Mastering Audio </b></font><font face="Courier">
<a href="http://www.digido.com/" target="_blank">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>
</span></div>
</blockquote>
</div>
<br>
</div>
</blockquote>
<br>
<div class="m_-6926211169150109977m_-4942096243117196752m_-7954694793874134295moz-signature">-- <br>
<div class="m_-6926211169150109977m_-4942096243117196752m_-7954694793874134295moz-signature">
<div class="m_-6926211169150109977m_-4942096243117196752m_-7954694793874134295moz-signature">
<div class="m_-6926211169150109977m_-4942096243117196752m_-7954694793874134295moz-signature">
<div class="m_-6926211169150109977m_-4942096243117196752m_-7954694793874134295moz-signature">
<div class="m_-6926211169150109977m_-4942096243117196752m_-7954694793874134295moz-signature">
<div class="m_-6926211169150109977m_-4942096243117196752m_-7954694793874134295moz-signature">
<pre class="m_-6926211169150109977m_-4942096243117196752m_-7954694793874134295moz-signature" cols="80"><font face="Courier">
If you want good sound on your album, come to
Bob Katz <span id="m_-6926211169150109977m_-4942096243117196752gc-number-12" class="m_-6926211169150109977m_-4942096243117196752gc-cs-link" title="Call with Google Voice"><span id="m_-6926211169150109977gc-number-62" class="m_-6926211169150109977gc-cs-link" title="Call with Google Voice"><span id="gc-number-29" class="gc-cs-link" title="Call with Google Voice">407-831-0233</span></span></span> </font><font face="Courier">DIGITAL DOMAIN MASTERING STUDIO
Author: <b>Mastering Audio </b></font><font face="Courier">
<a href="http://www.digido.com/" target="_blank">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>
</div></blockquote></div></div></div></div></blockquote></div><br></div></div></div></div><span>
______________________________<wbr>_________________<br>MLA mailing list<br><a href="mailto:MLA@grimmaudio.nl" target="_blank">MLA@grimmaudio.nl</a><br><a href="http://grimmaudio.nl/mailman/listinfo/mla_grimmaudio.nl" target="_blank">http://grimmaudio.nl/mailman/l<wbr>istinfo/mla_grimmaudio.nl</a><br></span></div></blockquote></div><br></div><br>______________________________<wbr>_________________<br>
MLA mailing list<br>
<a href="mailto:MLA@grimmaudio.nl" target="_blank">MLA@grimmaudio.nl</a><br>
<a href="http://grimmaudio.nl/mailman/listinfo/mla_grimmaudio.nl" rel="noreferrer" target="_blank">http://grimmaudio.nl/mailman/l<wbr>istinfo/mla_grimmaudio.nl</a><br>
<br></blockquote></div><br></div></div></div></div>
______________________________<wbr>_________________<br>MLA mailing list<br><a href="mailto:MLA@grimmaudio.nl" target="_blank">MLA@grimmaudio.nl</a><br><a href="http://grimmaudio.nl/mailman/listinfo/mla_grimmaudio.nl" target="_blank">http://grimmaudio.nl/mailman/<wbr>listinfo/mla_grimmaudio.nl</a><br></div></blockquote></div></div></div><br></div><br>______________________________<wbr>_________________<br>
MLA mailing list<br>
<a href="mailto:MLA@grimmaudio.nl">MLA@grimmaudio.nl</a><br>
<a href="http://grimmaudio.nl/mailman/listinfo/mla_grimmaudio.nl" rel="noreferrer" target="_blank">http://grimmaudio.nl/mailman/<wbr>listinfo/mla_grimmaudio.nl</a><br>
<br></blockquote></div><br></div></div></div></div>