<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=utf-8">
</head>
<body text="#000000" bgcolor="#FFFFFF">
<p>Dynamics processing in streaming on mastered material is just
another backwards step to the ugly Orban, ugly-sounding and ugly
radio land. No ONE, I mean no ONE knows what's optimal for every
venue. NO ENGINEER has preknowlege of what the user's venue or
user's conditions are going to be. And giving the user the choice
rarely results in anything good. <br>
</p>
<p>Furthermore, presets called "Loud" and "Normal" are just ways of
making the sound "squashed" and "more squashed". Applying downward
compression, limiting and Orban style processing presets on top of
music which can vary from the most unprocessed to the most smashed
is just going to further and seriously distort the smashed
recordings, and ruin the depth and clarity of any high quality
material. Thus returning to the distortions that we successfully
got rid of by inventing R-128 in the first place! This is WHY the
EBU and ATSC do NOT advocate ANY loudness processing, simply
loudness normalization. Do you think that Spotify knows better
than experienced broadcast engineers?<br>
</p>
<p>There are two proper solutions to the noisy venue problem. The
eventual and proper one is to move to is a noise-based processor
that incorporates the microphone in the user device and raises the
gain of low level material without any level-based time-constants.
<br>
</p>
As we wait for a microphone-noise-based processor to be perfected, I
would propose interim presets labeled "noisy environment" "medium
noisey environment' and "quiet environment". These would use
parallel compression which is designed to be invisible at high
levels and only effective meaningful at low levels. NOT the kind of
processing that I wager Spotify is using. I wager they're using
ugly, undiscriminated, downward compression and limiting. <br>
<p>Otherwise vendors and streamers should keep their noses out of
the processing business. It failed and sucked with radio and
they're just bound to repeat the mistakes of FM radio :-(</p>
<p><br>
</p>
<p><br>
</p>
<p>Let's call a spade a spade and do things right. <br>
</p>
<p><br>
</p>
<p>Bob</p>
<p><br>
</p>
<br>
<div class="moz-cite-prefix">On 3/16/18 12:07 PM, Kevin Gross wrote:<br>
</div>
<blockquote type="cite"
cite="mid:CALw1_Q09-P5KoYpuPSsL-8T-SquZNOQ=MpSSLqbXpxf0+43XHA@mail.gmail.com">
<div dir="ltr">
<div class="gmail_extra">
<div class="gmail_quote">On Fri, Mar 16, 2018 at 3:22 AM,
Grimm | Eelco <span dir="ltr"><<a
href="mailto:eelco@grimmaudio.com" target="_blank"
moz-do-not-send="true">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><br>
</div>
<div>Let’s hope we can nudge Apple to implement the
“extra headroom with normalization on” option soon.
Then we just switch to a -23 LUFS target and have a
beer :-)</div>
<div><br>
</div>
<div>Cheers,</div>
<div>Eelco</div>
<div><br>
</div>
</div>
</blockquote>
<div>We have talked in this group in the past about the
potential need for different processing for different
listening scenarios. Spotify is touching on this with
their "Loud", "Normal", "Quiet" options. Based on the fact
that loudness-normalized material is played off a
different server, it appears they're doing some dynamics
processing. We've said that we'd look at this once we had
solid recommendations for unprocessed loudness
normalization. Maybe it is time to get started.</div>
<div><br>
</div>
<div>Kevin</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>