View unanswered posts    View active topics

All times are UTC - 6 hours





Post new topic Reply to topic  [ 14 posts ] 
Print view Previous topic   Next topic  
Author Message
Search for:
PostPosted: Sun May 09, 2010 3:43 am 
Offline
Joined: Tue Mar 22, 2005 9:18 pm
Posts: 1422
Location: Brisbane, Queensland, Australia
Hi folks,

I have been running a 6.02 box via DVI2HDMI to my 55" Samsung LED TV and when I installed it, the default X.org config seemed to work out of the box with the TV saying when I start up mythfrontend that the resolution is 1920x1080@60Hz.

Now this seems fine, however when I watch Blu-Rays on my 46" LCD Sony they look awesome, but when I watch Hi-Res stuff on the Samsung it looks good, but not great.

It would appear obvious that I need somehow adjust my Xorg.conf file, but where to start. Here is what is picked up by X when it starts:
Code:
(--) May 06 15:31:19 NVIDIA(0): Connected display device(s) on GeForce 8400 GS at PCI:2:0:0:
(--) May 06 15:31:19 NVIDIA(0):     SAMSUNG (DFP-0)
(--) May 06 15:31:19 NVIDIA(0): SAMSUNG (DFP-0): 165.0 MHz maximum pixel clock
(--) May 06 15:31:19 NVIDIA(0): SAMSUNG (DFP-0): Internal Single Link TMDS
(--) May 06 15:31:19 NVIDIA(0): SAMSUNG (DFP-0): Native FlatPanel Scaling is supported
(--) May 06 15:31:19 NVIDIA(0): SAMSUNG (DFP-0): DFP modes are not limited to 60 Hz refresh
(--) May 06 15:31:19 NVIDIA(0):     rate
(--) May 06 15:31:19 NVIDIA(0): SAMSUNG (DFP-0): DFP is not internal to notebook
(--) May 06 15:31:19 NVIDIA(0):
(--) May 06 15:31:19 NVIDIA(0): --- EDID for SAMSUNG (DFP-0) ---
(--) May 06 15:31:19 NVIDIA(0): EDID Version                 : 1.3
(--) May 06 15:31:19 NVIDIA(0): Manufacturer                 : SAM
(--) May 06 15:31:19 NVIDIA(0): Monitor Name                 : SAMSUNG
(--) May 06 15:31:19 NVIDIA(0): Product ID                   : 1289
(--) May 06 15:31:19 NVIDIA(0): 32-bit Serial Number         : 1
(--) May 06 15:31:19 NVIDIA(0): Serial Number String         :
(--) May 06 15:31:19 NVIDIA(0): Manufacture Date             : 2008, week 48
(--) May 06 15:31:19 NVIDIA(0): DPMS Capabilities            :
(--) May 06 15:31:19 NVIDIA(0): Prefer first detailed timing : Yes
(--) May 06 15:31:19 NVIDIA(0): Supports GTF                 : No
(--) May 06 15:31:19 NVIDIA(0): Maximum Image Size           : 160mm x 90mm
(--) May 06 15:31:19 NVIDIA(0): Valid HSync Range            : 26.0 kHz - 81.0 kHz
(--) May 06 15:31:19 NVIDIA(0): Valid VRefresh Range         : 24 Hz - 75 Hz
(--) May 06 15:31:19 NVIDIA(0): EDID maximum pixel clock     : 230.0 MHz
(--) May 06 15:31:19 NVIDIA(0):
(--) May 06 15:31:19 NVIDIA(0): Established Timings:
(--) May 06 15:31:19 NVIDIA(0):   640  x 480  @ 60 Hz
(--) May 06 15:31:19 NVIDIA(0):   640  x 480  @ 72 Hz
(--) May 06 15:31:19 NVIDIA(0):   640  x 480  @ 75 Hz
(--) May 06 15:31:19 NVIDIA(0):   800  x 600  @ 60 Hz
(--) May 06 15:31:19 NVIDIA(0):   800  x 600  @ 72 Hz
(--) May 06 15:31:19 NVIDIA(0):   800  x 600  @ 75 Hz
(--) May 06 15:31:19 NVIDIA(0):   1024 x 768  @ 60 Hz
(--) May 06 15:31:19 NVIDIA(0):   1024 x 768  @ 70 Hz
(--) May 06 15:31:19 NVIDIA(0):   1024 x 768  @ 75 Hz
(--) May 06 15:31:19 NVIDIA(0):   1280 x 1024 @ 75 Hz
(--) May 06 15:31:19 NVIDIA(0):
(--) May 06 15:31:19 NVIDIA(0): Standard Timings:
(--) May 06 15:31:19 NVIDIA(0):   1152 x 864  @ 75 Hz
(--) May 06 15:31:19 NVIDIA(0):   1280 x 800  @ 60 Hz
(--) May 06 15:31:19 NVIDIA(0):   1280 x 960  @ 60 Hz
(--) May 06 15:31:19 NVIDIA(0):   1280 x 1024 @ 60 Hz
(--) May 06 15:31:19 NVIDIA(0):   1440 x 900  @ 60 Hz
(--) May 06 15:31:19 NVIDIA(0):   1440 x 900  @ 75 Hz
(--) May 06 15:31:19 NVIDIA(0):   1680 x 1050 @ 60 Hz
(--) May 06 15:31:19 NVIDIA(0):
(--) May 06 15:31:19 NVIDIA(0): Detailed Timings:
(--) May 06 15:31:19 NVIDIA(0):   1920 x 1080 @ 60 Hz
(--) May 06 15:31:19 NVIDIA(0):     Pixel Clock      : 148.50 MHz
(--) May 06 15:31:19 NVIDIA(0):     HRes, HSyncStart : 1920, 2008
(--) May 06 15:31:19 NVIDIA(0):     HSyncEnd, HTotal : 2052, 2200
(--) May 06 15:31:19 NVIDIA(0):     VRes, VSyncStart : 1080, 1084
(--) May 06 15:31:19 NVIDIA(0):     VSyncEnd, VTotal : 1089, 1125
(--) May 06 15:31:19 NVIDIA(0):     H/V Polarity     : +/+
(--) May 06 15:31:19 NVIDIA(0):   1360 x 768  @ 60 Hz
(--) May 06 15:31:19 NVIDIA(0):     Pixel Clock      : 85.50 MHz
(--) May 06 15:31:19 NVIDIA(0):     HRes, HSyncStart : 1360, 1424
(--) May 06 15:31:19 NVIDIA(0):     HSyncEnd, HTotal : 1536, 1792
(--) May 06 15:31:19 NVIDIA(0):     VRes, VSyncStart : 768, 771
(--) May 06 15:31:19 NVIDIA(0):     VSyncEnd, VTotal : 777, 795
(--) May 06 15:31:19 NVIDIA(0):     H/V Polarity     : +/+
(--) May 06 15:31:19 NVIDIA(0):   1280 x 720  @ 60 Hz
(--) May 06 15:31:19 NVIDIA(0):     Pixel Clock      : 74.25 MHz
(--) May 06 15:31:19 NVIDIA(0):     HRes, HSyncStart : 1280, 1390
(--) May 06 15:31:19 NVIDIA(0):     HSyncEnd, HTotal : 1430, 1650
(--) May 06 15:31:19 NVIDIA(0):     VRes, VSyncStart : 720, 725
(--) May 06 15:31:19 NVIDIA(0):     VSyncEnd, VTotal : 730, 750
(--) May 06 15:31:19 NVIDIA(0):     H/V Polarity     : +/+
(--) May 06 15:31:19 NVIDIA(0):   1280 x 720  @ 50 Hz
(--) May 06 15:31:19 NVIDIA(0):     Pixel Clock      : 74.25 MHz
(--) May 06 15:31:19 NVIDIA(0):     HRes, HSyncStart : 1280, 1720
(--) May 06 15:31:19 NVIDIA(0):     HSyncEnd, HTotal : 1760, 1980
(--) May 06 15:31:19 NVIDIA(0):     VRes, VSyncStart : 720, 725
(--) May 06 15:31:19 NVIDIA(0):     VSyncEnd, VTotal : 730, 750
(--) May 06 15:31:19 NVIDIA(0):     H/V Polarity     : +/+
(--) May 06 15:31:19 NVIDIA(0):   1920 x 1080 @ 50 Hz
(--) May 06 15:31:19 NVIDIA(0):     Pixel Clock      : 74.25 MHz
(--) May 06 15:31:19 NVIDIA(0):     HRes, HSyncStart : 1920, 2448
(--) May 06 15:31:19 NVIDIA(0):     HSyncEnd, HTotal : 2492, 2640
(--) May 06 15:31:19 NVIDIA(0):     VRes, VSyncStart : 1080, 1084
(--) May 06 15:31:19 NVIDIA(0):     VSyncEnd, VTotal : 1094, 1124
(--) May 06 15:31:19 NVIDIA(0):     H/V Polarity     : +/+
(--) May 06 15:31:19 NVIDIA(0):     Extra            : Interlaced
(--) May 06 15:31:19 NVIDIA(0):
(--) May 06 15:31:19 NVIDIA(0): CEA-861B Timings:
(--) May 06 15:31:19 NVIDIA(0):   1920 x 1080 @ 60 Hz
(--) May 06 15:31:19 NVIDIA(0):     Pixel Clock      : 148.35 MHz
(--) May 06 15:31:19 NVIDIA(0):     HRes, HSyncStart : 1920, 2008
(--) May 06 15:31:19 NVIDIA(0):     HSyncEnd, HTotal : 2052, 2200
(--) May 06 15:31:19 NVIDIA(0):     VRes, VSyncStart : 1080, 1084
(--) May 06 15:31:19 NVIDIA(0):     VSyncEnd, VTotal : 1089, 1125
(--) May 06 15:31:19 NVIDIA(0):     H/V Polarity     : +/+
(--) May 06 15:31:19 NVIDIA(0):     CEA Format       : 16
(--) May 06 15:31:19 NVIDIA(0):   1920 x 1080 @ 50 Hz
(--) May 06 15:31:19 NVIDIA(0):     Pixel Clock      : 148.50 MHz
(--) May 06 15:31:19 NVIDIA(0):     HRes, HSyncStart : 1920, 2448
(--) May 06 15:31:19 NVIDIA(0):     HSyncEnd, HTotal : 2492, 2640
(--) May 06 15:31:19 NVIDIA(0):     VRes, VSyncStart : 1080, 1084
(--) May 06 15:31:19 NVIDIA(0):     VSyncEnd, VTotal : 1089, 1125
(--) May 06 15:31:19 NVIDIA(0):     H/V Polarity     : +/+
(--) May 06 15:31:19 NVIDIA(0):     CEA Format       : 31
(--) May 06 15:31:19 NVIDIA(0):   1280 x 720  @ 60 Hz
(--) May 06 15:31:19 NVIDIA(0):     Pixel Clock      : 74.18 MHz
(--) May 06 15:31:19 NVIDIA(0):     HRes, HSyncStart : 1280, 1390
(--) May 06 15:31:19 NVIDIA(0):     HSyncEnd, HTotal : 1430, 1650
(--) May 06 15:31:19 NVIDIA(0):     VRes, VSyncStart : 720, 725
(--) May 06 15:31:19 NVIDIA(0):     VSyncEnd, VTotal : 730, 750
(--) May 06 15:31:19 NVIDIA(0):     H/V Polarity     : +/+
(--) May 06 15:31:19 NVIDIA(0):     CEA Format       : 4
(--) May 06 15:31:19 NVIDIA(0):   1280 x 720  @ 50 Hz
(--) May 06 15:31:19 NVIDIA(0):     Pixel Clock      : 74.25 MHz
(--) May 06 15:31:19 NVIDIA(0):     HRes, HSyncStart : 1280, 1720
(--) May 06 15:31:19 NVIDIA(0):     HSyncEnd, HTotal : 1760, 1980
(--) May 06 15:31:19 NVIDIA(0):     VRes, VSyncStart : 720, 725
(--) May 06 15:31:19 NVIDIA(0):     VSyncEnd, VTotal : 730, 750
(--) May 06 15:31:19 NVIDIA(0):     H/V Polarity     : +/+
(--) May 06 15:31:19 NVIDIA(0):     CEA Format       : 19
(--) May 06 15:31:19 NVIDIA(0):   1920 x 1080 @ 60 Hz
(--) May 06 15:31:19 NVIDIA(0):     Pixel Clock      : 74.18 MHz
(--) May 06 15:31:19 NVIDIA(0):     HRes, HSyncStart : 1920, 2008
(--) May 06 15:31:19 NVIDIA(0):     HSyncEnd, HTotal : 2052, 2200
(--) May 06 15:31:19 NVIDIA(0):     VRes, VSyncStart : 1080, 1084
(--) May 06 15:31:19 NVIDIA(0):     VSyncEnd, VTotal : 1094, 1124
(--) May 06 15:31:19 NVIDIA(0):     H/V Polarity     : +/+
(--) May 06 15:31:19 NVIDIA(0):     Extra            : Interlaced
(--) May 06 15:31:19 NVIDIA(0):     CEA Format       : 5
(--) May 06 15:31:19 NVIDIA(0):   1920 x 1080 @ 50 Hz
(--) May 06 15:31:19 NVIDIA(0):     Pixel Clock      : 74.25 MHz
(--) May 06 15:31:19 NVIDIA(0):     HRes, HSyncStart : 1920, 2448
(--) May 06 15:31:19 NVIDIA(0):     HSyncEnd, HTotal : 2492, 2640
(--) May 06 15:31:19 NVIDIA(0):     VRes, VSyncStart : 1080, 1084
(--) May 06 15:31:19 NVIDIA(0):     VSyncEnd, VTotal : 1094, 1124
(--) May 06 15:31:19 NVIDIA(0):     H/V Polarity     : +/+
(--) May 06 15:31:19 NVIDIA(0):     Extra            : Interlaced
(--) May 06 15:31:19 NVIDIA(0):     CEA Format       : 20
(--) May 06 15:31:19 NVIDIA(0):   720  x 480  @ 60 Hz
(--) May 06 15:31:19 NVIDIA(0):     Pixel Clock      : 27.00 MHz
(--) May 06 15:31:19 NVIDIA(0):     HRes, HSyncStart : 720, 736
(--) May 06 15:31:19 NVIDIA(0):     HSyncEnd, HTotal : 798, 858
(--) May 06 15:31:19 NVIDIA(0):     VRes, VSyncStart : 480, 489
(--) May 06 15:31:19 NVIDIA(0):     VSyncEnd, VTotal : 495, 525
(--) May 06 15:31:19 NVIDIA(0):     H/V Polarity     : -/-
(--) May 06 15:31:19 NVIDIA(0):     CEA Format       : 3
(--) May 06 15:31:19 NVIDIA(0):   720  x 576  @ 50 Hz
(--) May 06 15:31:19 NVIDIA(0):     Pixel Clock      : 27.00 MHz
(--) May 06 15:31:19 NVIDIA(0):     HRes, HSyncStart : 720, 732
(--) May 06 15:31:19 NVIDIA(0):     HSyncEnd, HTotal : 796, 864
(--) May 06 15:31:19 NVIDIA(0):     VRes, VSyncStart : 576, 581
(--) May 06 15:31:19 NVIDIA(0):     VSyncEnd, VTotal : 586, 625
(--) May 06 15:31:19 NVIDIA(0):     H/V Polarity     : -/-
(--) May 06 15:31:19 NVIDIA(0):     CEA Format       : 18
(--) May 06 15:31:19 NVIDIA(0):   1920 x 1080 @ 24 Hz
(--) May 06 15:31:19 NVIDIA(0):     Pixel Clock      : 74.16 MHz
(--) May 06 15:31:19 NVIDIA(0):     HRes, HSyncStart : 1920, 2558
(--) May 06 15:31:19 NVIDIA(0):     HSyncEnd, HTotal : 2602, 2750
(--) May 06 15:31:19 NVIDIA(0):     VRes, VSyncStart : 1080, 1084
(--) May 06 15:31:19 NVIDIA(0):     VSyncEnd, VTotal : 1089, 1125
(--) May 06 15:31:19 NVIDIA(0):     H/V Polarity     : +/+
(--) May 06 15:31:19 NVIDIA(0):     CEA Format       : 32
(--) May 06 15:31:19 NVIDIA(0):   1920 x 1080 @ 25 Hz
(--) May 06 15:31:19 NVIDIA(0):     Pixel Clock      : 74.25 MHz
(--) May 06 15:31:19 NVIDIA(0):     HRes, HSyncStart : 1920, 2448
(--) May 06 15:31:19 NVIDIA(0):     HSyncEnd, HTotal : 2492, 2640
(--) May 06 15:31:19 NVIDIA(0):     VRes, VSyncStart : 1080, 1084
(--) May 06 15:31:19 NVIDIA(0):     VSyncEnd, VTotal : 1089, 1125
(--) May 06 15:31:19 NVIDIA(0):     H/V Polarity     : +/+
(--) May 06 15:31:19 NVIDIA(0):     CEA Format       : 33
(--) May 06 15:31:19 NVIDIA(0):   1920 x 1080 @ 30 Hz
(--) May 06 15:31:19 NVIDIA(0):     Pixel Clock      : 89.01 MHz
(--) May 06 15:31:19 NVIDIA(0):     HRes, HSyncStart : 1920, 2448
(--) May 06 15:31:19 NVIDIA(0):     HSyncEnd, HTotal : 2492, 2640
(--) May 06 15:31:19 NVIDIA(0):     VRes, VSyncStart : 1080, 1084
(--) May 06 15:31:19 NVIDIA(0):     VSyncEnd, VTotal : 1089, 1125
(--) May 06 15:31:19 NVIDIA(0):     H/V Polarity     : +/+
(--) May 06 15:31:19 NVIDIA(0):     CEA Format       : 34
(--) May 06 15:31:19 NVIDIA(0):
(--) May 06 15:31:19 NVIDIA(0):
(--) May 06 15:31:19 NVIDIA(0):
(--) May 06 15:31:19 NVIDIA(0):
(--) May 06 15:31:19 NVIDIA(0): Raw EDID bytes:
(--) May 06 15:31:19 NVIDIA(0):
(--) May 06 15:31:19 NVIDIA(0):   00 ff ff ff ff ff ff 00  4c 2d 09 05 01 00 00 00
(--) May 06 15:31:19 NVIDIA(0):   30 12 01 03 80 10 09 78  0a ee 91 a3 54 4c 99 26
(--) May 06 15:31:19 NVIDIA(0):   0f 50 54 bd ef 80 71 4f  81 00 81 40 81 80 95 00
(--) May 06 15:31:19 NVIDIA(0):   95 0f b3 00 01 01 02 3a  80 18 71 38 2d 40 58 2c
(--) May 06 15:31:19 NVIDIA(0):   45 00 a0 5a 00 00 00 1e  66 21 50 b0 51 00 1b 30
(--) May 06 15:31:19 NVIDIA(0):   40 70 36 00 a0 5a 00 00  00 1e 00 00 00 fd 00 18
(--) May 06 15:31:19 NVIDIA(0):   4b 1a 51 17 00 0a 20 20  20 20 20 20 00 00 00 fc
(--) May 06 15:31:19 NVIDIA(0):   00 53 41 4d 53 55 4e 47  0a 20 20 20 20 20 01 6f
(--) May 06 15:31:19 NVIDIA(0):   02 03 27 f1 4b 90 1f 04  13 05 14 03 12 20 21 22
(--) May 06 15:31:19 NVIDIA(0):   23 09 07 07 83 01 00 00  e2 00 0f e3 05 03 01 67
(--) May 06 15:31:19 NVIDIA(0):   03 0c 00 10 00 b8 2d 01  1d 00 72 51 d0 1e 20 6e
(--) May 06 15:31:19 NVIDIA(0):   28 55 00 a0 5a 00 00 00  1e 01 1d 00 bc 52 d0 1e
(--) May 06 15:31:19 NVIDIA(0):   20 b8 28 55 40 a0 5a 00  00 00 1e 01 1d 80 18 71
(--) May 06 15:31:19 NVIDIA(0):   1c 16 20 58 2c 25 00 a0  5a 00 00 00 9e 01 1d 80
(--) May 06 15:31:19 NVIDIA(0):   d0 72 1c 16 20 10 2c 25  80 a0 5a 00 00 00 9e 00
(--) May 06 15:31:19 NVIDIA(0):   00 00 00 00 00 00 00 00  00 00 00 00 00 00 00 1d
(--) May 06 15:31:19 NVIDIA(0):
(--) May 06 15:31:19 NVIDIA(0): --- End of EDID for SAMSUNG (DFP-0) ---


Then it goes through validating those modes and finally announces (in the log):
Code:
(II) May 06 15:31:20 NVIDIA(0): Requested modes:
(II) May 06 15:31:20 NVIDIA(0):     "nvidia-auto-select"
(II) May 06 15:31:20 NVIDIA(0): Validated modes:
(II) May 06 15:31:20 NVIDIA(0): MetaMode "nvidia-auto-select":
(II) May 06 15:31:20 NVIDIA(0):     Bounding Box: [0, 0, 1920, 1080]
(II) May 06 15:31:20 NVIDIA(0):     SAMSUNG (DFP-0): "nvidia-auto-select"
(II) May 06 15:31:20 NVIDIA(0):         Size          : 1920 x 1080
(II) May 06 15:31:20 NVIDIA(0):         Offset        : +0 +0
(II) May 06 15:31:20 NVIDIA(0):         Panning Domain: @ 1920 x 1080
(II) May 06 15:31:20 NVIDIA(0):         Position      : [0, 0, 1920, 1080]
(II) May 06 15:31:20 NVIDIA(0): Virtual screen size determined to be 1920 x 1080


Whilst I have played with my Xorg.conf file before I have never had to do it for modes, so this is new teritory for me. My Samsung is a 100Hz TV so I am wondering why this was not picked up in the edid scan from the nvidia card. and As our TV here is Oz works on 50hz that may be why it doesn't always look the best.

Could anyone steer me in the right direction on how to go about getting the best out of MythTV and my big screen TV.

Thanks

_________________
Girkers


Top
 Profile  
 
 Post subject:
PostPosted: Sun May 09, 2010 11:02 am 
Offline
Joined: Fri May 21, 2004 11:55 pm
Posts: 1206
Location: Silicon Valley, CA
You didn't say (or I didn't see it) -- are you connected by HDMI cable? I'm pretty sure the analog inputs (component video) are not able to go faster than 60Hz.

As an aside, did you know the Samsung "LED" tv set is really an LCD set with an LED backlight? I just think it's odd that they advertise it as an "LED" tv set. But it's a terrific set regardless!

_________________
Do you code to live, or live to code?
Search LinHES forum through Google


Top
 Profile  
 
 Post subject:
PostPosted: Sun May 09, 2010 3:52 pm 
Offline
Joined: Mon May 10, 2004 8:08 pm
Posts: 1891
Location: Adelaide, Australia
Since the australian DVB broadcasts are PAL they have a field rate of 50 Hz. You should ensure that your modeline is a 50 Hz modeline too to avoid subtle shuddering.

This probably goes without saying, but are you using a 2x deinterlacer. That is also very important.

My last thought is: does the TV do motion compensation? Does it do it on all inputs? What does the TV report as the modeline from your blueray player? (most films are 24fps progressive).


Top
 Profile  
 
 Post subject:
PostPosted: Sun May 09, 2010 6:04 pm 
Offline
Joined: Tue Mar 22, 2005 9:18 pm
Posts: 1422
Location: Brisbane, Queensland, Australia
Liv2Cod I did say in my OP that I am using DVI to HDMI to connect my myth box to my TV.

Greg, I will have to check with deinterlacer I am using as yes I do get some funny looking things especially when watching HD sport. My blu-ray player does run at 24P when the movies are playing.

So am I still looking for how to set the mode line for my TV, thanks.

_________________
Girkers


Top
 Profile  
 
 Post subject:
PostPosted: Mon May 10, 2010 3:42 am 
Offline
Joined: Mon May 10, 2004 8:08 pm
Posts: 1891
Location: Adelaide, Australia
Copy the details from the modeline for 1920x1080@50 into a line like this in the section of /etc/X11./xorg.conf:

Code:
    ModeLine       "1920x1080_50" 148.50 1920 2448 2492 2640 1080 1084 1089 1125 +hsync +vsync


Put this option in the "Screen" section:
Code:
    Option         "ExactModeTimingsDVI" "True"


and make the "Display" subsection of the screen section look like this:

Code:
    SubSection     "Display"
        Depth       24
        Modes      "1920x1080_50"
    EndSubSection


Also make sure you are using the "just scan" setting on your TV for 1:1 pixel mapping.


Top
 Profile  
 
 Post subject:
PostPosted: Mon May 10, 2010 5:40 am 
Offline
Joined: Tue Mar 22, 2005 9:18 pm
Posts: 1422
Location: Brisbane, Queensland, Australia
Thanks Greg,

I will try your settings out as I did find today that I could just add the Modes and use one of the modelines the system automatically detects. So I tried one of the 50Hz ones but my TV still thinks it is running at 60, even though the Xorg log confirms it is running at 50.

I will try your Modeline and see if I can find that setting you mention and report back.

Thanks for all the help

_________________
Girkers


Top
 Profile  
 
 Post subject:
PostPosted: Mon May 10, 2010 6:51 pm 
Offline
Joined: Thu Mar 25, 2004 11:00 am
Posts: 9551
Location: Arlington, MA
You may want to look at my write ups about setting up my HDTV. They contain some clues about getting the X server to do what you want. For example you could restrict your VertRefresh to 50Hz +/- 1 which would filter out any non 50Hz modes... You can also fiddle with the ModeValidation options like I did.

http://knoppmyth.net/phpBB2/viewtopic.php?t=19668

http://knoppmyth.net/phpBB2/viewtopic.php?t=19913


Top
 Profile  
 
 Post subject:
PostPosted: Tue May 11, 2010 12:30 am 
Offline
Joined: Tue Mar 22, 2005 9:18 pm
Posts: 1422
Location: Brisbane, Queensland, Australia
I had tried put a modeline in similar to what Greg had given me, however I could not transcribe it properly. When I put Greg's line in (that is when I had found my errors) and restarted X it looks great.

I couldn't find the "just scan" setting but there was a similar setting but the name eludes me at the moment.

Looking good, still curious though why when I watch a Blu-ray at 24p it looks so much different to a HD picture on my Mythbox????

Thanks

_________________
Girkers


Top
 Profile  
 
 Post subject:
PostPosted: Tue May 11, 2010 1:51 am 
Offline
Joined: Mon Jun 21, 2004 5:28 am
Posts: 700
Location: Germany
I see you have a nvidia card.

I suggest you use nvidia-settings to try the different modes available rather than editing modelines directly.

A few things to consider:

1. When done, select the mode explicity (not auto) in nvidia-settings. This way X will start even if the TV is off (no EDID).

2. In my bravia TV, selecting 1080p causes he TV to overscan which is annoying. I get a better pictures if I select one of the inherent resolutions of the screen.

3. Check your frontend settings to make sure you aren't inadvertently changing the screensize (no positioning or resizing as you might do if the TV is overscanning).

4. If you are using VDPAU, you might have to disable composite (google VDPAU composite). This might be fixed now....

5. 100hz TVs generally do not accept 100hz input. They still only accept 50/60 and then build a frame to add between them.

_________________
ASUS AT3N7A-I (Atom 330)
TBS 8922 PCI (DVB-S2)


Top
 Profile  
 
 Post subject:
PostPosted: Tue May 11, 2010 1:59 am 
Offline
Joined: Tue Mar 22, 2005 9:18 pm
Posts: 1422
Location: Brisbane, Queensland, Australia
1. I have done this thanks to Greg's help

2. I don't select the resolution, it picks it up automatically and I told the TV to just use what it gets as the picture.

3. None of that is set.

4. I am using VDPAU and in my googling I did see someone had done this but it wasn't explained. I just did a quick look and at http://www.mythtv.org/wiki/VDPAU found that this option helps prevent tearing and blurring especially of the background (which I get). I have now added it as per the wiki.

5. I have set it at 50Hz and as again suggested by Greg using the VDPAU Normal profile with has the main Deinterlacer 2x.

_________________
Girkers


Top
 Profile  
 
 Post subject:
PostPosted: Tue May 11, 2010 2:49 am 
Offline
Joined: Mon Jun 21, 2004 5:28 am
Posts: 700
Location: Germany
Girkers wrote:
2. I don't select the resolution, it picks it up automatically and I told the TV to just use what it gets as the picture.


Sorry, I didn't word that very well. I set nvidia to use the largest native resolution the TV supported instead of 1080i to prevent the TV from overscanning. Many TVs manipulate the picture when they receive exactly 1080i or 720p. Sometimes for the good, sometimes for the bad. If you pick a resolution that exactly matches the number of pixels on the TV, you can often by-pass this manipulation if it is a problem (a 1080i TV doesn't necessarily have 1080 rows of pixels).

It my case, it was obvious as the TV displays the resolution and the overscan was clear. I suggest you check how the TV is handling the edges of the picture on the various resolutions. You might like or not-like it.

_________________
ASUS AT3N7A-I (Atom 330)
TBS 8922 PCI (DVB-S2)


Top
 Profile  
 
 Post subject:
PostPosted: Tue May 11, 2010 8:37 am 
Offline
Joined: Thu Oct 19, 2006 11:21 am
Posts: 51
Hi,

I have a Samsung which does 1080p, so, I set it up not using interlace. I think it should output one field of a 1080i frame, then 1/60th sec. later, output the other field. It seems to look fine, with no interlacing. And shouldn't this work for 780P as well?

Am I missing something? It would seem to me if the lcd panel does 1080P, interlace is not needed. Why use a 2x deinterlacer? Thanks.


Top
 Profile  
 
 Post subject:
PostPosted: Tue May 11, 2010 9:04 am 
Offline
Joined: Mon Jun 21, 2004 5:28 am
Posts: 700
Location: Germany
luxluthor wrote:
Hi,

I have a Samsung which does 1080p, so, I set it up not using interlace. I think it should output one field of a 1080i frame, then 1/60th sec. later, output the other field. It seems to look fine, with no interlacing. And shouldn't this work for 780P as well?

Am I missing something? It would seem to me if the lcd panel does 1080P, interlace is not needed. Why use a 2x deinterlacer? Thanks.


Deinterlacing is required to convert 1080i (or any interlaced source) to 1080p (or any non-interlaced output). A 1080i "frame" only has 540 lines. Deinterlacing fills in the other 540 lines in a way that tries to keep motion smooth.

To make things even more complicated.... even if both the source and output is interlaced, you will probably want to de-interlace because it is almost impossible to match source and output interlacing properly.

If the source is non-interlaced, mythtv automatically disables de-interlacing as it isn't needed.

_________________
ASUS AT3N7A-I (Atom 330)
TBS 8922 PCI (DVB-S2)


Top
 Profile  
 
 Post subject:
PostPosted: Mon May 17, 2010 9:13 pm 
Offline
Joined: Tue Mar 22, 2005 9:18 pm
Posts: 1422
Location: Brisbane, Queensland, Australia
luxluthor wrote:
Why use a 2x deinterlacer? Thanks.


The reason for this is that the signal from my Mythbox is 50Hz, my TV can handle 100Hz, so by using a 2x deinterlacer I am effectively doubling my 50Hz signal to 100Hz.

I must say it has made a HUGE difference configuring this properly, whilst I may need to adjust the colour settings a little, the picture quality itself is awesome and with the State of Origin (sort of like the Pro Bowl) on in just over a week I am stoked.

Thanks again everyone for your help.

_________________
Girkers


Top
 Profile  
 

Display posts from previous:  Sort by  
Post new topic Reply to topic  [ 14 posts ] 


All times are UTC - 6 hours




Who is online

Users browsing this forum: No registered users and 115 guests


You cannot post new topics in this forum
You cannot reply to topics in this forum
You cannot edit your posts in this forum
You cannot delete your posts in this forum
You cannot post attachments in this forum

Jump to:  
Powered by phpBB® Forum Software © phpBB Group

Theme Created By ceyhansuyu