<?xml version="1.0"?>
<rss version="2.0" xmlns:dc="http://purl.org/dc/elements/1.1/">
<channel>
<title>Engadget HD - Comments for Comcast Media Center gets creative with compression</title>
<link>http://hd.engadget.com/2007/12/14/comcast-media-center-gets-creative-with-compression/</link>
<description>Engadget HD Comments for Comcast Media Center gets creative with compression</description>
<image>
<url>http://hd.engadget.com/media/feedlogo.gif</url>
<title>Engadget HD</title>
<link>http://hd.engadget.com</link>
</image>
<language>en-us</language>
<copyright>Copyright 2009 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 Comcast Media Center gets creative with compression]]></title><link>http://hd.engadget.com/2007/12/14/comcast-media-center-gets-creative-with-compression/</link><guid isPermaLink="true">http://hd.engadget.com/2007/12/14/comcast-media-center-gets-creative-with-compression/</guid><description><![CDATA[This article is a little inaccurate. Three HD channels (when properly placed) can be placed on single QAM256 carrier at 39 mbps.  No HD channel runs at a full 19 mbps constantly...the bit rate is dependent on the type of programming being ran (example CNNHD will use less bandwidth than a CBS football broadcast) or if it is 720p or 1080i (720p tends to max out at 15 mbps).  So if you are careful on where you place things, you can statistical mutiplex 3 HD channels together and not take a hit in picture quality.  Now there are cases either due to a.) bad planning or b.) an unusually high bit-rate on all the stat mux'ed channels that you could run out of bandwidth.  The problem with a stat mux is that it will start to drop bits on the floor which rapidly degrades picture quality. the one advantage of this "2nd look MPEG2 encoder" is that it may be a bit more graceful in these conditions.  Maybe it even has a way of prioritizing what channels get "recompressed" first.  Maybe recompress CNNHD before NFL Network?  Definitely interesting that you can do that pretty much in real-time now. ]]></description><dc:creator><![CDATA[Jim Mallory]]></dc:creator><pubDate>Dec 14th 2007 11:20AM</pubDate></item><item><title><![CDATA[Comments on Comcast Media Center gets creative with compression]]></title><link>http://hd.engadget.com/2007/12/14/comcast-media-center-gets-creative-with-compression/</link><guid isPermaLink="true">http://hd.engadget.com/2007/12/14/comcast-media-center-gets-creative-with-compression/</guid><description><![CDATA[It would be nice if someone at Imagine Communications can explain how this 2nd look MPEG2 encoder works. I dont think they'll cram channels like CBS, Fox, ESPN, etc on that type of bandwidth. Maybe channels like DiscoveryHD, TBSHD, NatGeoHD, etc will be better suited for this like you've stated in your comment.]]></description><dc:creator><![CDATA[Diceburna]]></dc:creator><pubDate>Dec 14th 2007 1:05PM</pubDate></item><item><title><![CDATA[Comments on Comcast Media Center gets creative with compression]]></title><link>http://hd.engadget.com/2007/12/14/comcast-media-center-gets-creative-with-compression/</link><guid isPermaLink="true">http://hd.engadget.com/2007/12/14/comcast-media-center-gets-creative-with-compression/</guid><description><![CDATA[Bright House Networks in Michigan does this 3:1 compression on a few HD channels.  The non-technical response to Jim Mallory, is that this compression looks bad.<br><br>I noticed poor picture quality on a few stations, and found out these channels were being over-compressed.  Let's not kid ourselves, compression is compression.  ANY compression will produce artifacting, even a 25mb/s signal (although this would look quite good).  Compressing HD channels down to ~12mb/s from 16mb/s is indeed noticable.<br><br>OTA HD signals look the best, but I'll at least agree to 2:1 with 256 QAM just so it doesn't ever get worse than this.  NO MORE 3:1, PLEASE!!]]></description><dc:creator><![CDATA[looseinthedeuce]]></dc:creator><pubDate>Dec 17th 2007 1:39PM</pubDate></item></channel></rss>