<?xml version="1.0"?>
<rss version="2.0" xmlns:dc="http://purl.org/dc/elements/1.1/">
<channel>
<title>Engadget HD - Comments for Some XStreamHD details emerge, some still fuzzy</title>
<link>http://www.engadgethd.com/2007/12/13/some-xstreamhd-details-emerge-some-still-fuzzy/</link>
<description>Engadget HD Comments for Some XStreamHD details emerge, some still fuzzy</description>
<image>
<url>http://www.engadgethd.com/media/feedlogo.gif</url>
<title>Engadget HD</title>
<link>http://www.engadgethd.com</link>
</image>
<language>en-us</language>
<copyright>Copyright 2008 Weblogs, Inc. The contents of this feed are available for non-commercial use only.</copyright>
<generator>Blogsmith http://www.blogsmith.com/</generator><item><title><![CDATA[Comments on Some XStreamHD details emerge, some still fuzzy]]></title><link>http://www.engadgethd.com/2007/12/13/some-xstreamhd-details-emerge-some-still-fuzzy/</link><guid isPermaLink="true">http://www.engadgethd.com/2007/12/13/some-xstreamhd-details-emerge-some-still-fuzzy/</guid><description><![CDATA[Come on guys, how about some simple research. XStreamHD engineering management are ex-HNS and iDirect. Job openings call for FEC code, prepackaging content at the headend, RTP/RTSP experience, and satellite modem integration. <br><br>Obviously they are going to use a trickle delivery mechanism to get content onto the box, and local LAN RTP/RTSP streaming to ancillary STBs from the central receiver. <br><br>No-one at the consumer level pulls content using sat modems, there just isn't a business case for implementing turbo internet anymore. <br><br>Good god if you're going to post news at least read up on the technology you're dealing with. NACK implosion wrt network scalability for consumer rollouts is fundamental knowledge when it comes to data delivery over satellite.<br><br>Interesting that they are reinventing the wheel for so many pieces of their puzzle. I would venture to say rather stupid, as well, given the failure rate of systems doing this in the past (Moviebeam, Cyberstar, iBlast, Geocast, ...).]]></description><dc:creator><![CDATA[Kon]]></dc:creator><pubDate>Dec 13th 2007 4:10PM</pubDate></item><item><title><![CDATA[Comments on Some XStreamHD details emerge, some still fuzzy]]></title><link>http://www.engadgethd.com/2007/12/13/some-xstreamhd-details-emerge-some-still-fuzzy/</link><guid isPermaLink="true">http://www.engadgethd.com/2007/12/13/some-xstreamhd-details-emerge-some-still-fuzzy/</guid><description><![CDATA[I expect them to use pre-loaded content, since, as you say, the scalability of on-demand via satellite is questionable.  But some of the comments seem odd in that case, such as being able to start watching 'within 5 minutes'.  Why is there any delay if the content is all local?  It certainly wouldn't take 5 minutes to stream from the server to the client.  Is there a delay for authorization?  If so, why so long?<br><br>Still, I suspect it is main a context issue and it is going to work very much like Moviebeam - or DirecTV and DISH Networks 'On Demand' offerings for that matter.  Content will be pre-loaded onto the server in the home, and users will only be able to select from that small library of 'current' titles.  Perhaps there will be an ability to pre-select what is loaded, so you can tell it which upcoming titles you wish to be able to view.]]></description><dc:creator><![CDATA[MegaZone]]></dc:creator><pubDate>Dec 13th 2007 4:14PM</pubDate></item><item><title><![CDATA[Comments on Some XStreamHD details emerge, some still fuzzy]]></title><link>http://www.engadgethd.com/2007/12/13/some-xstreamhd-details-emerge-some-still-fuzzy/</link><guid isPermaLink="true">http://www.engadgethd.com/2007/12/13/some-xstreamhd-details-emerge-some-still-fuzzy/</guid><description><![CDATA[I suspect their '5 minutes' comment is marketing drone speak for 'I don't really understand how this technology  works'. <br><br>One instance where that would make sense would be in the case of a higher-bitrate data carousel carrying say the top 5 movies chunked up to facilitate 'instant on'. The carousel iterations may require a minimum of 5 minutes at datarate x for the box to aquire enough data chunks to start playback without fear of hitting a buffer underrun. My experience in this has been that this concept is a pipedream.<br><br>The other possibility is that they continuously trickle content to the box and send metadata announcements in an ancillary channel that has a announce time of 5 minutes. The maximum lead time from receiving the entire file to the first decode of new metadata would then be 5 minutes.<br><br>Pre-selecting items from a carousel is novel yet not original. The advantage is that the user can manage content. The disadvantage is that the lead time to obtain item B when eliminating item A is not decreased. Best to give them the illusion of queue management by simply hiding what they see on the OSD, and not what is on the drive (so when they change their minds, that 'old' content is suddenly instantly available).<br><br>This box is just another Moviebeam push device. Too late to market and doomed to failure -- unless they plan to implement broadband on the box from the get-go to dynamically populate the box using sat for popular content and broadband for user-NVOD.]]></description><dc:creator><![CDATA[Kon]]></dc:creator><pubDate>Dec 13th 2007 4:31PM</pubDate></item></channel></rss>