<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:wfw="http://wellformedweb.org/CommentAPI/"
	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/"
	xmlns:slash="http://purl.org/rss/1.0/modules/slash/"
	>

<channel>
	<title>rullzer &#187; new player</title>
	<atom:link href="http://rullzer.com/blog/tag/new-player/feed/" rel="self" type="application/rss+xml" />
	<link>http://rullzer.com/blog</link>
	<description>an experience beyond</description>
	<lastBuildDate>Sat, 19 Mar 2011 07:59:59 +0000</lastBuildDate>
	<language>en</language>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.1</generator>
		<item>
		<title>Writing a music player demon</title>
		<link>http://rullzer.com/blog/2008/11/12/writing-a-music-player-demon/</link>
		<comments>http://rullzer.com/blog/2008/11/12/writing-a-music-player-demon/#comments</comments>
		<pubDate>Wed, 12 Nov 2008 15:11:12 +0000</pubDate>
		<dc:creator><span property="dc:creator" resource="http://rullzer.com/blog/2008/11/12/writing-a-music-player-demon/">rullzer</span></dc:creator>
				<category><![CDATA[Hardware]]></category>
		<category><![CDATA[Linux]]></category>
		<category><![CDATA[gstreamer]]></category>
		<category><![CDATA[MPD]]></category>
		<category><![CDATA[new player]]></category>
		<category><![CDATA[QtMPC]]></category>

		<guid isPermaLink="false">http://rullzer.com/blog/?p=152</guid>
		<description><![CDATA[Yesterday Sander and I released a new version of QtMPC (0.4.1). However when thinking about some of the features we would like to have in QtMPC we once again got annoyed by the MPD protocol. One of the main issues we had was that it is not event based, or even publish-subscribe. You have to [...]]]></description>
			<content:encoded><![CDATA[<p>Yesterday <a href="http://knopper.tk/">Sander</a> and I released a new version of <a href="http://lowblog.nl/2008/11/11/qtmpc-041-out-now/">QtMPC (0.4.1)</a>. </p>
<p>However when thinking about some of the features we would like to have in QtMPC we once again got annoyed by the <a href="http://musicpd.org">MPD</a> protocol. One of the main issues we had was that it is not event based, or even publish-subscribe. You have to ask for every little detail you want. This is a choice and it is true that this way you do not get unwanted messages thus generate unwanted network traffic.</p>
<p>But we feel that some sort of event based protocol will do a better job here. Lets say in the default nothing is send as well. That way mobile clients can still control the player without receiving anything unwanted. Or just subscribe to events related to playback. This way mobile clients are still supported but again. They do not have to request the status ever <strong>x</strong> seconds. They just get a message once had changed.</p>
<p>For full blown clients event bases is also a positive thing. For example the reaction time. When adding a new song. Right now this has to be noted by the client when requesting the version of the playlist. A simple message from the server saying <strong>playlist current newsong &#8230;&#8230;..</strong> (or something like that) could be send right after the song is actually added. It just makes things easier.</p>
<p>Another thing that kind of bother us that there was no inotify support. This would be great however. Lets say you have a music server running on your server. And add some new music to the collection. It would be best of course if it would find the new music. Add it to the database and notify the clients of a change in the music library.</p>
<p>Now we have not written any code yet. But we are thinking about it. For the music playback part we are planing to use gstreamer. Since well it already supports a lot of audio formats. And why reinvent the wheel right?</p>
]]></content:encoded>
			<wfw:commentRss>http://rullzer.com/blog/2008/11/12/writing-a-music-player-demon/feed/</wfw:commentRss>
		<slash:comments>19</slash:comments>
		</item>
	</channel>
</rss>

