<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
<html>
<head>
<meta content="text/html; charset=ISO-8859-1"
http-equiv="Content-Type">
<title></title>
</head>
<body text="#000000" bgcolor="#ffffff">
On 5/2/2011 13:31, Tom Bongiorno wrote:
<blockquote
cite="mid:BANLkTinAL+9gweQfyYtwnpZ7BHUxjO5G5g@mail.gmail.com"
type="cite">
<div class="gmail_quote">On Mon, May 2, 2011 at 12:58 PM, Ronald
Frazier <span dir="ltr"><<a moz-do-not-send="true"
href="mailto:ron@ronfrazier.net" target="_blank">ron@ronfrazier.net</a>></span>
wrote:<br>
<blockquote class="gmail_quote" style="margin: 0pt 0pt 0pt
0.8ex; border-left: 1px solid rgb(204, 204, 204);
padding-left: 1ex;">
<div>On Mon, May 2, 2011 at 12:41 PM, Raymond Wagner <<a
moz-do-not-send="true" href="mailto:raymond@wagnerrp.com"
target="_blank">raymond@wagnerrp.com</a>> wrote:<br>
> These copy protection flags are the same ones that
restrict users<br>
> presently recording shows over firewire.<br>
<br>
</div>
I don't believe that is correct. I am pretty sure that
Firewire's<br>
Digital Transmission Content Protection and Cablecard's Copy
Control<br>
Information schemes are separate schemes that don't
necessarily match<br>
up. If you have a cablecard-based cable box, then it could
possibly<br>
generate the firewire setup based on what cablecard CCI flags
are set<br>
(not sure if that would depend on the cable company's
implementation,<br>
or the way the cable box is designed). However, I don't think
that is<br>
guaranteed to be true. My understanding is that it is possible
to have<br>
firewire restricted while cablecard is copy-freely, or vice
versa. How<br>
often that happens, I have no idea.<font color="#888888"><br>
</font></blockquote>
</div>
<br>
<div>I think that 5C, CCI, and DTCP are all the same thing. They
all apply to Firewire and CableCard. The confusion may arise
from the fact that multiple acronyms are used to refer to the
same thing and it was originally only in place for Firewire.<br>
</div>
</blockquote>
<br>
They are all the same flags. The confusion arises from the fact
that firewire can be used to positively indicate a channel will be
available, but not to negatively indicate a channel will not be
available. Since the copy freely content is uncontrolled, there is
no specification on how a 5C device should behave with such
material. Some cable box firmwares will still require the 5C
handshake that MythTV is incapable of performing, resulting in a
copy-freely show being unrecordable.<br>
</body>
</html>