Text 15562, 348 rader
Skriven 2007-01-21 20:24:10 av Rich (1:379/45)
Kommentar till text 15556 av Geo. (1:379/45)
Ärende: Re: Content protection
==============================
From: "Rich" <@>
This is a multi-part message in MIME format.
------=_NextPart_000_112D_01C73D9A.1C64BB50
Content-Type: text/plain;
charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
Nope. They will pay someone or someone will step up for money. For =
a very obvious example look at all the content protection schemes in use = not
supported by Windows from CSS for DVDs to apple's DRM for itunes.
Rich
"Geo." <georger@nls.net> wrote in message news:45b42e12@w3.nls.net...
It's not required to play the game. If there is no support from =
software=20
makers for DRM then the content industry has to accept that in order =
to reap=20
the profits from that market. And as everyone knows, some profits are =
better=20
than NO profits..
Geo.
"Rich" <@> wrote in message news:45b40c49@w3.nls.net...
Nonsense. Region coding, encryption (e.g. CSS), expiring content =
(e.g.=20
DivX) are examples that existed without pre-existing support from =
software=20
vendors. These and the other forms of restrictions all exist because =
the=20
content providers require it. Microsoft, Apple, real as well as CE =
vendors=20
(e.g. Pioneer, Creative, Apple) support it only because it is required =
to=20
even play the game. Without it you can only sit on the outside and =
watch.
Rich
"Geo." <georger@nls.net> wrote in message =
news:45b407ba@w3.nls.net...
My point is it is the vendors who enable features like content =
expiration
who are responsible, not the people who requested it, but the people =
like
Microsoft who make it real.
Geo.
"Rich" <@> wrote in message news:45b405a9$1@w3.nls.net...
The implementation in Windows is a framework with a set of =
capabilities
necessary to meet the requirements of not just HD-DVD but other =
content as
well. It is not a hard coded implementation of any specific =
requirements.
This is necessary to allow Windows to be a platform for playback of =
as=20
much
content as possible.
Your example of expiration is something that doesn't apply to =
HD-DVD,=20
or
at least I don't think so but I could be wrong. I'm not at all =
familiar
with what AACS allows. It is something that applies to =
distributable=20
audio
and video content. If you see it used, you should contact the =
content
provider and/or licensor to ask why. FWIW, an expiration date has =
been
supported since version 1.0 or WMDRM released in 1999.
Rich
"Geo." <georger@nls.net> wrote in message =
news:45b3c20f$1@w3.nls.net...
If the content protection in vista goes above and beyond that =
found on
HDDVD
players then can you really claim it was just to support =
protections
mandated by the content? For example if vista allows downloading =
content
that expires after a week, you can't possibly be serious that =
vista=20
isn't
directly responsible for extending the capabilities of HD-DVD =
content
protection.
Geo.
"Rich" <@> wrote in message news:45b2f6e3$1@w3.nls.net...
The extra CPU is to support the protections mandated by the =
content.
The
additional functionality is the ability to render that content at =
all.=20
If
you don't want to play protected content such as HD-DVD or bluray =
then=20
you
should care that increased CPU is required to do so. If you do =
want to
play
such content then you should be pleased that it is possible.
Rich
"Rich Gauszka" <gauszka@dontspamhotmail.com> wrote in message
news:45b2ec71$1@w3.nls.net...
The Vista team is hallucinating equating additional CPU cycles =
used=20
for
drm
with additional functionality for consumers.
from the link
------------------------------------------------------------
Will Windows Vista content protection features increase CPU =
resource
consumption?
Yes. However, the use of additional CPU cycles is inevitable, =
as the=20
PC
provides consumers with additional functionality.
-------------------------------------------------------------
"John Beamish" <JLBeamish@rogers.com> wrote in message
=
news:op.tmhkksu1m6tn4t@dellblack.wlfdle.phub.net.cable.rogers.com...
> In this vein ... there was the story that Vista imposed DRM in =
such=20
a
> manner that if (for example) you were listening to a CD that =
was
subject
> to DRM and you were a technician viewing (according to this =
example)=20
a
> digital x-ray that the x-ray would be degraded to the same =
extent=20
that
DRM
> required the CD to be degraded.
>
> The Windows Vista team replied here:
>
=
http://windowsvistablog.com/blogs/windowsvista/archive/2007/01/20/windows=
-vista-content-protection-twenty-questions-and-answers.aspx
------=_NextPart_000_112D_01C73D9A.1C64BB50
Content-Type: text/html;
charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<HTML><HEAD>
<META http-equiv=3DContent-Type content=3D"text/html; =
charset=3Diso-8859-1">
<META content=3D"MSHTML 6.00.6000.16386" name=3DGENERATOR>
<STYLE></STYLE>
</HEAD>
<BODY bgColor=3D#ffffff>
<DIV><FONT face=3DArial size=3D2> Nope. They will pay =
someone or=20
someone will step up for money. For a very obvious example = look
at=20
all the content protection schemes in use not supported by Windows from = CSS
for=20
DVDs to apple's DRM for itunes.</FONT></DIV>
<DIV><FONT face=3DArial size=3D2></FONT> </DIV>
<DIV><FONT face=3DArial size=3D2>Rich</FONT></DIV>
<DIV><FONT face=3DArial size=3D2></FONT> </DIV>
<BLOCKQUOTE=20
style=3D"PADDING-RIGHT: 0px; PADDING-LEFT: 5px; MARGIN-LEFT: 5px; =
BORDER-LEFT: #000000 2px solid; MARGIN-RIGHT: 0px">
<DIV>"Geo." <<A =
href=3D"mailto:georger@nls.net">georger@nls.net</A>> wrote=20
in message <A=20
=
href=3D"news:45b42e12@w3.nls.net">news:45b42e12@w3.nls.net</A>...</DIV>It=
's not=20
required to play the game. If there is no support from software =
<BR>makers for=20
DRM then the content industry has to accept that in order to reap =
<BR>the=20
profits from that market. And as everyone knows, some profits are =
better=20
<BR>than NO profits..<BR><BR>Geo.<BR><BR>"Rich" <@> wrote in =
message <A=20
=
href=3D"news:45b40c49@w3.nls.net">news:45b40c49@w3.nls.net</A>...<BR>&nbs=
p; =20
Nonsense. Region coding, encryption (e.g. CSS), expiring content =
(e.g.=20
<BR>DivX) are examples that existed without pre-existing support from =
software=20
<BR>vendors. These and the other forms of restrictions all exist =
because=20
the <BR>content providers require it. Microsoft, Apple, real as =
well as=20
CE vendors <BR>(e.g. Pioneer, Creative, Apple) support it only because =
it is=20
required to <BR>even play the game. Without it you can only sit =
on the=20
outside and watch.<BR><BR>Rich<BR><BR> "Geo." <<A=20
href=3D"mailto:georger@nls.net">georger@nls.net</A>> wrote in =
message <A=20
=
href=3D"news:45b407ba@w3.nls.net">news:45b407ba@w3.nls.net</A>...<BR>&nbs=
p; My=20
point is it is the vendors who enable features like content=20
expiration<BR> who are responsible, not the people who requested =
it, but=20
the people like<BR> Microsoft who make it real.<BR><BR> =20
Geo.<BR><BR> "Rich" <@> wrote in message <A=20
=
href=3D"news:45b405a9$1@w3.nls.net">news:45b405a9$1@w3.nls.net</A>...<BR>=
=20
The implementation in Windows is a framework with a set of=20
capabilities<BR> necessary to meet the requirements of not just =
HD-DVD=20
but other content as<BR> well. It is not a hard coded=20
implementation of any specific requirements.<BR> This is =
necessary to=20
allow Windows to be a platform for playback of as =
<BR>much<BR> =20
content as possible.<BR><BR> Your example of=20
expiration is something that doesn't apply to HD-DVD, <BR>or<BR> =
at=20
least I don't think so but I could be wrong. I'm not at all=20
familiar<BR> with what AACS allows. It is something that =
applies=20
to distributable <BR>audio<BR> and video content. If you =
see it=20
used, you should contact the content<BR> provider and/or =
licensor to ask=20
why. FWIW, an expiration date has been<BR> supported since =
version=20
1.0 or WMDRM released in 1999.<BR><BR> =
Rich<BR><BR> =20
"Geo." <<A href=3D"mailto:georger@nls.net">georger@nls.net</A>> =
wrote in=20
message <A=20
=
href=3D"news:45b3c20f$1@w3.nls.net">news:45b3c20f$1@w3.nls.net</A>...<BR>=
=20
If the content protection in vista goes above and beyond that found=20
on<BR> HDDVD<BR> players then can you really =
claim it=20
was just to support protections<BR> mandated by the =
content?=20
For example if vista allows downloading content<BR> =
that=20
expires after a week, you can't possibly be serious that vista=20
<BR>isn't<BR> directly responsible for extending the =
capabilities of HD-DVD content<BR> =20
protection.<BR><BR> Geo.<BR><BR> =
"Rich"=20
<@> wrote in message <A=20
=
href=3D"news:45b2f6e3$1@w3.nls.net">news:45b2f6e3$1@w3.nls.net</A>...<BR>=
=20
The extra CPU is to support the protections mandated by the =
content.<BR> =20
The<BR> additional functionality is the ability to =
render=20
that content at all. <BR>If<BR> you don't want to =
play=20
protected content such as HD-DVD or bluray then =
<BR>you<BR> =20
should care that increased CPU is required to do so. If you do =
want=20
to<BR> play<BR> such content then you should =
be=20
pleased that it is possible.<BR><BR> =20
Rich<BR><BR> "Rich Gauszka" <<A=20
=
href=3D"mailto:gauszka@dontspamhotmail.com">gauszka@dontspamhotmail.com</=
A>>=20
wrote in message<BR> <A=20
=
href=3D"news:45b2ec71$1@w3.nls.net">news:45b2ec71$1@w3.nls.net</A>...<BR>=
=20
The Vista team is hallucinating equating additional CPU cycles used=20
<BR>for<BR> drm<BR> =
with=20
additional functionality for =
consumers.<BR><BR> =20
from the link<BR> =20
=
------------------------------------------------------------<BR> &nb=
sp; =20
Will Windows Vista content protection features increase CPU=20
resource<BR> =20
consumption?<BR><BR> Yes. However, =
the use=20
of additional CPU cycles is inevitable, as the=20
<BR>PC<BR> provides consumers with =
additional=20
functionality.<BR> =20
=
-------------------------------------------------------------<BR><BR>&nbs=
p; =20
"John Beamish" <<A=20
href=3D"mailto:JLBeamish@rogers.com">JLBeamish@rogers.com</A>> =
wrote in=20
message<BR> <A=20
=
href=3D"news:op.tmhkksu1m6tn4t@dellblack.wlfdle.phub.net.cable.rogers.com=
">news:op.tmhkksu1m6tn4t@dellblack.wlfdle.phub.net.cable.rogers.com</A>..=
.<BR> =20
> In this vein ... there was the story that Vista imposed DRM in =
such=20
<BR>a<BR> > manner that if (for =
example) you=20
were listening to a CD that was<BR> =20
subject<BR> > to DRM and you were a=20
technician viewing (according to this example)=20
<BR>a<BR> > digital x-ray that the =
x-ray=20
would be degraded to the same extent <BR>that<BR> =20
DRM<BR> > required the CD to be=20
degraded.<BR> =20
><BR> > The Windows Vista team =
replied=20
here:<BR> ><BR> <A=20
=
href=3D"http://windowsvistablog.com/blogs/windowsvista/archive/2007/01/20=
/windows-vista-content-protection-twenty-questions-and-answers.aspx">http=
://windowsvistablog.com/blogs/windowsvista/archive/2007/01/20/windows-vis=
ta-content-protection-twenty-questions-and-answers.aspx</A><BR></BLOCKQUO=
TE></BODY></HTML>
------=_NextPart_000_112D_01C73D9A.1C64BB50--
--- BBBS/NT v4.01 Flag-5
* Origin: Barktopia BBS Site http://HarborWebs.com:8081 (1:379/45)
|