<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=utf-8">
</head>
<body bgcolor="#FFFFFF" text="#000000">
<p>Spotify Giving more than one option is bound to be confusing for
the user and ultimately a mess for mastering engineers trying to
communicate ONE MESSAGE to our clients.<br>
</p>
Secondly, regardless of the Cenelec issue and the low headphones
issue on cheap devices we have to hold our ground. Advocating -11
LUFS at any point is a real problem sonically and a real compromise
sonically. There has to be another solution and we must NEVER EVER
advocate -11 LUFS. It's a stupid idea and cannot be rationalized
away. <br>
<br>
Even Thomas accepts -14 LUFS with album normalization, so let's not
cross that line in the sand. And to repeat: -14 without album
normalization is unacceptable also. So we need to know whether
Spotify has album norm.<br>
<br>
<br>
Bob<br>
<br>
<br>
<br>
<div class="moz-cite-prefix">On 3/8/18 6:26 PM, Grimm | Eelco wrote:<br>
</div>
<blockquote type="cite"
cite="mid:47AC1187-9B8B-464B-94B9-5190262AED39@grimmaudio.com">
<pre wrap="">Hi all,
</pre>
<blockquote type="cite">
<pre wrap="">Another interesting Spotify thing though - two people have emailed me to say that their latest iOS versions have three different normalisation choices:
Loud (-11)
Normal (-14)
Quiet (??)
I don’t see it here yet, though.
</pre>
</blockquote>
<pre wrap="">
I checked it with my Spotify contact. He wrote (please keep it confidential):
</pre>
<blockquote type="cite">
<pre wrap="">Yes, this is indeed true!
Loud is -11, Normal -14 and Quiet is -23.
Default is Normal, and will remain so, don't worry!
The thinking here is that we can cater to the three different use cases that we have identified:
- The most common situation is that -14 is loud enough for users to be able to play as loud as they need.
- Quiet, -23, is there for all those who actually care about the dynamics and want a really good experience - and, most importantly, they are either in such a quiet environment that they can deal with -23 or they have enough power (eg in a home hifi system) to bring up the volume sufficiently.
- Loud is for those users (yes, we do receive complaints about this) whose earphones on their mobile phones can't give them enough loudness in the environment they're in.
</pre>
</blockquote>
<pre wrap="">
So the good news that -23 LUFS is in! And that -14 LUFS is still default. But of course, our fear is that mastering engineers will take the ‘loud’ -11 LUFS as their target “just to be sure".
He also wrote that it should already be present in the current app. I updated my app to the brand new 8.4.43 but still don’t see the options. Maybe they’re not shown in the Spotify Free app? I check it with him.
The whole discussion triggered an idea that I shared with him. Let’s hope he gets enthusiastic and that we can get Apple and Google on board with it (I know it will be quite difficult…). It goes like this:
I thought about the Cenelec requirements for smart phones in the EU: the special noise signal of -11 LUFS is not allowed to play louder than 100 dBA on the ear buds. Let’s say the device is limited to this level. If we normalize that test file to -14 LUFS, we attenuate it by 3 dB. It will now play to max 97 dBA. Apparently that leads to complaints at Spotify, and legally one would indeed be allowed to play 3 dB louder. There are two ways to solve this:
1. Set the target level to -11 LUFS. This is Spotify's current ‘loud’ option. The disadvantage is that the normalization target is raised and mastering engineers may use that as a reference.
2. Let the Spotify app signal to the OS of the phone that normalization at -14 LUFS is engaged. The OS can then offer 3 dB extra gain to audio from the Spotify app and still comply with Cenelec. If the ref noise is played with normalization on, it will have a max of 100 dBA. If normalization is turned off, the OS will not offer the extra 3 dB headroom and again play at 100 dBA max.
The beauty of the second method is that you may also choose a -23 LUFS target and still play equally loud as a non-normalized app...
Fingers crossed…
Cheers,
Eelco
_______________________________________________
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>