<?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: Managing a digital music collection Part 4: Getting it together</title>
	<atom:link href="http://qwertyuiopia.com/2007/12/16/managing-a-digital-music-collection-part-4-getting-it-together/feed/" rel="self" type="application/rss+xml" />
	<link>http://qwertyuiopia.com/2007/12/16/managing-a-digital-music-collection-part-4-getting-it-together/</link>
	<description>Chewing down culture into little bits.</description>
	<lastBuildDate>Tue, 20 Jul 2010 08:20:17 +0000</lastBuildDate>
	<generator>http://wordpress.org/?v=2.9.2</generator>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
		<item>
		<title>By: Harley Marshall</title>
		<link>http://qwertyuiopia.com/2007/12/16/managing-a-digital-music-collection-part-4-getting-it-together/comment-page-1/#comment-461</link>
		<dc:creator>Harley Marshall</dc:creator>
		<pubDate>Thu, 15 Jul 2010 15:39:00 +0000</pubDate>
		<guid isPermaLink="false">http://qwertyuiopia.com/2007/12/16/managing-a-digital-music-collection-part-4-getting-it-together/#comment-461</guid>
		<description>when i hear about David Bowie, it reminds me of Vanilla Ice. :-&#039;</description>
		<content:encoded><![CDATA[<p>when i hear about David Bowie, it reminds me of Vanilla Ice. :-&#8217;</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Communications</title>
		<link>http://qwertyuiopia.com/2007/12/16/managing-a-digital-music-collection-part-4-getting-it-together/comment-page-1/#comment-444</link>
		<dc:creator>Communications</dc:creator>
		<pubDate>Fri, 25 Jun 2010 00:06:16 +0000</pubDate>
		<guid isPermaLink="false">http://qwertyuiopia.com/2007/12/16/managing-a-digital-music-collection-part-4-getting-it-together/#comment-444</guid>
		<description>Great post. I really appreciate the information.  You have done a good job communicating your message.  Keep up the good writing.</description>
		<content:encoded><![CDATA[<p>Great post. I really appreciate the information.  You have done a good job communicating your message.  Keep up the good writing.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Nathanial Mcconahy</title>
		<link>http://qwertyuiopia.com/2007/12/16/managing-a-digital-music-collection-part-4-getting-it-together/comment-page-1/#comment-384</link>
		<dc:creator>Nathanial Mcconahy</dc:creator>
		<pubDate>Fri, 19 Feb 2010 12:57:58 +0000</pubDate>
		<guid isPermaLink="false">http://qwertyuiopia.com/2007/12/16/managing-a-digital-music-collection-part-4-getting-it-together/#comment-384</guid>
		<description>I extremely enjoyed this! I would have to say this is an awful informative post that deserves mentioning elsewhere.</description>
		<content:encoded><![CDATA[<p>I extremely enjoyed this! I would have to say this is an awful informative post that deserves mentioning elsewhere.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Amr</title>
		<link>http://qwertyuiopia.com/2007/12/16/managing-a-digital-music-collection-part-4-getting-it-together/comment-page-1/#comment-137</link>
		<dc:creator>Amr</dc:creator>
		<pubDate>Sat, 06 Dec 2008 12:34:16 +0000</pubDate>
		<guid isPermaLink="false">http://qwertyuiopia.com/2007/12/16/managing-a-digital-music-collection-part-4-getting-it-together/#comment-137</guid>
		<description>Good description. I came to almost the same arrangement, and deciding now about a few things and could use your input on:

* Disc # of #: I think the x/x  practise (also in track number) breaks universal causality. Software should be able to take this field&#039;s value and compute on it. The &#039;Disc # of #&#039; information should belong elsewhere.

* Disc number in structure: .../%album%/Disc %discnumber%/... or the way you are doing it is still something I need to decide on. It feels that having files at different levels in the hierarchy (some releases are single-disc, other are multiple-disc) is not right, but so does putting a single release in two or more folders: Album (Disc 1) and Album (Disc 2). We are still too attached to physical disc limitations, while in soft-and-digital world, a release is a release.

* %filetype% at the top of the structure: I keep lossy and lossless copies of my music in the same structure: Music/ogg/Artist and Music/flac/Artist, so keeping them separate at a higher level is good in mass-file manipulation. I am also moving away from MP3 to OGG, and this is a process that will take years, so it is good to see Music/ogg growing and Music/mp3 and other formats shrinking as I make the transition.

* File names: I like to think of the whole structure together. There is no need to repeat the artist name in the file name, because it is already in the Artist folder (and the tags if the file lost its way outside the hierarchy). This is my current suggestion: Music/ogg/Pink Floyd/1977 Animals/03-Dogs.ogg

* Spaces in file names: Especially if you are going to manipulate the files later using Linux bash, wouldn&#039;t it be easier to remove spaces from folder and file names, either partially (Music/ogg/Pink Floyd/1975 Wish you were here/01-Shine on you crazy diamond.ogg) or totally (Music/ogg/Pink.Floyd/1975-Wish.you.were.here/01-Shine.on.you.crazy.diamond.ogg)?

* Compilations: I use Picard and like the way it sorts this out. It places all compilations in a Various Artists folder right next to other artists, but then, would you place the artist name in the file name?

There are a few other issues regarding non-Roman script and Windows incompatible characters, also what to do with &#039;bonus disc&#039; and &#039;feature artist&#039; info in file naming, and what to call cover images and whether they should be embedded into tags or not.

This can be detailed enough to go on an RFC!</description>
		<content:encoded><![CDATA[<p>Good description. I came to almost the same arrangement, and deciding now about a few things and could use your input on:</p>
<p>* Disc # of #: I think the x/x  practise (also in track number) breaks universal causality. Software should be able to take this field&#8217;s value and compute on it. The &#8216;Disc # of #&#8217; information should belong elsewhere.</p>
<p>* Disc number in structure: &#8230;/%album%/Disc %discnumber%/&#8230; or the way you are doing it is still something I need to decide on. It feels that having files at different levels in the hierarchy (some releases are single-disc, other are multiple-disc) is not right, but so does putting a single release in two or more folders: Album (Disc 1) and Album (Disc 2). We are still too attached to physical disc limitations, while in soft-and-digital world, a release is a release.</p>
<p>* %filetype% at the top of the structure: I keep lossy and lossless copies of my music in the same structure: Music/ogg/Artist and Music/flac/Artist, so keeping them separate at a higher level is good in mass-file manipulation. I am also moving away from MP3 to OGG, and this is a process that will take years, so it is good to see Music/ogg growing and Music/mp3 and other formats shrinking as I make the transition.</p>
<p>* File names: I like to think of the whole structure together. There is no need to repeat the artist name in the file name, because it is already in the Artist folder (and the tags if the file lost its way outside the hierarchy). This is my current suggestion: Music/ogg/Pink Floyd/1977 Animals/03-Dogs.ogg</p>
<p>* Spaces in file names: Especially if you are going to manipulate the files later using Linux bash, wouldn&#8217;t it be easier to remove spaces from folder and file names, either partially (Music/ogg/Pink Floyd/1975 Wish you were here/01-Shine on you crazy diamond.ogg) or totally (Music/ogg/Pink.Floyd/1975-Wish.you.were.here/01-Shine.on.you.crazy.diamond.ogg)?</p>
<p>* Compilations: I use Picard and like the way it sorts this out. It places all compilations in a Various Artists folder right next to other artists, but then, would you place the artist name in the file name?</p>
<p>There are a few other issues regarding non-Roman script and Windows incompatible characters, also what to do with &#8216;bonus disc&#8217; and &#8216;feature artist&#8217; info in file naming, and what to call cover images and whether they should be embedded into tags or not.</p>
<p>This can be detailed enough to go on an RFC!</p>
]]></content:encoded>
	</item>
</channel>
</rss>
