On 12/1/06, <b class="gmail_sendername">Patrick Ouellette</b> <<a href="mailto:pat@flying-gecko.net">pat@flying-gecko.net</a>> wrote:<div><span class="gmail_quote"></span><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
On Fri, Dec 01, 2006 at 12:07:11PM -0500, Michael Tiller wrote:<br>><br>> built MythTV from SVN recently and specifically looked and it said something<br>> like "OpenGL Sync: Disabled" or some such thing. That is the correct
<br>> setting right? (i.e. the default setting)<br><br>I was told to try turning it on and it seems to work for me.</blockquote><div><br>I'm just starting wonder how many of these claims have actually been substantiated. :-) So many XvMC related issues seem to be "try standing on your head and rubbing your stomach". I'm always left wondering "Are you sure this makes any difference?" :-)
<br></div><br><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">> using the latest NVidia driver<br>><br>> I've got a 440 MX using the 8776 driver.
<br><br>9629 driver. Check the AGP settings in the xorg.conf to be sure you age<br>really getting full speed out of the AGP.</blockquote><div><br>It's not an AGP card. <br></div><br><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
Partially, if you enable the OpenGL vblank at compile time, you get a<br>check box in the TV Playback setup screen too (same screen that sets<br>"use video as timebase" I think).</blockquote><div><br>I get that setting even without enable OpenGL vsync.
<br></div><br><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">> soundcard buffer settings<br>><br>><br>> By this do you mean turn on extra audio buffering during playback? (in the
<br>> Playback settings on the front end)<br><br>You can try it - for my system it helps to have it turned on with the<br>9629 video driver, but off with the 8776 driver (don't know why).<br><br>I will say XvMC output really, really, really, really sucked on my
<br>system before 8776, and 9629 is even better.</blockquote><div><br>I'll have to try 9629 just to cover all the bases but I'm not optimistic. <br></div><br><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
> and dot clock in my modeline have significantly improved my XvMC output.<br>><br>><br>> I'm lost here. I've tried adding my own modelines but it always complains<br>> they aren't valid</blockquote><div><br>
</div><br><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">There is a modeline calculator at<br><a href="http://xtiming.sourceforge.net/cgi-bin/xtiming.pl">
http://xtiming.sourceforge.net/cgi-bin/xtiming.pl</a><br><br>Something around this should be close:<br><br>Modeline "720x480@60i" 12.60 720 752 792 824 480 491 494 505 interlace</blockquote><div><br>I still get:
<br><br>(II) NVIDIA(0): Assigned Display Device: TV-0<br>(WW) NVIDIA(0): No valid modes for "1024x768_60"; removing.<br>(WW) NVIDIA(0): No valid modes for "720x480@60i"; removing.<br>(WW) NVIDIA(0): No valid modes for "720x480_60"; removing.
<br>(WW) NVIDIA(0): No valid modes for "NTSC_60i"; removing.<br>(II) NVIDIA(0): Validated modes:<br>(II) NVIDIA(0): "1024x768"<br>(II) NVIDIA(0): "720x480"<br>(II) NVIDIA(0): Virtual screen size determined to be 1024 x 768
<br><br>I'm putting the Modeline here:<br><br><blockquote style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;" class="gmail_quote"><div style="margin-left: 40px;">Section "Monitor"
<br> Identifier "Monitor0"<br> VendorName "Monitor Vendor"<br> ModelName "27in Analog TV"<br> HorizSync 30.0 - 50.0<br> #VertRefresh 60.0 - 60.0<br>
Option "dpms"<br> Option "UseEdidDpi" "FALSE"<br> Option "DPI" "100 x 100"<br> ModeLine "NTSC_60i" 14.318 768 784 848 910 483 484 492 525 Interlace
<br> Modeline "720x480_60" 26.72 720 736 808 896 480 481 484 497 -HSync +Vsync<br> Modeline "720x480@60i" 12.60 720 752 792 824 480 491 494 505 interlace<br>EndSection<br></div></blockquote>
<br>...is this the right place. I notice that it names the device "TV-0". Do I have to use the same name for my monitor?!?<br><br> <br></div><br><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
The calculator should be able to come up with something that works. The NVidia<br>driver restricts modelines depending on the output format and tv<br>standard.<br><br>option "TVStandard" "NTSC-M"<br>Option "TVOutFormat" "SVIDEO"
</blockquote><div><br>Exactly what I have. <br></div><br><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">or change SVIDEO to COMPOSITE for composite out.
<br><br>If you are using an external converter, you should be able to get a<br>wider variety of modelines to work.</blockquote><div><br>I'm thinking I'm doing something fundamentally wrong since no Modeline I put in the file seems to work?!?
<br></div><br><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">DISCALIMER: I run the SVN-HEAD version of Myth, YMMV for release<br>versions.</blockquote>
<div><br>I'm running the fixes branch from SVN. <br></div><br><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">Pat</blockquote><div><br>Thanks for all the help.
<br><br>--<br>Mike<br> <br></div><br></div>