<html>
<head>
<meta http-equiv="Content-Type" content="text/html;
charset=windows-1252">
</head>
<body text="#000000" bgcolor="#FFFFFF">
<p>We had some similar information from the developer of iTunes in
our correspondence years ago. afinfo tantalizingly tells us a
little about the measurements of the music.<br>
</p>
<p>Personally I hope that Apple changes over to R128-style analysis.
Though who knows? Maybe they know something that we don't know by
incorporating some short term peak information into their
calculations for sound check. <br>
</p>
<p>My biggest wish is for Apple to start normalizing Beats Radio
(Apple Music) ASAP! My clients are so confused when I tell them
that Spotify will normalize but Apple won't etc. etc. etc. <br>
</p>
<p><br>
</p>
<p>Bob</p>
<p><br>
</p>
<br>
<div class="moz-cite-prefix">On 9/7/17 8:49 AM, Grimm | Eelco wrote:<br>
</div>
<blockquote type="cite"
cite="mid:F582E083-D83A-431F-A82E-FFE13E3C9946@grimmaudio.com">
<div dir="ltr">
<div>ft Channel, in milliseconds from file start</div>
<div>10. Position of Max Sample Peak, Right Channel, in
milliseconds from file start</div>
<div><br>
</div>
<div>All values are stored as a single string in 8-digit HEX
format in the file metadata but they can be viewed as decimal
numbers (not dB values) via Terminal with afinfo command.</div>
<div><br>
</div>
<div>For RMS values 1 to 4, an EQ curve somewhat similar to ISO
223 is used for the frequency weighting.</div>
<div><br>
</div>
<div>The file is adjusted by searching the maximum single value
of 1 and 2, and attenuated accordingly if the values 7 or 8
would exceed 0dBfs for wav file extension and -1 dBFS for the
m4a file extension (even for Apple Lossless encoding) after
the adjustment of 1 and 2.</div>
<div><br>
</div>
<div>The max perceived loudness values (3&4) and the
location values (5,6 and 9,10) do not affect the adjustment.</div>
<div><br>
</div>
<div>This test was done by setting the values 7 and 8 to zero,
so that the player doesn't attenuate by the sample peak
values.</div>
<div><br>
</div>
<div>All the best,</div>
<div>Mikko</div>
<div><br>
</div>
<div><br>
</div>
<div><br>
</div>
<div><br>
</div>
<div><br>
</div>
<div><br>
</div>
</div>
<div class="gmail_extra"><br>
<div class="gmail_quote">2017-09-06 23:58 GMT+03:00 Eelco Grimm
<span dir="ltr"><<a href="mailto:eelco.grimm@hku.nl"
target="_blank" moz-do-not-send="true">eelco.grimm@hku.nl</a>></span>:<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 Mikko,</div>
<div><br>
</div>
<div>Great catch!</div>
<div><br>
</div>
<div>Can you explain what you mean with "It is only
possible to adjust a file within -12 to +12 dB's."?
Which adjustment is that?</div>
<div><br>
</div>
<div>And I figure that your implementation idea would be
to just have a +7 dB offset for -23 LUFS material in the
streaming app. But of course this will lead to clipping
as soon as users turn up the volume and peaks on the
original program are louder than -7 dBFS. Mark that I am
not sure if this is a very bad thing (it only happens
when people play very loud and in that case the ear buds
will already distort a lot...), but if possible a
limiter would be more elegant.</div>
<div><br>
</div>
<div>All the best,</div>
<div>Eelco</div>
<div><br>
<blockquote type="cite"><span class="">
<div dir="ltr">
<div>I am running Apple's iOS 11 Beta on my phone,
and I discovered that the manufacturer has made
a good step in loudness normalisation
architecture.</div>
<div><br>
</div>
<div>I have understood that previous versions of
the iOS operating system have used fixed point
architecture and therefore it was important to
not exceed peaks before the device volume
control stage. Thi</div>
</div>
</span></blockquote>
</div>
</div>
</blockquote>
</div>
</div>
</blockquote>
<br>
<div class="moz-signature">-- <br>
<meta http-equiv="content-type" content="text/html;
charset=windows-1252">
<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>