<div dir="ltr"><div class="gmail_extra"><div class="gmail_quote">On Tue, Nov 4, 2014 at 1:09 PM, Steven Adeff <span dir="ltr"><<a href="mailto:adeffs.mythtv@gmail.com" target="_blank">adeffs.mythtv@gmail.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div class="HOEnZb"><div class="h5">On Mon, Nov 3, 2014 at 11:42 AM, Ronald Frazier <<a href="mailto:ron@ronfrazier.net">ron@ronfrazier.net</a>> wrote:<br>
> Oops...premature post via keyboard shortcut on that last message :-(<br>
><br>
> Anyway, I'll add an additional thought to this (regarding the prime...I<br>
> don;t know much about firewire DRM). Cable companies usually don't flip CCI<br>
> flags on individual programs. They usually do it per channel and it never<br>
> changes unless someone goes in and reconfigures. So most likely the DRM is<br>
> coming from the analog CGMS flags. The fact that the CGMS flag comes into<br>
> play means one of two things<br>
><br>
> 1) Comcast has not applied any CCI flags to that channel, so you are victim<br>
> to whatever CGMS flags are applied by the broadcaster of that station (or<br>
> possibly even flags from the source content itself). The solution to this is<br>
> to ask Comcast to fix it (Comcast is generally cooperative with this once<br>
> you get in touch with the right person). If it were currently mid 2013, this<br>
> would (I think) be the only explanation for this situation, however....<br>
><br>
> 2) There has been a new development in the last year or so. The cablecard<br>
> specification was changed by CableLabs, and Cisco has implemented this<br>
> change in their latest firmware (my cable company rolled it out a few months<br>
> ago, but I think I saw a few Comcast people posting about it last December).<br>
> Previous to this change, a CCI flag of "Copy Freely" (or any CCI flag, for<br>
> that matter) would override any CGMS flag (even if the CGMS was more<br>
> restrictive). This new specification says that, when a channel is marked<br>
> "Copy Freely", the cablecard can (or must??? im not clear on that part)<br>
> report that there are no CCI flags at all. So whereas previously, CGMS only<br>
> mattered if there were no CCI flags, now it also matters if the CCI flag is<br>
> "Copy Freely". With this change, the only 2 conditions under which mythtv<br>
> can record are both hampered by CGMS flags when present.<br>
><br>
> This last situation has been discussed in a few other threads. The current<br>
> solutions are<br>
><br>
> 1) If your HDHR prime is running firmware older than the 20140604 vesion,<br>
> then upgrade it to that version (it has a bug that disregards the CGMS<br>
> flags). However, DO NOT upgrade it...EVER...to any version newer than<br>
> 20140604, because once you do, that bug has been fixed, you will be subject<br>
> to CGMS flags, and you will NOT be able to downgrade back to 20140604 EVER.<br>
><br>
> 2) If you've already upgraded past 20140604, you could try to find another<br>
> device that isn't. Not sure what version new models are currently running<br>
> off the shelf. You could also try to get a used one off ebay (ask the seller<br>
> before bidding)<br>
><br>
> 3) With my cable provider (WOW) they can set a flag on their system that<br>
> will lock your cablecard firmware to a version before this new specification<br>
> change was implemented. You can see if comcast will do the same thing for<br>
> you. Then (assuming your comcast flags it as CCI: Copy Freely) you should be<br>
> set...at least for as long as you can stay on that firmware. My cable<br>
> company said it should not be a problem long term, as they rarely upgrade<br>
> firmware, and that last version had been in use for a few years, so they<br>
> probably aren't likely to implement anything soon that would break the old<br>
> firmware and force me to upgrade. If they ever do, then you are currently<br>
> stuck with options 1 or 2. I've got a HDHR Prime running 20140604 which I<br>
> don't use, but which I am holding onto for that exact reason...just in case.<br>
<br>
</div></div>Ron,<br>
any idea about how Ceton handles this? or are Ceton users not in luck<br>
with a "buggy firmware" type situation?<br></blockquote><div><br></div><div><br></div><div>The ceton does NOT have an equivalent "buggy firmware" workaround. In fact, thats the whole reason I did buy a HDHR prime. After dealing with the issue for a whole month (and many many failed recordings), and nobody being able to figure a way to deal with it, I gave in and bought a used prime off ebay. A few weeks later, my cable company finally figured out they can lock the cablecard firmware version (to a version that does report the CCI: Copy Freely flag), so I switched back to the ceton.</div><div><br></div><div>In my emails with ceton, as I recall, they did say they had requested to be able to ignore CGMS at one point in the past and were shot down, but with the latest changes they were in processing of updating and resubmitting the request to cable labs. I don't have much confidence cablelabs would actually agree with any sort of change like that unless they had someone big like comcast or microsoft pushing on them about it.</div></div><div><br></div>-- <br><div class="gmail_signature">Ron Frazier</div>
</div></div>