From: "Rich" 

This is a multi-part message in MIME format.

------=_NextPart_000_0211_01C72C5C.61DAA180
Content-Type: text/plain;
        charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable

   There is no protected content for it to apply.  As you note, Windows =
Media Player works so you can clearly display the content on your = system.

   You would have to look at the encoder documentation to see to what =
profile applies.  I believe it refers to not just bitrate but also =
variations such as whether the encoding uses a constant or variable =
bitrate, resolution, and other quality factors.  It may be that Movie =
Maker doesn't expose this or does so in a simplified manner.  I noticed =
this when I played in the past with Windows Media Encoder.

   I don't have a system on to which to install media player classic and =
I don't like installing random software on my production systems.

Rich

  "Geo."  wrote in message =
news:45973179$1{at}w3.nls.net...
  Ok, so then you're saying that PMP doesn't exist if the file is not =
drm=20
  wrapped? Because this only happens at resolutions over 480p it sure =
looks=20
  like if it's a bug it's a bug in PMP or at least caused by PMP.

  what exactly is a codec profile? Is there some way to control this =
from=20
  Windows Movie maker because I changed absolutely nothing but the =
resolution=20
  and hit publish when creating the test videos.

  You can download Media Player Classic here=20
  =
http://sourceforge.net/project/showfiles.php?group_id=3D82303&package_id=3D=
84358&release_id=3D403110
  it's the second one in the list if you feel like looking at this to =
see if=20
  it does it on your system.

  Geo.

  "Rich"  wrote in message news:45972c0f{at}w3.nls.net...
     It's very obvious it's not as there is no DRM in any of the files.  =
While=20
  the codec may be the same, the profile I believe it is called is not.=20
  Within a single codec you can have differences.  That the other two =
players=20
  fail on Windows Vista only in some cases suggests a bug.  Unless the =
two=20
  broken players were tested on Vista I would suspect that the bug =
resides in=20
  them.

  Rich

    "Geo."  wrote in message =
news:4596e221$1{at}w3.nls.net...


    It think its pretty obvious at this point that it's DRM at work =
here.

    Geo.

------=_NextPart_000_0211_01C72C5C.61DAA180
Content-Type: text/html;
        charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable








   There is
no protected =
content for it=20
to apply.  As you note, Windows Media Player works so you can = clearly=20
display the content on your system.
 
   You would
have to look at =
the encoder=20
documentation to see to what profile applies.  I believe it refers
= to not=20
just bitrate but also variations such as whether the encoding uses a = constant or=20
variable bitrate, resolution, and other quality factors.  It may
be = that=20
Movie Maker doesn't expose this or does so in a simplified manner.  = I=20
noticed this when I played in the past with Windows Media =
Encoder.
 
   I don't
have a system on =
to which to=20
install media player classic and I don't like installing random software = on my=20
production systems.
 
Rich
 

  "Geo." <georger{at}nls.net>">mailto:georger{at}nls.net">georger{at}nls.net>
wrote=20
  in message news:45973179$1{at}w3.nls.net...Ok,=20
  so then you're saying that PMP doesn't exist if the file is not drm=20
  wrapped? Because this only happens at resolutions over 480p it =
sure looks=20
  like if it's a bug it's a bug in PMP or at least caused by=20
  PMP.what exactly is a codec profile? Is there some way to =
control this=20
  from Windows Movie maker because I changed absolutely nothing but =
the=20
  resolution and hit publish when creating the test =
videos.You can=20
  download Media Player Classic here http://sourceforge.net/project/showfiles.php?group_id=3D82303&=
;package_id=3D84358&release_id=3D403110">http://sourceforge.net/proje=
ct/showfiles.php?group_id=3D82303&package_id=3D84358&release_id=3D=
403110it's=20
  the second one in the list if you feel like looking at this to see if =
it=20
  does it on your
system.Geo."Rich"
<{at}> wrote in =
message=20
  news:45972c0f{at}w3.nls.net...&nbs=
p; =20
  It's very obvious it's not as there is no DRM in any of the =
files.  While=20
  the codec may be the same, the profile I believe it is called is =
not.=20
  Within a single codec you can have differences.  That the =
other two=20
  players fail on Windows Vista only in some cases suggests a =
bug. =20
  Unless the two broken players were tested on Vista I would suspect =
that=20
  the bug resides in
them.Rich 
"Geo." <georger{at}nls.net>">mailto:georger{at}nls.net">georger{at}nls.net>
wrote in =
message news:4596e221$1{at}w3.nls.net...=
 =20
  It think its pretty obvious at this point that it's DRM at work=20
  here. 
Geo.

------=_NextPart_000_0211_01C72C5C.61DAA180--

--- BBBS/NT v4.01 Flag-5