<?xml version="1.0" encoding="UTF-8"?><!-- generator="wordpress/2.2.3" -->
<rss version="2.0" 
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:dc="http://purl.org/dc/elements/1.1/"
	>
<channel>
	<title>Comments on: multimedia over network I</title>
	<link>http://uucode.com/blog/2008/09/24/multimedia-over-network-i/</link>
	<description>advocating olpa's open source developments</description>
	<pubDate>Sat, 11 Feb 2012 09:00:05 +0000</pubDate>
	<generator>http://wordpress.org/?v=2.2.3</generator>

	<item>
		<title>By: T_X</title>
		<link>http://uucode.com/blog/2008/09/24/multimedia-over-network-i/#comment-15687</link>
		<dc:creator>T_X</dc:creator>
		<pubDate>Mon, 04 Jul 2011 15:11:54 +0000</pubDate>
		<guid>http://uucode.com/blog/2008/09/24/multimedia-over-network-i/#comment-15687</guid>
		<description>Great tutorial, it helped me a lot figuring out how to get it working. And I like that you've done it in these quite small chunks, so that everyone has a chance to test different components.

I've first been trying to use the feature of pulse to also directly receive the rtp stream: load-module module-rtp-recv. However that resulted in annoying tune and speed changes. Looks like cvlc is more mature here, in that being able to synchronize the stream playback better.

And I've actually removed the whole #transcode from cvlc. Works fine here, usually drains about 1.44MBit/s which is no sweat for the gbit-lan here at all.

And to make it even more complicated, I'm using a multicast address, so anyone else who would like to drop in and listen too or play it back over their own speakers can do so. And I'm doing some multicast routing as well (using smcroute in linux), the pc streaming the music is on a different ip subnet than the pc playing the music. Getting the multicast bit was a pain in the a** to get working, but it worked in the end. So I suggest anyone to start with the normal, unicast address stuff first, like you did.</description>
		<content:encoded><![CDATA[<p>Great tutorial, it helped me a lot figuring out how to get it working. And I like that you&#8217;ve done it in these quite small chunks, so that everyone has a chance to test different components.</p>
<p>I&#8217;ve first been trying to use the feature of pulse to also directly receive the rtp stream: load-module module-rtp-recv. However that resulted in annoying tune and speed changes. Looks like cvlc is more mature here, in that being able to synchronize the stream playback better.</p>
<p>And I&#8217;ve actually removed the whole #transcode from cvlc. Works fine here, usually drains about 1.44MBit/s which is no sweat for the gbit-lan here at all.</p>
<p>And to make it even more complicated, I&#8217;m using a multicast address, so anyone else who would like to drop in and listen too or play it back over their own speakers can do so. And I&#8217;m doing some multicast routing as well (using smcroute in linux), the pc streaming the music is on a different ip subnet than the pc playing the music. Getting the multicast bit was a pain in the a** to get working, but it worked in the end. So I suggest anyone to start with the normal, unicast address stuff first, like you did.</p>
]]></content:encoded>
	</item>
</channel>
</rss>

