<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=utf-8">
</head>
<body text="#000000" bgcolor="#FFFFFF">
<p>As was pointed out, Tidal have to retain the track loudness
values in order to compute album normalization. So thank you very
much, it is totally possible to add or restore track
normalization....</p>
<p><br>
</p>
<p>BK</p>
<p><br>
</p>
<br>
<div class="moz-cite-prefix">On 12/14/17 1:22 AM, Thomas Lund wrote:<br>
</div>
<blockquote type="cite"
cite="mid:BA93B428-E6A4-4033-AD29-31294BF1DCBB@lund.one">
<meta http-equiv="Content-Type" content="text/html; charset=utf-8">
It has long been in MQA’s plans to integrate loudness
normalization, which should be easy to do well in a highly
proprietary system.
<div class=""><br class="">
</div>
<div class="">When I circulated the different streaming
level-diagrams 4 years ago, one of the reasons was Roon, then a
sound quality oriented frontend to Tidal. They were also
interested in quality-conscious search criteria based on PLR or
Programme Loudness filtering. In case Tidal indeed have
discarded track data, <i class="">that</i> motivating function
will not come to fruition now; thank you very much.</div>
<div class=""><br class="">
</div>
<div class="">br Thomas</div>
<div class=""><br class="">
<div class=""><br class="">
</div>
<div class=""><br class="">
<div>
<blockquote type="cite" class="">
<div class="">On 14 Dec 2017, at 00.44, Grimm | Eelco <<a
href="mailto:eelco@grimmaudio.com" class=""
moz-do-not-send="true">eelco@grimmaudio.com</a>>
wrote:</div>
<br class="Apple-interchange-newline">
<div class="">
<meta http-equiv="Content-Type" content="text/html;
charset=utf-8" class="">
<div style="word-wrap: break-word; -webkit-nbsp-mode:
space; -webkit-line-break: after-white-space;"
class="">
<div class="">Just some extra info: MQA on Tidal has
loudness normalization (I was told - I did not test
it yet). </div>
<div class=""><br class="">
</div>
<div class="">Plus I am cooperating with Roon Labs to
forward the metadata of Tidal and the local audio
files through our upcoming media player downstream
to our LS1 loudspeakers so the volume setting and
loudness data are merged in the DSP at the final
stage before the DAC - yes that is 'norm-l'. It is
all possible right now and pretty audiophile. You
can even forward the metadata further downstream to
a digitally controlled analog volume stage after the
DAC if that's your taste.</div>
<div class=""><br class="">
</div>
<div class="">Cheers,</div>
<div class="">Eelco</div>
<div class=""><br class="">
</div>
<div class="">
<blockquote type="cite" class="">
<div dir="auto" class="">Audiophiles can have
anxiety about bit transparency so could shun
loudness normalization on those grounds. But MQA
is not bit transparent so that doesn't seem to
be a reasonable objection in this context. Is
there some nice story we can tell about a
symbiotic relationship between high resolution
or MQA and loudness normalization?<br class="">
<br class="">
<div data-smartmail="gmail_signature" dir="auto"
class="">Kevin </div>
<div class="gmail_extra" dir="auto"><br class="">
<div class="gmail_quote">On Dec 12, 2017 8:19
AM, "Robert Ludwig" <<a
href="mailto:gatewaybob@mac.com" class=""
moz-do-not-send="true">gatewaybob@mac.com</a>>
wrote:<br type="attribution" class="">
<blockquote class="quote" style="margin:0 0
0 .8ex;border-left:1px #ccc
solid;padding-left:1ex">
<div style="word-wrap:break-word" class="">Hi
Bob K!
<div class=""><br class="">
</div>
<div class="">
<blockquote type="cite" class="">
<div text="#000000"
bgcolor="#FFFFFF" class="">I
cannot justify a Tidal
subscription each month so I am
not subscribed. </div>
</blockquote>
<div class=""><br class="">
</div>
<div class="">But Bob K. you CAN <u
class="">test out</u> the TIDAL
Hi-Fi/ TIDAL-Masters for free for 30
days. </div>
<div class=""><br class="">
</div>
<div class="">It should sound
identical to the MQA site you are
beta testing. You can compare
buffering algorithms when used for
DSL and less-than fast internet
hook-ups. Tidal used to work well
on my home DSL, now not as much
after the last software revision.
The new beta site seemed to be
better in that regard.</div>
<br class="">
<blockquote type="cite" class="">
<div text="#000000"
bgcolor="#FFFFFF" class="">But I
am currently beta testing a new
high resolution MQA streaming
service that has not yet become
public. The sound quality of the
MQA on the stream made from good
2496 and higher resolution masters
is astounding. If this service can
obtain more high resolution
masters and have a good selection,
I would subscribe to them at
$19.99 a month. <br class="">
</div>
</blockquote>
<div class=""><br class="">
</div>
Just playing devil’s advocate:<br
class="">
So, being that TIDAL already HAS lots
more high resolution masters than the
beta site, and the fact that they are
BOTH $19.99 a month, why favor the
beta site? <br class="">
<br class="">
<blockquote type="cite" class="">
<div text="#000000"
bgcolor="#FFFFFF" class=""> I have
not yet brought up the issue of
loudness normalization to them, as
I suspect the director of the
company will hit the roof…</div>
</blockquote>
<br class="">
</div>
<div class="">I completely agree here, I
would not want to be the one to bring
it up.</div>
<div class=""><br class="">
</div>
<div class="">As a matter of curiosity,
have you come across titles that do
NOT seem to benefit from MQA? For me,
I have found quite a few pop titles
and even some classical titles where
they sounded better without clearer
transients. Just curious!</div>
<div class=""><br class="">
</div>
<div class="">Best!</div>
<div class="">Bob L.</div>
</div>
<br class="">
______________________________<wbr
class="">_________________<br class="">
MLA mailing list<br class="">
<a href="mailto:MLA@grimmaudio.nl"
class="" moz-do-not-send="true">MLA@grimmaudio.nl</a><br
class="">
<a
href="http://grimmaudio.nl/mailman/listinfo/mla_grimmaudio.nl"
rel="noreferrer" target="_blank"
class="" moz-do-not-send="true">http://grimmaudio.nl/mailman/<wbr
class="">listinfo/mla_grimmaudio.nl</a><br
class="">
<br class="">
</blockquote>
</div>
<br class="">
</div>
</div>
_______________________________________________<br
class="">
MLA mailing list<br class="">
<a href="mailto:MLA@grimmaudio.nl" class=""
moz-do-not-send="true">MLA@grimmaudio.nl</a><br
class="">
<a
href="http://grimmaudio.nl/mailman/listinfo/mla_grimmaudio.nl"
class="" moz-do-not-send="true">http://grimmaudio.nl/mailman/listinfo/mla_grimmaudio.nl</a><br
class="">
</blockquote>
</div>
<br class="">
</div>
_______________________________________________<br
class="">
MLA mailing list<br class="">
<a href="mailto:MLA@grimmaudio.nl" class=""
moz-do-not-send="true">MLA@grimmaudio.nl</a><br
class="">
<a class="moz-txt-link-freetext" href="http://grimmaudio.nl/mailman/listinfo/mla_grimmaudio.nl">http://grimmaudio.nl/mailman/listinfo/mla_grimmaudio.nl</a><br
class="">
</div>
</blockquote>
</div>
<br class="">
</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>