No subject

the STB to turn off any outputs that don't have content protection (like the
component outputs).  It sounds to me like the implication is that the
general STB probably already has SOC implemented, but that the FCC does not
allow it to be used.  What the studios want to do is get an exception to
turn on SOC for first-run movies.  Of course once they get that foot in the
door...

-Jerry

------=_Part_15323_28119446.1213024314282
Content-Type: text/html; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
Content-Disposition: inline

On Mon, Jun 9, 2008 at 10:52 AM, John Drescher &lt;<a href="mailto:drescherjm at gmail.com">drescherjm at gmail.com</a>&gt; wrote:<br><div class="gmail_quote"><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
<div class="Ih2E3d">&gt; I wonder what the effect of something like this would be on recent devices like HD-PVR that exploit the<br>
&gt; analog hole. &nbsp;I would assume the HD-PVR would pass on any stream unmodified, thus any copy control<br>
&gt; encoded into the stream would remain intact.<br>
&gt;<br>
</div>There is no such copy control in the analog stream. Only digital streams.<br>
<font color="#888888"></font></blockquote><div><br>From TFA, it sounds like what SOC does is enable the digital stream to tell the STB to turn off any  outputs that don&#39;t have content protection (like the component outputs).&nbsp; It sounds to me like the implication is that the general STB probably already has SOC implemented, but that the FCC does not allow it to be used.&nbsp; What the studios want to do is get an exception to turn on SOC for first-run movies.&nbsp; Of course once they get that foot in the door...<br>
<br>-Jerry<br></div></div>

------=_Part_15323_28119446.1213024314282--