<html>
<head>
<meta content="text/html; charset=windows-1252"
http-equiv="Content-Type">
</head>
<body bgcolor="#FFFFFF" text="#000000">
<div class="moz-cite-prefix">On 01/14/2015 03:32 PM, Ronald Frazier
wrote:<br>
</div>
<blockquote
cite="mid:CADvQU8BdbHtFyvLsQ41sSmj5ds6XEzeAGq80phcdVLWEpf-s3A@mail.gmail.com"
type="cite">
<div dir="ltr">
<div class="gmail_extra">
<div class="gmail_quote">On Wed, Jan 14, 2015 at 12:31 AM,
Gary Buhrmaster <span dir="ltr"><<a
moz-do-not-send="true"
href="mailto:gary.buhrmaster@gmail.com" target="_blank">gary.buhrmaster@gmail.com</a>></span>
wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0
.8ex;border-left:1px #ccc solid;padding-left:1ex"><span
class=""><br>
</span>Ceton is reporting that their request to remove
legacy<br>
copy protection has been approved by CableLabs<br>
</blockquote>
<div><br>
</div>
<div>Holy crap. Good thing I'm not a betting man, because I
would have put good money against that one. While it is a
welcome change, from their perspective that seems entirely
contrary to the entire point of changing it to not pass
along the CCI 0x00 flag.</div>
<div><br>
</div>
<div>On the plus side (for us), I think this fixes the
problem when a cable provider didn't add any CCI flags at
all, which causes CGMS to kick in. Previously they could
only ignore CGMS when CCI was present, but since they can
now no longer tell that it is present or not, CGMS should
be ignored in all cases.</div>
</div>
</div>
</div>
<br>
<fieldset class="mimeAttachmentHeader"></fieldset>
<br>
</blockquote>
<br>
It looks like from the document that they don't need to honor the
CGMS for clear QAM any more either. This brings Ceton and Homerun
Prime in line with the tuner sticks for those few people who still
have clear QAM on the cable system.<br>
<br>
Most amazing is how fast it was approved and even more amazing is
how fast the firmware was released<br>
From the time stamps on the web sites:<br>
Update to Cable Labs Spec: Tue, 13 Jan 2015 19:54:58 GMT<br>
Firmware upgrade: Tue, 13 Jan 2015 23:08:47 GMT<br>
3 hours to code, test, package and release a firmware upgrade!<br>
I wonder how well they tested it.<br>
Hopefully they had already been working on it and had it ready for
when the approval came.<br>
<br>
Peter<br>
</body>
</html>