<?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: Strictly Leakage</title>
	<atom:link href="http://isgreaterthan.net/2008/01/strictly-leakage/feed/" rel="self" type="application/rss+xml" />
	<link>http://isgreaterthan.net/2008/01/strictly-leakage/</link>
	<description>Literary-minded culture blog</description>
	<lastBuildDate>Sun, 25 Sep 2011 06:38:40 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=abc</generator>
	<item>
		<title>By: Paul M Davis</title>
		<link>http://isgreaterthan.net/2008/01/strictly-leakage/comment-page-1/#comment-977</link>
		<dc:creator>Paul M Davis</dc:creator>
		<pubDate>Wed, 23 Jan 2008 23:07:47 +0000</pubDate>
		<guid isPermaLink="false">http://www.isgreaterthan.net/2008/01/23/strictly-leakage/#comment-977</guid>
		<description>It&#039;s a tough question. Leaks are definitely a problem, for many reasons--oftentimes what gets leaked isn&#039;t a final version of the album, and I believe the musicians have the right to decide what final version of their work makes it out to the audience. The problem with these contingency plans is that they end up discouraging critics from giving the albums a fair listen.

I haven&#039;t owned a CD player that wasn&#039;t built into a computer in years, so the watermarked CD&#039;s that often don&#039;t work on CD-R players are a problem for me (and I suspect many other music writers). The net effect of those sort of watermarked promos is to bury them under the pile on my desk of crap I never go through and writing the feature/preview based on what&#039;s available on the musicians&#039; Myspace/last.fm profiles or The Hype Machine. 

Listening parties are a joke as well--how many albums have you had a fair impression of based on one or two initial listens?

The basic fact here is that there may be no way of stemming these leaks. I&#039;d wager that many more leaks are coming from the production chain and the label end than writers and editors, and it&#039;s really impossible to stop them from getting out there unless you completely lock down the masters and &quot;leak&quot; it yourself, a la Radiohead or Stars.</description>
		<content:encoded><![CDATA[<p>It&#8217;s a tough question. Leaks are definitely a problem, for many reasons&#8211;oftentimes what gets leaked isn&#8217;t a final version of the album, and I believe the musicians have the right to decide what final version of their work makes it out to the audience. The problem with these contingency plans is that they end up discouraging critics from giving the albums a fair listen.</p>
<p>I haven&#8217;t owned a CD player that wasn&#8217;t built into a computer in years, so the watermarked CD&#8217;s that often don&#8217;t work on CD-R players are a problem for me (and I suspect many other music writers). The net effect of those sort of watermarked promos is to bury them under the pile on my desk of crap I never go through and writing the feature/preview based on what&#8217;s available on the musicians&#8217; Myspace/last.fm profiles or The Hype Machine. </p>
<p>Listening parties are a joke as well&#8211;how many albums have you had a fair impression of based on one or two initial listens?</p>
<p>The basic fact here is that there may be no way of stemming these leaks. I&#8217;d wager that many more leaks are coming from the production chain and the label end than writers and editors, and it&#8217;s really impossible to stop them from getting out there unless you completely lock down the masters and &#8220;leak&#8221; it yourself, a la Radiohead or Stars.</p>
]]></content:encoded>
	</item>
</channel>
</rss>

<!-- Performance optimized by W3 Total Cache. Learn more: http://www.w3-edge.com/wordpress-plugins/

Minified using disk
Page Caching using disk (enhanced)
Database Caching 4/3208 queries in 0.086 seconds using disk
Object Caching 686/690 objects using disk

Served from: isgreaterthan.net @ 2012-02-10 21:27:56 -->
