<?xml version="1.0" encoding="UTF-8"?><rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:dc="http://purl.org/dc/elements/1.1/"
	xmlns:atom="http://www.w3.org/2005/Atom"
	xmlns:sy="http://purl.org/rss/1.0/modules/syndication/"
		>
<channel>
	<title>Comments on: How Spotify will end the Loudness Wars</title>
	<atom:link href="http://productionadvice.co.uk/spotify-loudness-war/feed/" rel="self" type="application/rss+xml" />
	<link>http://productionadvice.co.uk/spotify-loudness-war/</link>
	<description>make your music sound great</description>
	<lastBuildDate>Sun, 20 May 2012 23:40:59 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.3.1</generator>
	<item>
		<title>By: Studio Manifesto&#124;The Decibel Heap &#8211; A List of Loudness</title>
		<link>http://productionadvice.co.uk/spotify-loudness-war/comment-page-1/#comment-4156</link>
		<dc:creator>Studio Manifesto&#124;The Decibel Heap &#8211; A List of Loudness</dc:creator>
		<pubDate>Thu, 09 Jun 2011 15:37:22 +0000</pubDate>
		<guid isPermaLink="false">http://productionadvice.co.uk/?p=1467#comment-4156</guid>
		<description>[...] 2. How Spotify Might Defuse the Loudness War from Production Advice [...]</description>
		<content:encoded><![CDATA[<p>[...] 2. How Spotify Might Defuse the Loudness War from Production Advice [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Why I was wrong about Spotify</title>
		<link>http://productionadvice.co.uk/spotify-loudness-war/comment-page-1/#comment-1604</link>
		<dc:creator>Why I was wrong about Spotify</dc:creator>
		<pubDate>Sat, 07 Nov 2009 01:03:06 +0000</pubDate>
		<guid isPermaLink="false">http://productionadvice.co.uk/?p=1467#comment-1604</guid>
		<description>[...] How Spotify will end the Loudness Wars  [...]</description>
		<content:encoded><![CDATA[<p>[...] How Spotify will end the Loudness Wars  [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Ian Shepherd</title>
		<link>http://productionadvice.co.uk/spotify-loudness-war/comment-page-1/#comment-1396</link>
		<dc:creator>Ian Shepherd</dc:creator>
		<pubDate>Fri, 09 Oct 2009 22:19:39 +0000</pubDate>
		<guid isPermaLink="false">http://productionadvice.co.uk/?p=1467#comment-1396</guid>
		<description>@Tor That&#039;s a fair comment and something I&#039;ve worried about. I think I will write a new one with only the correct information. I felt it was important to keep this one up to begin with, though. I&#039;ll archive it and link to it from the new one for people who are interested.</description>
		<content:encoded><![CDATA[<p>@Tor That&#8217;s a fair comment and something I&#8217;ve worried about. I think I will write a new one with only the correct information. I felt it was important to keep this one up to begin with, though. I&#8217;ll archive it and link to it from the new one for people who are interested.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Tor Arne</title>
		<link>http://productionadvice.co.uk/spotify-loudness-war/comment-page-1/#comment-1390</link>
		<dc:creator>Tor Arne</dc:creator>
		<pubDate>Fri, 09 Oct 2009 12:17:26 +0000</pubDate>
		<guid isPermaLink="false">http://productionadvice.co.uk/?p=1467#comment-1390</guid>
		<description>You should leave the original article without the strikeouts and red, reading it now for context for your other post (the update) is completely impossible.</description>
		<content:encoded><![CDATA[<p>You should leave the original article without the strikeouts and red, reading it now for context for your other post (the update) is completely impossible.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Studio Manifesto &#124; How Spotify might defuse the Loudness Wars &#124; Studio Manifesto</title>
		<link>http://productionadvice.co.uk/spotify-loudness-war/comment-page-1/#comment-1379</link>
		<dc:creator>Studio Manifesto &#124; How Spotify might defuse the Loudness Wars &#124; Studio Manifesto</dc:creator>
		<pubDate>Mon, 05 Oct 2009 13:13:48 +0000</pubDate>
		<guid isPermaLink="false">http://productionadvice.co.uk/?p=1467#comment-1379</guid>
		<description>[...] Read the full article (and subsequent corrections) at Production Advice [...]</description>
		<content:encoded><![CDATA[<p>[...] Read the full article (and subsequent corrections) at Production Advice [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: pete whitfield</title>
		<link>http://productionadvice.co.uk/spotify-loudness-war/comment-page-1/#comment-1374</link>
		<dc:creator>pete whitfield</dc:creator>
		<pubDate>Sun, 04 Oct 2009 09:15:24 +0000</pubDate>
		<guid isPermaLink="false">http://productionadvice.co.uk/?p=1467#comment-1374</guid>
		<description>Good to provoke this discussion Ian - and to be so honest and transparent about it.</description>
		<content:encoded><![CDATA[<p>Good to provoke this discussion Ian &#8211; and to be so honest and transparent about it.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Dean Whitbread</title>
		<link>http://productionadvice.co.uk/spotify-loudness-war/comment-page-1/#comment-1371</link>
		<dc:creator>Dean Whitbread</dc:creator>
		<pubDate>Sun, 04 Oct 2009 02:05:51 +0000</pubDate>
		<guid isPermaLink="false">http://productionadvice.co.uk/?p=1467#comment-1371</guid>
		<description>As a passionate audiophile, you can be forgiven for making the odd mistake. Your honesty is a shining beacon of hope and decency - remind yourself never to go into politics.</description>
		<content:encoded><![CDATA[<p>As a passionate audiophile, you can be forgiven for making the odd mistake. Your honesty is a shining beacon of hope and decency &#8211; remind yourself never to go into politics.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Tom</title>
		<link>http://productionadvice.co.uk/spotify-loudness-war/comment-page-1/#comment-1366</link>
		<dc:creator>Tom</dc:creator>
		<pubDate>Sat, 03 Oct 2009 10:49:21 +0000</pubDate>
		<guid isPermaLink="false">http://productionadvice.co.uk/?p=1467#comment-1366</guid>
		<description>I&#039;d just like to add that you should be careful because when Spotify update their app, at least on mac, they do it in the background, and the user is not notified. When the app is updated, the preferences are reset to default. 

Just now I noticed that Spotify had been updated and had reverted to normalisation   on, and disabled high quality files for playback!</description>
		<content:encoded><![CDATA[<p>I&#8217;d just like to add that you should be careful because when Spotify update their app, at least on mac, they do it in the background, and the user is not notified. When the app is updated, the preferences are reset to default. </p>
<p>Just now I noticed that Spotify had been updated and had reverted to normalisation   on, and disabled high quality files for playback!</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: ludde</title>
		<link>http://productionadvice.co.uk/spotify-loudness-war/comment-page-1/#comment-1365</link>
		<dc:creator>ludde</dc:creator>
		<pubDate>Sat, 03 Oct 2009 09:33:38 +0000</pubDate>
		<guid isPermaLink="false">http://productionadvice.co.uk/?p=1467#comment-1365</guid>
		<description>Ian,

I&#039;d like to find the cause as much as you do, but from my analysis, having normalization on results in less distortion than if normalization is off.

I have a bunch of sample files from my test. Drop me an email and I can send them to you as well as a more lengthy explanation/clarification.</description>
		<content:encoded><![CDATA[<p>Ian,</p>
<p>I&#8217;d like to find the cause as much as you do, but from my analysis, having normalization on results in less distortion than if normalization is off.</p>
<p>I have a bunch of sample files from my test. Drop me an email and I can send them to you as well as a more lengthy explanation/clarification.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Ian Shepherd</title>
		<link>http://productionadvice.co.uk/spotify-loudness-war/comment-page-1/#comment-1364</link>
		<dc:creator>Ian Shepherd</dc:creator>
		<pubDate>Sat, 03 Oct 2009 07:58:50 +0000</pubDate>
		<guid isPermaLink="false">http://productionadvice.co.uk/?p=1467#comment-1364</guid>
		<description>Hi Ludde,

Thanks for posting !

Sorry, but this is working in the opposite way to what you describe, in listening terms.

With &quot;Volume Normalisation&quot; ON (ie. with the checkbox ticked) the playback level is LOWER, and the kick and snare drum have audibly less impact, as a result of limiting. This is the &quot;flat, empty sound&quot; described by everyone in the thread on your forum.

With &quot;Volume Normalisation&quot; OFF (ie. with the checkbox un-ticked) the playback level is HIGHER, and the kick and snare have more impact.

Try listening to &quot;Yellow&quot;, by Coldplay, for a clearer example.

But you are saying that the gain is added to the &quot;normalised&quot; version only, and that the limiter is always active ? If so, the limiter settings must be &lt;strong&gt;incredibly&lt;/strong&gt; aggressive, to reduce the overall replay level by 3dB - it would be no wonder in this case that the normalised version sounds bad. It&#039;s also, as my post says, &lt;em&gt;completely unnecessary&lt;/em&gt; since to achieve normalisation, all that&#039;s required it to reduce the level of louder tracks somewhat.

Are you saying that there is no adjustment of level based on the original dynamic range, in the &quot;normaliser&quot; ? You&#039;re simply lifting the level of everything and letting the limiter squash it all ? 

Ian

PS. Both VN-ON and VN-OFF samples were captured from Spotify, using Wavelab.

PPS. The &quot;trebly&quot; stuff is just high-frequency content that is left over from the null test (remember you need to level-match before nulling). A complete null isn&#039;t possible, even adjusting in increments of 0.1 dB, but most of the signal does cancel, except for the limiter &quot;pulses&quot;.</description>
		<content:encoded><![CDATA[<p>Hi Ludde,</p>
<p>Thanks for posting !</p>
<p>Sorry, but this is working in the opposite way to what you describe, in listening terms.</p>
<p>With &#8220;Volume Normalisation&#8221; ON (ie. with the checkbox ticked) the playback level is LOWER, and the kick and snare drum have audibly less impact, as a result of limiting. This is the &#8220;flat, empty sound&#8221; described by everyone in the thread on your forum.</p>
<p>With &#8220;Volume Normalisation&#8221; OFF (ie. with the checkbox un-ticked) the playback level is HIGHER, and the kick and snare have more impact.</p>
<p>Try listening to &#8220;Yellow&#8221;, by Coldplay, for a clearer example.</p>
<p>But you are saying that the gain is added to the &#8220;normalised&#8221; version only, and that the limiter is always active ? If so, the limiter settings must be <strong>incredibly</strong> aggressive, to reduce the overall replay level by 3dB &#8211; it would be no wonder in this case that the normalised version sounds bad. It&#8217;s also, as my post says, <em>completely unnecessary</em> since to achieve normalisation, all that&#8217;s required it to reduce the level of louder tracks somewhat.</p>
<p>Are you saying that there is no adjustment of level based on the original dynamic range, in the &#8220;normaliser&#8221; ? You&#8217;re simply lifting the level of everything and letting the limiter squash it all ? </p>
<p>Ian</p>
<p>PS. Both VN-ON and VN-OFF samples were captured from Spotify, using Wavelab.</p>
<p>PPS. The &#8220;trebly&#8221; stuff is just high-frequency content that is left over from the null test (remember you need to level-match before nulling). A complete null isn&#8217;t possible, even adjusting in increments of 0.1 dB, but most of the signal does cancel, except for the limiter &#8220;pulses&#8221;.</p>
]]></content:encoded>
	</item>
</channel>
</rss>

<!-- Served from: productionadvice.co.uk @ 2012-05-21 18:07:15 by W3 Total Cache -->
