<?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"
	>
<channel>
	<title>Comments on: Odeo Now Has Audio Segments URL Addressable (Sort of?)</title>
	<atom:link href="http://cogdogblog.com/2006/07/28/odeo-now-has-audio-segments-url-addressable/feed/" rel="self" type="application/rss+xml" />
	<link>http://cogdogblog.com/2006/07/28/odeo-now-has-audio-segments-url-addressable/</link>
	<description>Alan Levine's blog space for barking about instructional technology</description>
	<pubDate>Fri, 29 Aug 2008 03:51:49 +0000</pubDate>
	<generator>http://wordpress.org/?v=2.6.1</generator>
		<item>
		<title>By: Matt Pasiewicz</title>
		<link>http://cogdogblog.com/2006/07/28/odeo-now-has-audio-segments-url-addressable/#comment-8301</link>
		<dc:creator>Matt Pasiewicz</dc:creator>
		<pubDate>Thu, 03 Aug 2006 14:57:13 +0000</pubDate>
		<guid isPermaLink="false">http://cogdogblog.com/2006/07/28/odeo-now-has-audio-segments-url-addressable/#comment-8301</guid>
		<description>Good stuff ... if we can get podzinger-like indexing in odeo then it would be really fun</description>
		<content:encoded><![CDATA[<p>Good stuff &#8230; if we can get podzinger-like indexing in odeo then it would be really fun</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Teemu</title>
		<link>http://cogdogblog.com/2006/07/28/odeo-now-has-audio-segments-url-addressable/#comment-8220</link>
		<dc:creator>Teemu</dc:creator>
		<pubDate>Mon, 31 Jul 2006 12:19:29 +0000</pubDate>
		<guid isPermaLink="false">http://cogdogblog.com/2006/07/28/odeo-now-has-audio-segments-url-addressable/#comment-8220</guid>
		<description>This is really nice. I wonder if there are any plans to agree on a single form of the URL? 

This is again a great example of how things work out in the web, where standards are rough consensus and working code.</description>
		<content:encoded><![CDATA[<p>This is really nice. I wonder if there are any plans to agree on a single form of the URL? </p>
<p>This is again a great example of how things work out in the web, where standards are rough consensus and working code.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Alan</title>
		<link>http://cogdogblog.com/2006/07/28/odeo-now-has-audio-segments-url-addressable/#comment-8162</link>
		<dc:creator>Alan</dc:creator>
		<pubDate>Sat, 29 Jul 2006 16:59:22 +0000</pubDate>
		<guid isPermaLink="false">http://cogdogblog.com/2006/07/28/odeo-now-has-audio-segments-url-addressable/#comment-8162</guid>
		<description>Yikes, this was one of the things I posted w/o even trying first (lame excuse, heavy rain was affecting my satellite net connection....)

But I just tried it this morning, and here is what happened:
* Odeo loads with a progress bar that is about 1/3 the way out in the audio, looking about where out of a 38 minute clip, 8:05 would start (but the counter on the right, black is at 0:00
* I clicked play, and it spent about 40-70 seconds "buffering" and then started playing at the 8:05 mark.

So my guess is the way it works is it still must fetch the entire audio, and must buffer its way through the media to hit the right start point. It is now really just fetching the clip I asked for, just a shorthand for doing, "Get the whole audio, but start playing it 1/3 the way in..."

Thanks for actually testing it! Would be worth a comment to the Evhead blog...</description>
		<content:encoded><![CDATA[<p>Yikes, this was one of the things I posted w/o even trying first (lame excuse, heavy rain was affecting my satellite net connection&#8230;.)</p>
<p>But I just tried it this morning, and here is what happened:<br />
* Odeo loads with a progress bar that is about 1/3 the way out in the audio, looking about where out of a 38 minute clip, 8:05 would start (but the counter on the right, black is at 0:00<br />
* I clicked play, and it spent about 40-70 seconds &#8220;buffering&#8221; and then started playing at the 8:05 mark.</p>
<p>So my guess is the way it works is it still must fetch the entire audio, and must buffer its way through the media to hit the right start point. It is now really just fetching the clip I asked for, just a shorthand for doing, &#8220;Get the whole audio, but start playing it 1/3 the way in&#8230;&#8221;</p>
<p>Thanks for actually testing it! Would be worth a comment to the Evhead blog&#8230;</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Tim Lauer</title>
		<link>http://cogdogblog.com/2006/07/28/odeo-now-has-audio-segments-url-addressable/#comment-8153</link>
		<dc:creator>Tim Lauer</dc:creator>
		<pubDate>Sat, 29 Jul 2006 07:35:07 +0000</pubDate>
		<guid isPermaLink="false">http://cogdogblog.com/2006/07/28/odeo-now-has-audio-segments-url-addressable/#comment-8153</guid>
		<description>Hi Alan, looks great, but I can't seem to make it work. I follow the link and it still loads at the beginning of the podcast. Any idea what I am doing wrong?
Thanks,
tim</description>
		<content:encoded><![CDATA[<p>Hi Alan, looks great, but I can&#8217;t seem to make it work. I follow the link and it still loads at the beginning of the podcast. Any idea what I am doing wrong?<br />
Thanks,<br />
tim</p>
]]></content:encoded>
	</item>
</channel>
</rss>
