<?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: The Magic Lamp of Standardization</title>
	<atom:link href="http://blogs.gnome.org/uraeus/2006/12/12/the-magic-lamp-of-standardization/feed/" rel="self" type="application/rss+xml" />
	<link>http://blogs.gnome.org/uraeus/2006/12/12/the-magic-lamp-of-standardization/</link>
	<description>Just another GNOME Blogs weblog</description>
	<lastBuildDate>Wed, 25 Nov 2009 02:40:57 +0000</lastBuildDate>
	<generator>http://wordpress.org/?v=2.8.6</generator>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
		<item>
		<title>By: AdamW</title>
		<link>http://blogs.gnome.org/uraeus/2006/12/12/the-magic-lamp-of-standardization/comment-page-1/#comment-695</link>
		<dc:creator>AdamW</dc:creator>
		<pubDate>Tue, 30 Nov 1999 00:00:00 +0000</pubDate>
		<guid isPermaLink="false">http://blogs.gnome.org/uraeus/2006/12/12/the-magic-lamp-of-standardization/#comment-695</guid>
		<description>The biggest problem with Linux audio is simply that ALSA is on crack and its developers would not know what user-friendliness was if it came up and smacked them in the face. Their idea of a sensible development process is to either a) rename all the channels for a given card or b) leave the names the same but reverse the functions of them, for every card, every second ALSA release. And then not tell anyone about it.&lt;p/&gt;As for trying to have some kind of standardization for the names and functions of channels across different cards...forget about it.&lt;p/&gt;Technically speaking, ALSA&#039;s a great project. From the point of view of any poor sod user who actually has to do something to make it work, it&#039;s a freaking nightmare.&lt;p/&gt;Personally I reckon if this problem was solved, a lot of the others would suddenly get fixed too.</description>
		<content:encoded><![CDATA[<p>The biggest problem with Linux audio is simply that ALSA is on crack and its developers would not know what user-friendliness was if it came up and smacked them in the face. Their idea of a sensible development process is to either a) rename all the channels for a given card or b) leave the names the same but reverse the functions of them, for every card, every second ALSA release. And then not tell anyone about it.
<p />As for trying to have some kind of standardization for the names and functions of channels across different cards&#8230;forget about it.
<p />Technically speaking, ALSA&#8217;s a great project. From the point of view of any poor sod user who actually has to do something to make it work, it&#8217;s a freaking nightmare.
<p />Personally I reckon if this problem was solved, a lot of the others would suddenly get fixed too.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Robert</title>
		<link>http://blogs.gnome.org/uraeus/2006/12/12/the-magic-lamp-of-standardization/comment-page-1/#comment-696</link>
		<dc:creator>Robert</dc:creator>
		<pubDate>Tue, 30 Nov 1999 00:00:00 +0000</pubDate>
		<guid isPermaLink="false">http://blogs.gnome.org/uraeus/2006/12/12/the-magic-lamp-of-standardization/#comment-696</guid>
		<description>I wouldn&#039;t be so sure about MacOS and &#039;pro audio&#039;. The pd community are always getting migrations from MacOS to linux/jack to get the latencies they need for live performance.</description>
		<content:encoded><![CDATA[<p>I wouldn&#8217;t be so sure about MacOS and &#8216;pro audio&#8217;. The pd community are always getting migrations from MacOS to linux/jack to get the latencies they need for live performance.</p>
]]></content:encoded>
	</item>
</channel>
</rss>
