<?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 for The adventures of Foo</title>
	<atom:link href="http://jensge.org/comments/feed/" rel="self" type="application/rss+xml" />
	<link>http://jensge.org</link>
	<description>My aggregated random tech blabber</description>
	<lastBuildDate>Thu, 17 May 2012 18:19:49 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.3.2</generator>
	<item>
		<title>Comment on N9 media pushing by Jed</title>
		<link>http://jensge.org/2012/04/n9-media-pushing/comment-page-1/#comment-8271</link>
		<dc:creator>Jed</dc:creator>
		<pubDate>Thu, 17 May 2012 18:19:49 +0000</pubDate>
		<guid isPermaLink="false">http://jensge.org/?p=643#comment-8271</guid>
		<description>And it looks like apps4meego has a slightly more recent version of PushUp than what&#039;s linked to in this post.</description>
		<content:encoded><![CDATA[<p>And it looks like apps4meego has a slightly more recent version of PushUp than what&#8217;s linked to in this post.</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on N9 media pushing by Jed</title>
		<link>http://jensge.org/2012/04/n9-media-pushing/comment-page-1/#comment-8270</link>
		<dc:creator>Jed</dc:creator>
		<pubDate>Thu, 17 May 2012 18:17:48 +0000</pubDate>
		<guid isPermaLink="false">http://jensge.org/?p=643#comment-8270</guid>
		<description>For those that don&#039;t want to wait this can also be obtained using the apps4meego client.
It&#039;s likely to be what ends up in the Nokia Store ultimately anyway....</description>
		<content:encoded><![CDATA[<p>For those that don&#8217;t want to wait this can also be obtained using the apps4meego client.<br />
It&#8217;s likely to be what ends up in the Nokia Store ultimately anyway&#8230;.</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on N9 media pushing by Jens</title>
		<link>http://jensge.org/2012/04/n9-media-pushing/comment-page-1/#comment-8269</link>
		<dc:creator>Jens</dc:creator>
		<pubDate>Thu, 17 May 2012 09:32:06 +0000</pubDate>
		<guid isPermaLink="false">http://jensge.org/?p=643#comment-8269</guid>
		<description>@Thomas: The WD TV Live doesn&#039;t work with any control point. I always get error 718 for Stop and the flickering behaviour for Pause. With which control point does it work for you? Which WDTV Live do you have? The grey, roundish one or the black shiny one? And with which firmware version?</description>
		<content:encoded><![CDATA[<p>@Thomas: The WD TV Live doesn&#8217;t work with any control point. I always get error 718 for Stop and the flickering behaviour for Pause. With which control point does it work for you? Which WDTV Live do you have? The grey, roundish one or the black shiny one? And with which firmware version?</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on N9 media pushing by Jed</title>
		<link>http://jensge.org/2012/04/n9-media-pushing/comment-page-1/#comment-8268</link>
		<dc:creator>Jed</dc:creator>
		<pubDate>Thu, 17 May 2012 08:30:48 +0000</pubDate>
		<guid isPermaLink="false">http://jensge.org/?p=643#comment-8268</guid>
		<description>This just gets better &amp; better, thanks for your work Jens!</description>
		<content:encoded><![CDATA[<p>This just gets better &amp; better, thanks for your work Jens!</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on N9 media pushing by Thomas W</title>
		<link>http://jensge.org/2012/04/n9-media-pushing/comment-page-1/#comment-8266</link>
		<dc:creator>Thomas W</dc:creator>
		<pubDate>Tue, 15 May 2012 14:06:26 +0000</pubDate>
		<guid isPermaLink="false">http://jensge.org/?p=643#comment-8266</guid>
		<description>Will debug the communication between N9 and that radio next week. Good to know some more internals as it helps to narrow down this problem. Could be also the radios problem...

@WD TV Live: Which issue do you mean. The repeated playback after stopping or the slow position skipping (meant 15 sec not min by the way). With other software control points this prepeated playback does not appear with my WD TV Live.</description>
		<content:encoded><![CDATA[<p>Will debug the communication between N9 and that radio next week. Good to know some more internals as it helps to narrow down this problem. Could be also the radios problem&#8230;</p>
<p>@WD TV Live: Which issue do you mean. The repeated playback after stopping or the slow position skipping (meant 15 sec not min by the way). With other software control points this prepeated playback does not appear with my WD TV Live.</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on N9 media pushing by Jens</title>
		<link>http://jensge.org/2012/04/n9-media-pushing/comment-page-1/#comment-8265</link>
		<dc:creator>Jens</dc:creator>
		<pubDate>Tue, 15 May 2012 12:52:00 +0000</pubDate>
		<guid isPermaLink="false">http://jensge.org/?p=643#comment-8265</guid>
		<description>PushUp is brings its own (HTTP) server to serve the media. It does not use the DLNA server on the N9 in any way. And your imagination is correct, you more or less just provide an URI to the device and tell it to start playing. The UPnP calls are exactly the same. Just that in the Helium case the meta-data and the URI come from another UPnP server while with PushUp the meta-data is retrieved from the Tracker DB and the file is served from its own HTTP server. One thing the N9 DLNA server and PushUp share is the underlying library to implement the HTTP server (which is quite old on the N9). Maybe something is going wrong in there.

I know that issue with the WDTV Live, I have that device myself. I don&#039;t really understand it. It seems that it doesn&#039;t really like to be remote controlled.</description>
		<content:encoded><![CDATA[<p>PushUp is brings its own (HTTP) server to serve the media. It does not use the DLNA server on the N9 in any way. And your imagination is correct, you more or less just provide an URI to the device and tell it to start playing. The UPnP calls are exactly the same. Just that in the Helium case the meta-data and the URI come from another UPnP server while with PushUp the meta-data is retrieved from the Tracker DB and the file is served from its own HTTP server. One thing the N9 DLNA server and PushUp share is the underlying library to implement the HTTP server (which is quite old on the N9). Maybe something is going wrong in there.</p>
<p>I know that issue with the WDTV Live, I have that device myself. I don&#8217;t really understand it. It seems that it doesn&#8217;t really like to be remote controlled.</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on N9 media pushing by Thomas W</title>
		<link>http://jensge.org/2012/04/n9-media-pushing/comment-page-1/#comment-8264</link>
		<dc:creator>Thomas W</dc:creator>
		<pubDate>Tue, 15 May 2012 12:39:45 +0000</pubDate>
		<guid isPermaLink="false">http://jensge.org/?p=643#comment-8264</guid>
		<description>I could see that PushUp or Helium provided the Sagem Radio with a URL (from where it can stream the media). If this URL points to my N9 DLNA server it doesn&#039;t work. If it&#039;s another DLNA server URL it works, so the problem must appear when the Radio trys to consume the media URL.

What are the (technical) DLNA similarities when streaming Media from N9 DLNA Server via Helium to Radio and when using PushUp? In my imagination the Radio is provided with a link to a media resource (on my N9) from where it should start streaming, or? In that case I guess it&#039;s simply a problem of the N9 DLNA Server...

Also, Helium &amp; PushUp work nicely with WD TV Live but I also experienced some problems with Movies starting again and again even after stopping their playback on (Helium). Other issues are skipping the movie is sometimes supported but often needs 15 min to react to jump at the given position.</description>
		<content:encoded><![CDATA[<p>I could see that PushUp or Helium provided the Sagem Radio with a URL (from where it can stream the media). If this URL points to my N9 DLNA server it doesn&#8217;t work. If it&#8217;s another DLNA server URL it works, so the problem must appear when the Radio trys to consume the media URL.</p>
<p>What are the (technical) DLNA similarities when streaming Media from N9 DLNA Server via Helium to Radio and when using PushUp? In my imagination the Radio is provided with a link to a media resource (on my N9) from where it should start streaming, or? In that case I guess it&#8217;s simply a problem of the N9 DLNA Server&#8230;</p>
<p>Also, Helium &amp; PushUp work nicely with WD TV Live but I also experienced some problems with Movies starting again and again even after stopping their playback on (Helium). Other issues are skipping the movie is sometimes supported but often needs 15 min to react to jump at the given position.</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on N9 media pushing by Jens</title>
		<link>http://jensge.org/2012/04/n9-media-pushing/comment-page-1/#comment-8263</link>
		<dc:creator>Jens</dc:creator>
		<pubDate>Tue, 15 May 2012 11:50:39 +0000</pubDate>
		<guid isPermaLink="false">http://jensge.org/?p=643#comment-8263</guid>
		<description>PushUp doesn&#039;t use Rygel so something else is going wrong there.</description>
		<content:encoded><![CDATA[<p>PushUp doesn&#8217;t use Rygel so something else is going wrong there.</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on N9 media pushing by Thomas W</title>
		<link>http://jensge.org/2012/04/n9-media-pushing/comment-page-1/#comment-8262</link>
		<dc:creator>Thomas W</dc:creator>
		<pubDate>Tue, 15 May 2012 09:41:48 +0000</pubDate>
		<guid isPermaLink="false">http://jensge.org/?p=643#comment-8262</guid>
		<description>Forgot to mention that I&#039;m using PushUp 0.2.1-1</description>
		<content:encoded><![CDATA[<p>Forgot to mention that I&#8217;m using PushUp 0.2.1-1</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on N9 media pushing by Thomas W</title>
		<link>http://jensge.org/2012/04/n9-media-pushing/comment-page-1/#comment-8261</link>
		<dc:creator>Thomas W</dc:creator>
		<pubDate>Tue, 15 May 2012 09:40:57 +0000</pubDate>
		<guid isPermaLink="false">http://jensge.org/?p=643#comment-8261</guid>
		<description>Hi Jens,

was playing yesterday a bit with sniffing packets but I have general issues with several separated networks (LAN, WLAN) at home (Always a pain when trying DLNA related stuff). So I haven&#039;t been successful yet with testing rygel but will try next week.

It would be really cool to have such a debugger in your beta versions (Helium, PushUp), so all you need to do is save DLNA communication in a log file.

Meanwhile I made more tests with my devices. It seems not to be the problem of PushUp, because also Helium can&#039;t play songs (from N9) to that radio. If I select another DLNA Media server everything works fine, so indeed it seems to be rygel related. Will provide you with details next week.</description>
		<content:encoded><![CDATA[<p>Hi Jens,</p>
<p>was playing yesterday a bit with sniffing packets but I have general issues with several separated networks (LAN, WLAN) at home (Always a pain when trying DLNA related stuff). So I haven&#8217;t been successful yet with testing rygel but will try next week.</p>
<p>It would be really cool to have such a debugger in your beta versions (Helium, PushUp), so all you need to do is save DLNA communication in a log file.</p>
<p>Meanwhile I made more tests with my devices. It seems not to be the problem of PushUp, because also Helium can&#8217;t play songs (from N9) to that radio. If I select another DLNA Media server everything works fine, so indeed it seems to be rygel related. Will provide you with details next week.</p>
]]></content:encoded>
	</item>
</channel>
</rss>

