[mythtv-users] Svideo Tearing
Jonathan Rogers
jonner at teegra.net
Sat May 20 12:19:18 UTC 2006
Mache Creeger wrote:
> While mplayer SD video as viewed on my CRT is excellent, I get
> tearing during fast pans in clone mode viewing SD video through
> svideo-out on a standard TV. I have the same results with both a
> GeForce FX 5500 and GeForce FX 6200. I have tried repeatedly to get
> a single response from the Nvidia support forum but have been
> unsuccessful to date. I have a WinTV PVR 500 capture card and the
> mpg files it generates are excellent. This has been proven by
> watching the video on a Windows box using Windows Media Player and a
> Samba mount of the file.
>
> I need to demonstrate to my spouse that my MythTV investment is
> worthwhile. The tearing annoys her and while the video quality on a
> PC is excellent, watching shows using Tapeworm on her PC will not cut
> it for her. I am running all the most recent versions of
> MythTV. Any help would be most appreciated.
>
> My xorg.conf and .nvidia-settings-rc files are listed below. I am
> running FC5, 2111 kernel, and the 8756 nvidia driver.
>
> -- Mache Creeger
>
> =================================================================
>
> /etc/X11/xorg.conf
>
> # XFree86 4 configuration created by pyxf86config
> # Section "DRI"
> # Group 0
> # Mode 0666
> # EndSection
>
> Section "ServerLayout"
> Identifier "Default Layout"
> Screen 0 "Screen0" 0 0
> InputDevice "Mouse0" "CorePointer"
> InputDevice "Keyboard0" "CoreKeyboard"
> EndSection
>
> Section "Files"
>
> # Multiple FontPath entries are allowed (they are concatenated together)
> # By default, a font server independent of the X server is
> # used to render fonts.
> ModulePath "/usr/lib/xorg/modules/extensions/nvidia"
> ModulePath "/usr/lib/xorg/modules"
> FontPath "unix/:7100"
> EndSection
>
> Section "Module"
> Load "dbe"
> Load "extmod"
> Load "fbdevhw"
> Load "record"
> Load "freetype"
> Load "type1"
> Load "glx"
> EndSection
>
> Section "InputDevice"
>
> # Specify which keyboard LEDs can be user-controlled (eg, with xset(1))
> # Option "Xleds" "1 2 3"
> # To disable the XKEYBOARD extension, uncomment XkbDisable.
> # Option "XkbDisable"
> # To customise the XKB settings to suit your keyboard, modify the
> # lines below (which are the defaults). For example, for a non-U.S.
> # keyboard, you will probably want to use:
> # Option "XkbModel" "pc102"
> # If you have a US Microsoft Natural keyboard, you can use:
> # Option "XkbModel" "microsoft"
> #
> # Then to change the language, change the Layout setting.
> # For example, a german layout can be obtained with:
> # Option "XkbLayout" "de"
> # or:
> # Option "XkbLayout" "de"
> # Option "XkbVariant" "nodeadkeys"
> #
> # If you'd like to switch the positions of your capslock and
> # control keys, use:
> # Option "XkbOptions" "ctrl:swapcaps"
> # Or if you just want both to be control, use:
> # Option "XkbOptions" "ctrl:nocaps"
> #
> Identifier "Keyboard0"
> Driver "kbd"
> Option "XkbModel" "pc105"
> Option "XkbLayout" "us"
> EndSection
>
> Section "InputDevice"
> Identifier "Mouse0"
> Driver "mouse"
> Option "Protocol" "IMPS/2"
> Option "Device" "/dev/input/mice"
> Option "ZAxisMapping" "4 5"
> Option "Emulate3Buttons" "yes"
> EndSection
>
> Section "Monitor"
>
> ### Comment all HorizSync and VertSync values to use DDC:
> ### Comment all HorizSync and VertSync values to use DDC:
> ### Comment all HorizSync and VertSync values to use DDC:
> ### Comment all HorizSync and VertSync values to use DDC:
> ### Comment all HorizSync and VertSync values to use DDC:
> ### Comment all HorizSync and VertSync values to use DDC:
> ### Comment all HorizSync and VertSync values to use DDC:
> ### Comment all HorizSync and VertSync values to use DDC:
> ### Comment all HorizSync and VertSync values to use DDC:
> ### Comment all HorizSync and VertSync values to use DDC:
> ### Comment all HorizSync and VertSync values to use DDC:
> ### Comment all HorizSync and VertSync values to use DDC:
> ### Comment all HorizSync and VertSync values to use DDC:
> ### Comment all HorizSync and VertSync values to use DDC:
> ### Comment all HorizSync and VertSync values to use DDC:
> ### Comment all HorizSync and VertSync values to use DDC:
> ### Comment all HorizSync and VertSync values to use DDC:
> ### Comment all HorizSync and VertSync values to use DDC:
> Identifier "Monitor0"
> VendorName "Monitor Vendor"
> ModelName "Dell M1110"
> DisplaySize 400 300
> ### Comment all HorizSync and VertSync values to use DDC:
> HorizSync 30.0 - 107.0
> VertRefresh 50.0 - 160.0
> ModeLine "1024x768" 94.5 1024 1072 1168 1376 768 769 772
> 808 +hsync +vsync
> Option "dpms"
> EndSection
>
> Section "Device"
> Identifier "Videocard0"
> Driver "nvidia"
> VendorName "Videocard vendor"
> BoardName "nVidia Corporation GeForce 6200"
> EndSection
>
> Section "Screen"
> Identifier "Screen0"
> Device "Videocard0"
> Monitor "Monitor0"
> DefaultDepth 24
> Option "NvAgp" "1"
> Option "NoLogo" "1"
> Option "RenderAccel" "1"
> Option "TwinView" "1"
> Option "TwinViewOrientation" "Clone"
> Option "SecondMonitorHorizSync" "30-50"
> Option "SecondMonitorVertRefresh" "60"
> Option "MetaModes" "1024x768, 1024x768"
> Option "ConnectedMonitor" "TV, CRT"
> Option "TVStandard" "NTSC-M"
> Option "TVOutFormat" "SVIDEO"
> Option "TVOverScan" "0.7"
> Option "TransparentIndex" "0"
> SubSection "Display"
> Viewport 0 0
> Depth 24
> Modes "1024x768"
> EndSubSection
> EndSection
>
> ==========================
>
> .nvidia-settings-rc
>
> #
> # /home/mythtv/.nvidia-settings-rc
> #
> # Configuration file for nvidia-settings - the NVIDIA X Server Settings utility
> # Generated on Wed May 17 10:52:22 2006
> #
>
> # ConfigProperties:
>
> ToolTips = Yes
> DisplayStatusBar = Yes
> SliderTextEntries = Yes
> IncludeDisplayNameInConfigFile = No
> ShowQuitDialog = Yes
>
> # Attributes:
>
> 0/DigitalVibrance[CRT-0]=0
> 0/DigitalVibrance[TV-0]=0
> 0/ImageSharpening[CRT-0]=0
> 0/ImageSharpening[TV-0]=0
> 0/SyncToVBlank=1
> 0/AllowFlipping=1
> 0/LogAniso=0
> 0/FSAA=0
> 0/TextureSharpen=0
> 0/ForceGenericCpu=0
> 0/CursorShadow=0
> 0/CursorShadowXOffset=4
> 0/CursorShadowYOffset=2
> 0/CursorShadowAlpha=64
> 0/CursorShadowRed=0
> 0/CursorShadowGreen=0
> 0/CursorShadowBlue=0
> 0/FSAAAppControlled=1
> 0/LogAnisoAppControlled=1
> 0/RedBrightness=0.000000
> 0/GreenBrightness=0.000000
> 0/BlueBrightness=0.000000
> 0/RedContrast=0.000000
> 0/GreenContrast=0.000000
> 0/BlueContrast=0.000000
> 0/RedGamma=1.000000
> 0/GreenGamma=1.000000
> 0/BlueGamma=1.000000
> 0/OpenGLImageSettings=0
> 0/XVideoTextureSyncToVBlank=1
> 0/XVideoBlitterSyncToVBlank=0
> 0/XVideoSyncToDisplay=256
It's just a guess, but "0/XVideoBlitterSyncToVBlank=0" might be
relevant. See if you can enable that option. I'm not sure what the
difference between Xvideo textures and blitter is or what MythTV uses.
Also, looking in nvidia-settings on my desktop (which currently only has
a VGA CRT connected), I see the setting "Sync to this display device,"
which seems to correspond to your XVideoSyncToDisplay attribute. It
seems to me that you need to select the TV as the display to sync to,
but I don't know what "256" means.
Jonathan Rogers
More information about the mythtv-users
mailing list