<?xml version="1.0"?>
<?xml-stylesheet type="text/css" href="http://wiki.xiph.org/skins/common/feed.css?272"?>
<feed xmlns="http://www.w3.org/2005/Atom" xml:lang="en">
		<id>http://wiki.xiph.org/index.php?title=Sydney&amp;feed=atom&amp;action=history</id>
		<title>Sydney - Revision history</title>
		<link rel="self" type="application/atom+xml" href="http://wiki.xiph.org/index.php?title=Sydney&amp;feed=atom&amp;action=history"/>
		<link rel="alternate" type="text/html" href="http://wiki.xiph.org/index.php?title=Sydney&amp;action=history"/>
		<updated>2013-05-26T05:39:24Z</updated>
		<subtitle>Revision history for this page on the wiki</subtitle>
		<generator>MediaWiki 1.16.1</generator>

	<entry>
		<id>http://wiki.xiph.org/index.php?title=Sydney&amp;diff=9774&amp;oldid=prev</id>
		<title>Conrad: init page</title>
		<link rel="alternate" type="text/html" href="http://wiki.xiph.org/index.php?title=Sydney&amp;diff=9774&amp;oldid=prev"/>
				<updated>2008-12-08T11:41:45Z</updated>
		
		<summary type="html">&lt;p&gt;init page&lt;/p&gt;
&lt;p&gt;&lt;b&gt;New page&lt;/b&gt;&lt;/p&gt;&lt;div&gt;{{draft}}&lt;br /&gt;
&lt;br /&gt;
= Introduction =&lt;br /&gt;
&lt;br /&gt;
The idea of the Sydney audio API is to have a powerful, but easy to use cross-platform API for PCM audio capture and playback. So it would sit right on top of ALSA, pulseaudio, OSS, ... and abstract away all hardware-related complexity (e.g. having to check whether a card supports XYZ on ALSA before using it).&lt;br /&gt;
&lt;br /&gt;
The API was named after the location of&lt;br /&gt;
[http://www.foms-workshop.org/foms2007/pmwiki.php/Main/CommunityGoals FOMS2007], which was held in Sydney, Australia.&lt;br /&gt;
&lt;br /&gt;
= Implementations =&lt;br /&gt;
&lt;br /&gt;
* http://svn.annodex.net/libsydneyaudio/trunk This is a lightweight implementation used by Mozilla Firefox&lt;br /&gt;
* http://git.0pointer.de/repos/libsydney.git/ Lennart Poettering's implementation&lt;br /&gt;
&lt;br /&gt;
There is talk of merging these implementations. Alternatively, they can be considered as drop-in replacements for each&lt;br /&gt;
other depending on platform needs.&lt;/div&gt;</summary>
		<author><name>Conrad</name></author>	</entry>

	</feed>