<!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 bgcolor="#ffffff" text="#000000">
<blockquote type="cite"><font color="black"
face="Verdana,Arial,Helvetica" size="2"><font color="black"
face="Verdana,Arial,Helvetica" size="2"> From the man page for the
i810 driver: <br>
Option "XvMCSurfaces" "integer" <br>
This option enables XvMC. The integer parameter specifies the <br>
number of surfaces to use. Valid values are 6 and 7. Default: <br>
XvMC is disabled. <br>
<br>
Now I notice that the Xorg.0.log says something to the effect that the <br>
XvMCSurfaces line is ignored, and then the i810 driver seems to use
xvmc... <br>
However, on my box, I have now noticed that if I re-boot (which I try <br>
not to do, but this is a new buildup) the Xserver sometime does not <br>
start, and the system creates a new xorg.conf *using the intel driver*.
<br>
Same Option line is required for that driver, plus 'Option
"LinearAlloc" <br>
"6144" for HD. The intel driver works on my box, but it is using ffmpeg
<br>
decoding. From Xorg.0.log: <br>
<br>
2007-10-03 22:19:19.167 VideoOutputXv Error: XvMC output requested, but
<br>
is not supported by display. <br>
Xlib: extension "XVideo-MotionCompensation" missing on display ":0.0". <br>
2007-10-03 22:19:19.168 XvMCSurfaceTypes::find(w 1280, h 720, chroma 1,
<br>
vld 0, idct 1, mpeg2, sub-width 0, sub-height 0, disp, p<= 88, 730
<=p, <br>
port, surfNum) <br>
2007-10-03 22:19:19.168 Trying XvMC port 73 <br>
.... <br>
<br>
So maybe *both* of them don't do xvmc? That is clearly not correct, so <br>
something is going on...And the mythbox still records, and plays, so
I'm <br>
not touching it until the weekend! <br>
<br>
Geoff <br>
</font></font></blockquote>
<br>
Yeah, I quickly found out that XvMC doesn't seem to work with this
chipset. Upon closer inspection of the manual the 'XvMCSurfaces'
option is listed under the section that says "The following driver
Options are supported for the i810 and i815 chipsets:". Since this
frontend has a 915G chipset it appears that I am SOL for XvMC.<br>
<br>
I am still using the 1.x version (i810) of the driver rather than the
brand-new 2.x (renamed intel) version. The main advantage of the new
driver seems to be the ability to use non-BIOS resolutions and since I
just use a standard resolution and from your description it sounds like
it doesn't do XvMC I will probably just continue to use my current
driver. I have played around with the various deinterlacing options
and I am getting much better video quality than before. It appears
that I need to deinterlace the HD stream before it is interlaced and
sent to my TV. My CPU seems to be able to handle the playback and
deinterlacing so I probably don't have to have XvMC although if I did
it might help me to use BOB deinterlacing. <br>
<br>
When I first tested this machine for HD I ran into the 'badalloc' error
and googled a solution and set LinearAlloc to 8192. When I was reading
the manual pages today I saw the line recommending 6144 and so I
changed my xorg.conf to that value. This caused my machine to lock up
HARD with nasty things happening to my display when I attempted to view
HD content. Changing the value back to 8192 fixed the problem. <br>
<br>
<br>
</body>
</html>