LinHES Forums http://forums.linhes.org/ |
|
visual distortions watching SD content on HD set http://forums.linhes.org/viewtopic.php?f=15&t=19594 |
Page 1 of 2 |
Author: | graysky [ Wed Feb 25, 2009 4:02 pm ] |
Post subject: | visual distortions watching SD content on HD set |
Basically, most if not all of my xvid transcoded content looks horrible on my new HD set. The set is DVI-->HDMI running 1680x1050 (screen's native resolution) and the avi files are 512x384 or 720x480. I'm watching them with mplayer in mythvideo. EDIT: seems as though my PVR-250's capture files do this as well. They are 720x480 and played back using the internal player as I normally watch them. The best way I can describe the distortions are horizontal lines that appear over areas of motion. Is this what I've seen people term as 'cutting'? Are there known work arounds for it? Thanks! |
Author: | wmcvetty [ Wed Feb 25, 2009 9:32 pm ] |
Post subject: | |
Just did the same. I upped my bitrate quite a bit and changed my playback settings to bob(2x) and one field as the secondary deinterlacer. That and setting my videoscan to either detect or interlaced normal. It's not perfect, but that's the best I could get. Anyone else have any tips as I am attempting to be cheap and not do hd just yet. |
Author: | Grant_Edwards [ Wed Feb 25, 2009 10:30 pm ] |
Post subject: | Re: visual distortions watching SD content on HD set |
graysky wrote: Basically, most if not all of my xvid transcoded content looks
horrible on my new HD set. The set is DVI-->HDMI running 1680x1050 (screen's native resolution) and the avi files are 512x384 or 720x480. I'm watching them with mplayer in mythvideo. EDIT: seems as though my PVR-250's capture files do this as well. They are 720x480 and played back using the internal player as I normally watch them. The best way I can describe the distortions are horizontal lines that appear over areas of motion. Sounds like de-interlacing artifacts. Try some different de-interlacing methods (bob2x is reputed to look the best). In any case, watching low-res stuff on a 1680x1050 panel is always going to look bad. You can play with settings to make it a little less bad, but you're never going to be happy with. Start saving up for an ATSC/QAM tuner. In the meantime, sit further away and squint. |
Author: | tjc [ Wed Feb 25, 2009 11:08 pm ] |
Post subject: | |
It may also be scaling artifacts. These are quite common when you're blowing an image up. Especially if the size relationships between the original resolution and the display resolution aren't simple (in this case simple means simple ratios). For example 1->2 or even 1->3 generally gives good results (although it may start to look blocky and pixellated, and 2 -> 3 generally isn't bad, but when you start to get say 3->7 or 32->105 you'll see serious effects from the scaling, especially if you're not using some kind of fairly good smoothing filter. |
Author: | wmcvetty [ Thu Feb 26, 2009 8:27 am ] |
Post subject: | |
Where are the smoothing filters set and are there any recomendations? Is that the setting right before the playback profiles? Thanks! |
Author: | graysky [ Thu Feb 26, 2009 3:11 pm ] |
Post subject: | |
Thanks for the replies, all. When I use the mplayer that came w/ my Ubuntu 8.10 install on my desktop machine, I don't see these distortions AT ALL playing the same files with the same mplayer options.... the only differences are: Desktop Machine Distro: Ubuntu 8.10 amd64 X Manager: Gnome Video Card: 8800GTS, 512 meg (PCI-E 16x) Video Driver: v180.29 Monitor: 22" Samsung LCD, model T220 (2 ms) Frontend Machine Distro: KM R5.5 X Manager: Fluxbox Video Card: 8400GS, 512 meg (PCI) Video Driver: v177.14.x Monitor: 22" Samsung HDTV, model LN22450A (8 ms) Can anyone explain this? Is it the 8 ms response time on the HDTV that's messing with me? EDIT: It's *NOT* the differences in the screens. I just hooked both of them up to my desktop machine (twinview) driving off my 8800GTS and I can play the same file in each monitor free of distortion. Now it seems as though the variables are: 1) Video cards and/or drivers 2) mplayer version 3) Linux versions? 4) Something Gnome is doing that fluxbox isn't doing? 4) something I'm not thinking of.... I can put the 32-bit version of Ubuntu 8.10 on my frontend (spare HDD) and do this same comparison on the 8400GS (PCI) card to see. Again, suggestions are welcomed |
Author: | ceenvee703 [ Thu Feb 26, 2009 3:56 pm ] |
Post subject: | |
When you're in TwinView mode and playing from your desktop machine, what resolution is the HDTV being driven at? Is it the same as the resolution you're running your frontend at? |
Author: | graysky [ Thu Feb 26, 2009 4:01 pm ] |
Post subject: | |
ceenvee703 wrote: When you're in TwinView mode and playing from your desktop machine, what resolution is the HDTV being driven at? Is it the same as the resolution you're running your frontend at?
Yes, it's the same: 1680x1050 (the HDTV's recommended resolution). |
Author: | graysky [ Thu Feb 26, 2009 5:33 pm ] |
Post subject: | |
OK! I got Ubuntu 8.10 on the frontend machine, using the 180.29 drivers, and using the ubuntu mplayer, I do NOT see the distortions that I see when running R5.5 Therefore, it's gotta be something in R5.5 that's causing these since I ruled out the hardware. I'll try two things under R5.5: 1) compile my own mplayer from source and see if that matters 2) try to update the drivers to 180.29 If both those fail, does anyone have a suggestion? Could it be something that fluxbox isn't doing that Gnome is doing? |
Author: | ceenvee703 [ Thu Feb 26, 2009 6:11 pm ] |
Post subject: | |
I wish I knew more to say conclusively that it couldn't be Fluxbox, but I wouldn't think so. It's worth trying to upgrade the drivers, and possibly mplayer. I'd also triple-check (via xorg logs) that your KnoppMyth box is running at the same resolution AND the same refresh rate AND the same color depth that your Ubuntu box is running at. Just because you have your xorg.conf file set up a certain way doesn't mean it's doing something differently than you think it is... checking the xorg logs is the only way to know what it's really running at. |
Author: | graysky [ Thu Feb 26, 2009 7:24 pm ] |
Post subject: | |
Well, the 180.29 drivers didn't help either.... Here is the damn /var/log/Xorg.0.log. You have to d/l it as a text file because it's too massive to post. Link to Xorg.0.log Here is the /etc/X11/xorg.conf Code: Section "ServerLayout"
Identifier "XFree86 Configured" Screen 0 "Screen0" 0 0 InputDevice "Keyboard0" "CoreKeyboard" # PS/2 Mouse not detected # Serial Mouse not detected InputDevice "USB Mouse" "CorePointer" EndSection Section "ServerFlags" Option "AllowMouseOpenFail" "true" EndSection Section "Files" RgbPath "/usr/share/X11/rgb" ModulePath "/usr/lib/xorg/modules" FontPath "/usr/share/fonts/X11/misc:unscaled" FontPath "/usr/share/fonts/X11/75dpi:unscaled" FontPath "/usr/share/fonts/X11/100dpi:unscaled" FontPath "/usr/share/fonts/X11/Type1" FontPath "/usr/share/fonts/X11/Speedo" FontPath "/usr/share/fonts/X11/PEX" # Additional fonts: Locale, Gimp, TTF... FontPath "/usr/share/fonts/X11/cyrillic" # FontPath "/usr/share/fonts/X11/latin2/75dpi" # FontPath "/usr/share/fonts/X11/latin2/100dpi" # True type and type1 fonts are also handled via xftlib, see /etc/X11/XftConfig! FontPath "/var/lib/defoma/x-ttcidfont-conf.d/dirs/TrueType" FontPath "/usr/share/fonts/truetype" FontPath "/usr/share/fonts/latex-ttf-fonts" EndSection Section "Module" # Comments: see http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=346408 Load "dbe" # Double Buffering Extension, very important. # Load "dri" # This shouldn't be available choice if user has selected driver vga, vesa or nv. Load "glx" # GLX Extension. Load "freetype" # Freetype fonts. Load "type1" # Type 1 fonts Load "record" # Developer extension, usually not needed # Load "extmod" # This is okay, but if you look into "man xorg.conf" you'll find option NOT to include DGA extension with extmod, and for a good reason.. DGA causes instability as it access videoram without consulting X about it. SubSection "extmod" Option "omit xfree86-dga" EndSubSection # Load "speedo" # Speedo fonts, this module doesn't exist in Xorg 7.0.17 # The following are deprecated/unstable/unneeded in Xorg 7.0 # Load "ddc" # ddc probing of monitor, this should be never present, as it gets automatically loaded. # Load "GLcore" # This should be never present, as it gets automatically loaded. # Load "bitmap" # Should be never present, as it gets automatically loaded. This is a font module, and loading it in xorg.conf makes X try to load it twice. EndSection Section "InputDevice" Identifier "Keyboard0" Driver "kbd" Option "CoreKeyboard" Option "XkbRules" "xorg" Option "XkbModel" "pc105" Option "XkbLayout" "us" EndSection Section "InputDevice" Identifier "Serial Mouse" Driver "mouse" Option "Protocol" "Microsoft" Option "Device" "/dev/ttyS0" Option "Emulate3Buttons" "true" Option "Emulate3Timeout" "70" Option "SendCoreEvents" "true" EndSection Section "InputDevice" Identifier "PS/2 Mouse" Driver "mouse" Option "Protocol" "auto" Option "ZAxisMapping" "4 5" Option "Device" "/dev/psaux" Option "Emulate3Buttons" "true" Option "Emulate3Timeout" "70" Option "SendCoreEvents" "true" EndSection Section "InputDevice" Identifier "USB Mouse" Driver "mouse" Option "Device" "/dev/input/mice" Option "SendCoreEvents" "true" Option "Protocol" "IMPS/2" Option "ZAxisMapping" "4 5" Option "Buttons" "5" EndSection # Auto-generated by KNOPPIX mkxf86config Section "Monitor" Identifier "Monitor0" Option "DPMS" "true" Option "UseEdidDpi" "FALSE" Option "DPI" "100 x 100" VendorName "VSC" ModelName "VSCbc1c" HorizSync 30 - 97 # DDC-probed VertRefresh 50 - 160 # DDC-probed # These are the DDC-probed settings reported by your monitor. # 1280x1024, 85.0Hz; hfreq=91.15, vfreq=85.02 ModeLine "1280x1024" 157.50 1280 1344 1504 1728 1024 1025 1028 1072 +hsync +vsync # 1280x1024, 75.0Hz; hfreq=79.98, vfreq=75.03 ModeLine "1280x1024" 135.00 1280 1296 1440 1688 1024 1025 1028 1066 +hsync +vsync # 1152x864, 75.0Hz; hfreq=67.50, vfreq=75.00 ModeLine "1152x864" 108.00 1152 1216 1344 1600 864 865 868 900 +hsync +vsync # 1024x768, 85.0Hz; hfreq=68.68, vfreq=85.00 ModeLine "1024x768" 94.50 1024 1072 1168 1376 768 769 772 808 +hsync +vsync # 1024x768, 75.0Hz; hfreq=60.02, vfreq=75.03 ModeLine "1024x768" 78.75 1024 1040 1136 1312 768 769 772 800 +hsync +vsync # 1024x768, 70.0Hz; hfreq=56.48, vfreq=70.07 ModeLine "1024x768" 75.00 1024 1048 1184 1328 768 771 777 806 -hsync -vsync # 800x600, 85.0Hz; hfreq=53.67, vfreq=85.06 ModeLine "800x600" 56.25 800 832 896 1048 600 601 604 631 +hsync +vsync # 800x600, 75.0Hz; hfreq=46.88, vfreq=75.00 ModeLine "800x600" 49.50 800 816 896 1056 600 601 604 625 +hsync +vsync # 800x600, 72.0Hz; hfreq=48.08, vfreq=72.19 ModeLine "800x600" 50.00 800 856 976 1040 600 637 643 666 +hsync +vsync # 800x600, 60.0Hz; hfreq=37.88, vfreq=60.32 ModeLine "800x600" 40.00 800 840 968 1056 600 601 605 628 +hsync +vsync # 800x600, 56.0Hz; hfreq=35.16, vfreq=56.25 ModeLine "800x600" 36.00 800 824 896 1024 600 601 603 625 +hsync +vsync # 640x480, 75.0Hz; hfreq=37.50, vfreq=75.00 ModeLine "640x480" 31.50 640 656 720 840 480 481 484 500 -hsync -vsync # 640x480, 72.0Hz; hfreq=37.86, vfreq=72.81 ModeLine "640x480" 31.50 640 656 696 816 480 481 484 504 -hsync -vsync # 640x480, 60.0Hz; hfreq=31.47, vfreq=59.94 ModeLine "640x480" 25.17 640 648 744 784 480 482 484 509 -hsync -vsync # Extended modelines with GTF timings # 640x480 @ 100.00 Hz (GTF) hsync: 50.90 kHz; pclk: 43.16 MHz ModeLine "640x480" 43.16 640 680 744 848 480 481 484 509 -HSync +Vsync # 768x576 @ 60.00 Hz (GTF) hsync: 35.82 kHz; pclk: 34.96 MHz ModeLine "768x576" 34.96 768 792 872 976 576 577 580 597 -HSync +Vsync # 768x576 @ 72.00 Hz (GTF) hsync: 43.27 kHz; pclk: 42.93 MHz ModeLine "768x576" 42.93 768 800 880 992 576 577 580 601 -HSync +Vsync # 768x576 @ 75.00 Hz (GTF) hsync: 45.15 kHz; pclk: 45.51 MHz ModeLine "768x576" 45.51 768 808 888 1008 576 577 580 602 -HSync +Vsync # 768x576 @ 85.00 Hz (GTF) hsync: 51.42 kHz; pclk: 51.84 MHz ModeLine "768x576" 51.84 768 808 888 1008 576 577 580 605 -HSync +Vsync # 768x576 @ 100.00 Hz (GTF) hsync: 61.10 kHz; pclk: 62.57 MHz ModeLine "768x576" 62.57 768 816 896 1024 576 577 580 611 -HSync +Vsync # 800x600 @ 100.00 Hz (GTF) hsync: 63.60 kHz; pclk: 68.18 MHz ModeLine "800x600" 68.18 800 848 936 1072 600 601 604 636 -HSync +Vsync # 1024x768 @ 100.00 Hz (GTF) hsync: 81.40 kHz; pclk: 113.31 MHz ModeLine "1024x768" 113.31 1024 1096 1208 1392 768 769 772 814 -HSync +Vsync # 1152x864 @ 60.00 Hz (GTF) hsync: 53.70 kHz; pclk: 81.62 MHz ModeLine "1152x864" 81.62 1152 1216 1336 1520 864 865 868 895 -HSync +Vsync # 1152x864 @ 85.00 Hz (GTF) hsync: 77.10 kHz; pclk: 119.65 MHz ModeLine "1152x864" 119.65 1152 1224 1352 1552 864 865 868 907 -HSync +Vsync # 1152x864 @ 100.00 Hz (GTF) hsync: 91.50 kHz; pclk: 143.47 MHz ModeLine "1152x864" 143.47 1152 1232 1360 1568 864 865 868 915 -HSync +Vsync # 1280x960 @ 72.00 Hz (GTF) hsync: 72.07 kHz; pclk: 124.54 MHz ModeLine "1280x960" 124.54 1280 1368 1504 1728 960 961 964 1001 -HSync +Vsync # 1280x960 @ 75.00 Hz (GTF) hsync: 75.15 kHz; pclk: 129.86 MHz ModeLine "1280x960" 129.86 1280 1368 1504 1728 960 961 964 1002 -HSync +Vsync # 1280x960 @ 100.00 Hz (GTF) hsync: 101.70 kHz; pclk: 178.99 MHz ModeLine "1280x960" 178.99 1280 1376 1520 1760 960 961 964 1017 -HSync +Vsync # 1280x1024 @ 100.00 Hz (GTF) hsync: 108.50 kHz; pclk: 190.96 MHz ModeLine "1280x1024" 190.96 1280 1376 1520 1760 1024 1025 1028 1085 -HSync +Vsync # 1400x1050 @ 60.00 Hz (GTF) hsync: 65.22 kHz; pclk: 122.61 MHz ModeLine "1400x1050" 122.61 1400 1488 1640 1880 1050 1051 1054 1087 -HSync +Vsync # 1400x1050 @ 72.00 Hz (GTF) hsync: 78.77 kHz; pclk: 149.34 MHz ModeLine "1400x1050" 149.34 1400 1496 1648 1896 1050 1051 1054 1094 -HSync +Vsync # 1400x1050 @ 75.00 Hz (GTF) hsync: 82.20 kHz; pclk: 155.85 MHz ModeLine "1400x1050" 155.85 1400 1496 1648 1896 1050 1051 1054 1096 -HSync +Vsync # 1400x1050 @ 85.00 Hz (GTF) hsync: 93.76 kHz; pclk: 179.26 MHz ModeLine "1400x1050" 179.26 1400 1504 1656 1912 1050 1051 1054 1103 -HSync +Vsync # 1400x1050 @ 100.00 Hz (GTF) hsync: 111.20 kHz; pclk: 214.39 MHz ModeLine "1400x1050" 214.39 1400 1512 1664 1928 1050 1051 1054 1112 -HSync +Vsync # 1600x1200 @ 100.00 Hz (GTF) hsync: 127.10 kHz; pclk: 280.64 MHz ModeLine "1600x1200" 280.64 1600 1728 1904 2208 1200 1201 1204 1271 -HSync +Vsync # 1680x1050 (Notebook) ModeLine "1680x1050" 154.2 1680 1712 2296 2328 1050 1071 1081 1103 # 1920x1200 @ 60.00 Hz (GTF) hsync: 74.52; pclk: 193.16 MHz ModeLine "1920x1200" 193.16 1920 2048 2256 2592 1200 1201 1204 1242 -HSync +HSync EndSection Section "Device" ### Available Driver options are:- # sw_cursor is needed for some ati and radeon cards #Option "sw_cursor" #Option "hw_cursor" #Option "NoAccel" #Option "ShowCache" #Option "ShadowFB" #Option "UseFBDev" #Option "Rotate" Identifier "Card0" # The following line is auto-generated by KNOPPIX mkxf86config Driver "nvidia" Option "XvmcUsesTextures" "false" Option "UseEvents" "true" VendorName "All" BoardName "All" # BusID "PCI:1:0:0" #Option "NVAGP" "2" EndSection Section "Screen" Identifier "Screen0" Device "Card0" Monitor "Monitor0" DefaultColorDepth 24 SubSection "Display" Depth 1 Modes "1280x1024" "1152x864" "1024x768" "800x600" "640x480" EndSubSection SubSection "Display" Depth 4 Modes "1280x1024" "1152x864" "1024x768" "800x600" "640x480" EndSubSection SubSection "Display" Depth 8 Modes "1280x1024" "1152x864" "1024x768" "800x600" "640x480" EndSubSection SubSection "Display" Depth 15 Modes "1280x1024" "1152x864" "1024x768" "800x600" "640x480" EndSubSection SubSection "Display" Depth 16 Modes "1680x1050" "1280x1024" "1152x864" "1024x768" "800x600" "640x480" EndSubSection SubSection "Display" Depth 24 # Modes "1680x1050" "720p" "1280x1024" "1152x864" "1024x768" "800x600" "640x480" Modes "1680x1050" "720p" "1280x1024" EndSubSection SubSection "Display" Depth 32 Modes "1680x1050" "1280x1024" # Modes "1680x1050" "1280x1024" "1152x864" "1024x768" "800x600" "640x480" EndSubSection EndSection Section "DRI" Mode 0666 EndSection # Needed for XvMC with some Nvidia boards and drivers #Section "Extensions" # Option "Composite" "Disabled" #EndSection |
Author: | ceenvee703 [ Thu Feb 26, 2009 9:49 pm ] |
Post subject: | |
Two things: 1) Any time I see an xorg.conf like that I strongly recommend either deleting or commenting out EVERY EVERY EVERY line that has nothing to do with the resolution and bitdepth you want. I also recommend getting rid of multiple resolutions per line, particularly if you know you only want to run at the TV's native resolution. So in your case I'd get rid of, or comment out, all SubSection "Display" items with a bit depth other than the one you want (24). Even with "DefaultColorDepth" set to 24, I would just do that to be sure. And on your "Modes" line, get rid of all resolutions other than "1680x1050" My guess is that it's running at some odd bit depth but that's just a guess. My second thing was going to be to use Nvidia macros to output a standard HDTV resolution like 1280x720 or 1920x1080, but if you really want to run at your TV's default resolution, you probably won't want to do that (although it will work just like any Blu-Ray player or set-top box would work with your TV). I'd also recommend checking out the xorg logs on your Ubuntu setup and see if you can compare what's going on. The stuff where it finally says what resolution it's running at is way at the end. |
Author: | graysky [ Fri Feb 27, 2009 3:42 am ] |
Post subject: | |
Yeah, the ubuntu logs show 1680x1050 as do my KM R5.5 logs. I modified my xorg.conf as you suggested, but the results are the same wen viewing videos. Here is my modded /etc/X11/xorg.conf Code: Section "ServerLayout"
Identifier "Layout0" Screen 0 "Screen0" 0 0 InputDevice "Keyboard0" "CoreKeyboard" InputDevice "Mouse0" "CorePointer" EndSection Section "Files" RgbPath "/usr/lib/X11/rgb" EndSection Section "Module" Load "dbe" Load "extmod" Load "type1" Load "freetype" Load "glx" EndSection Section "ServerFlags" Option "Xinerama" "0" EndSection Section "InputDevice" # generated from default Identifier "Mouse0" Driver "mouse" Option "Protocol" "auto" Option "Device" "/dev/psaux" Option "Emulate3Buttons" "no" Option "ZAxisMapping" "4 5" EndSection Section "InputDevice" # generated from default Identifier "Keyboard0" Driver "kbd" EndSection Section "Monitor" # HorizSync source: edid, VertRefresh source: edid Identifier "Monitor0" VendorName "Unknown" ModelName "SAMSUNG" HorizSync 26.0 - 68.0 VertRefresh 23.0 - 61.0 Option "DPMS" Option "UseEdidDpi" "FALSE" Option "DPI" "100 x 100" EndSection Section "Device" Identifier "Videocard0" Driver "nvidia" VendorName "NVIDIA Corporation" BoardName "GeForce 8400 GS" EndSection Section "Screen" Identifier "Screen0" Device "Videocard0" Monitor "Monitor0" DefaultDepth 24 Option "metamodes" "1680x1050 +0+0" SubSection "Display" Depth 24 Modes "1680x1050" EndSubSection EndSection Do you have an HDTV? I can upload a clip of this avi that looks like crap for you guys to see on your systems. |
Author: | alien [ Fri Feb 27, 2009 4:03 am ] |
Post subject: | |
As mentioned earlier, it sounds like deinterlacing artifacts. Bob2x should solve this. A few things I learned about bob2x with my nvidia card: 1. Disable QT. This made a huge difference. 2. Do not align the display to the screen. Set the stretch and screen offsets in the setup all to 0. Setting them to non-zero confused bob2x and the whole screen started wiggling. 3. Remove all the playback profiles except the one you have set up with bob2x. Not exactly necessary, but useful to make sure you are using the one you expect. You can add new ones later and test once it is working. 4. Don't use XVMC. Things have probably improved since I tried it, but I found it caused nothing but problems. Especially with the OSD. Comparing to a DVD player on the same TV is probably a good test. I now have something that looks almost indistinguishable on my 28' LCD from the DVD player. I say almost as I do see some minor mottling in mostly black scenes that seem to be due to colour depth. I haven't fixed this, but rarely notice it. |
Author: | Martian [ Fri Feb 27, 2009 9:12 am ] |
Post subject: | |
Have you tried nvidia-settings or whatever that command is to get to the Nvidia controls. It could be that something is messed up in there. Sorry I don't have the exact command but I know it's here on the forums. |
Page 1 of 2 | All times are UTC - 6 hours |
Powered by phpBB® Forum Software © phpBB Group http://www.phpbb.com/ |