This occurs inside the TV itself, and the TV has no method (without DVI or HDMI 2.0) of taking in 120Hz signals.
Now whether it could take a 720p (about half the pixels of 1080p) 120Hz signal on whatever version of HDMI it is running, is another topic altogether. Some TV's do, some don't.
]]>I'm really curious, now, to see what 120Hz would look like (vs the 60Hz HDMI), but I guess that's not to be! :-[
You should be able to test that with half the resolution (or I should write throughput). HDMI is digital so the throughput is the limit. The question is if hardware will accept such format, there might be protocol or other limitations I am not aware of.
Again HDMI 2.0 should introduce 120 Hz at x1080 resolutions, should be mentioned in the manual. After skimming through here, it should be possible.
]]>HDMI will not do anything past 60hz as far as i know. I just got a new 144hz monitor and when hooked up with HDMI, the max refresh is only 60, but when hooked up with a dual link DVI all rates up to 144hz are there. I think even if what you are watching isn't going to push the tv, you should notice a nice difference but I could be wrong.
This is all good stuff--and typically, the way I learn it: AFTER the fact!
I just checked, and my HDTV has no DVI inputs! (When I was shopping for one, I remember thinking, "Oh, a DVI input would be nice--but I couldn't have told you at the time WHY...)
The video card I got has only 1 DVI output--and I'm using that to drive the monitor in the office...
I'm really curious, now, to see what 120Hz would look like (vs the 60Hz HDMI), but I guess that's not to be! :-[
]]>man mplayer
man mplayer2
man mpv
Mythtv probably uses one of them.
Glad I could help.
]]>As for the resolution issue, most (all?) of the source material I watch is NOT at 120Hz, so I'm not going to sweat it for now. When/If I get the antenna and/or a blue-ray player hooked up will be a good time to revisit this issue.
Thanks for the education! I appreciate it! :-)
]]>You would have to look up current limitations of HDMI, to know if 120 Hz is supported at 1920x1080. HDMI 2.0 should introduce this. Recently there was a showcase of a lcd using 16 HDMI to get a very high resolution. The picture looked so sharp, almost like in 3 dimensions.
Xrandr suggests 60 Hz at highest resolution is the maximum vertical frequency. You can try adding a new mode at 120 Hz. Take a look here, use cvt. You can do that with xorg.conf also, read the manual for it (man xorg.conf). Do it at your own risk, but nothing should happen.
As for the tearing issue, I do not use Nvidia any more, so there is little I can do to help. You could run a recent live medium distribution like Linux Mint and see if you get tearing there. Then look up its settings, drivers version and so on.
Do you recall having that issue before? I would try downgrading at least the nvidia driver.
As a side note: Please refrain from using terms like true 120 Hz, there is only 120 Hz, adjectives are unnecessary and only add further confusion. The marketing people already made a mess out of majority of standards, norms, formats and characteristics. This ends up encouraging terms like PMPO.
]]>The other day I saw something (wish I could remember where) questioning the idea that HDMI input could be run at 120Hz--that it was the NATIVE rez (ie, OTA broadcasts and/or cable input?) that was at true 120Hz.
Does the xrandr output suggest to you that that might be the case?
The other issue (the video tearing) has NOT been remedied with the BACKINGSTORE on.
I'd love to 'fix' both the tearing and the refresh rate (if that's even possible), but if I could only choose one, it would be the tearing.
Thanks for your ongoing help while I climb this learning curve...
]]>Extracted contents:
header: 00 ff ff ff ff ff ff 00
serial number: 22 f0 4f 26 01 01 01 01 18 10
version: 01 03
basic params: e8 26 1e 8c ee
chroma info: 67 60 a2 5a 49 9e 23 13 50 54
established: ad ef 80
standard: 81 80 01 01 01 01 01 01 01 01 01 01 01 01 01 01
descriptor 1: 30 2a 00 98 51 00 2a 40 30 70 13 00 54 0e 11 00 00 1e
descriptor 2: 00 00 00 fd 00 32 4c 1e 53 0e 00 0a 20 20 20 20 20 20
descriptor 3: 00 00 00 fc 00 48 50 20 66 31 39 30 35 0a 20 20 20 20
descriptor 4: 00 00 00 ff 00 43 4e 43 36 32 34 50 4e 46 34 0a 20 20
extensions: 00
checksum: 01
Manufacturer: HWP Model 264f Serial Number 16843009
Made week 24 of 2006
EDID version: 1.3
Digital display
Maximum image size: 38 cm x 30 cm
Gamma: 2.40
DPMS levels: Standby Suspend Off
Supported color formats: RGB 4:4:4, YCrCb 4:2:2
Default (sRGB) color space is primary color space
First detailed timing is preferred timing
Established timings supported:
720x400@70Hz
640x480@60Hz
640x480@72Hz
640x480@75Hz
800x600@60Hz
800x600@72Hz
800x600@75Hz
832x624@75Hz
1024x768@60Hz
1024x768@70Hz
1024x768@75Hz
1280x1024@75Hz
1152x870@75Hz
Standard timings supported:
1280x1024@60Hz
Detailed mode: Clock 108.000 MHz, 340 mm x 270 mm
1280 1328 1440 1688 hborder 0
1024 1025 1028 1066 vborder 0
+hsync +vsync
Monitor ranges (GTF): 50-76Hz V, 30-83kHz H, max dotclock 140MHz
Monitor name: HP
Serial number: CNC624PNF4
Checksum: 0x1 (valid)
EDID block does NOT conform to EDID 1.3!
Digital display field contains garbage: 68
Detailed block string not properly terminated
Here the ranges are also the same compared to the generated xorg.conf.
Almost, to export a variable use the command export:
export SDL_VIDEO_X11_BACKINGSTORE=1
The profile file is basically a shell script.
INVOCATION
[...]
When bash is invoked as an interactive login shell, or as a non-interactive shell with the --login option, it first
reads and executes commands from the file /etc/profile, if that file exists. After reading that file, it looks for
~/.bash_profile, ~/.bash_login, and ~/.profile, in that order, and reads and executes commands from the first one
that exists and is readable. The --noprofile option may be used when the shell is started to inhibit this behavior.
[...]
Search for terms you do not understand. You probably use bash, so its profile could be also used, but I still prefer to recommend something neutral and universal like ~./profile, since it is used by majority if not all shells.
I would test it playing a video like already suggested. To check if the variable is exported run in a terminal after starting X:
echo $SDL_VIDEO_X11_BACKINGSTORE
#or
env | grep SDL
But now that EDID has been decoded for both monitors comes the question: where did you get the information your HDTV supports 120 Hz at the resolution 1920 x 1080?
Is that it (TECH SPECS)?
If yes, I wonder what refresh rate they are referring to. Seems to be related to this or something similar.
$ xrandr -display :0.0 --props;
Screen 0: minimum 8 x 8, current 1280 x 1024, maximum 16384 x 16384
VGA-0 disconnected primary (normal left inverted right x axis y axis)
BorderDimensions: 4
supported: 4
Border: 0 0 0 0
range: (0, 65535)
SignalFormat: VGA
supported: VGA
ConnectorType: VGA
ConnectorNumber: 2
_ConnectorLocation: 2
DVI-D-0 connected 1280x1024+0+0 (normal left inverted right x axis y axis) 340mm x 270mm
EDID:
00ffffffffffff0022f04f2601010101
18100103e8261e8cee6760a25a499e23
135054adef8081800101010101010101
010101010101302a009851002a403070
1300540e1100001e000000fd00324c1e
530e000a202020202020000000fc0048
502066313930350a20202020000000ff
00434e43363234504e46340a20200001
BorderDimensions: 4
supported: 4
Border: 0 0 0 0
range: (0, 65535)
SignalFormat: TMDS
supported: TMDS
ConnectorType: DVI-D
ConnectorNumber: 0
_ConnectorLocation: 0
1280x1024 60.02*+ 75.02
1024x768 75.03 70.07 60.00
800x600 75.00 72.19 60.32
640x480 75.00 72.81 59.94
And, sorry...I'm not clear on what "export the variable" means. I created a ~/.profile file, the contents of which is now
SDL_VIDEO_X11_BACKINGSTORE=1
Is that correct? Having it in .profile negates the need to start mythfrontend with a specific variable, correct?
I rebooted the machine, started up the mythfrontend, started a video -- but still saw the tearing. Is there a way to tell the backingstore is in effect?
]]>Extracted contents:
header: 00 ff ff ff ff ff ff 00
serial number: 59 3a 06 10 01 01 01 01 00 17
version: 01 03
basic params: 80 58 32 78 0a
chroma info: d8 1d a2 5a 50 a1 26 0f 47 4a
established: a5 ce 00
standard: 81 00 81 c0 01 01 01 01 01 01 01 01 01 01 01 01
descriptor 1: 02 3a 80 18 71 38 2d 40 58 2c 45 00 75 f2 31 00 00 1e
descriptor 2: 00 00 00 fd 00 32 4d 1f 46 0f 00 0a 20 20 20 20 20 20
descriptor 3: 00 00 00 fe 00 56 49 5a 49 4f 0a 20 20 20 20 20 20 20
descriptor 4: 00 00 00 fc 00 4d 34 30 31 69 2d 41 33 0a 20 20 20 20
extensions: 01
checksum: ba
Manufacturer: VIZ Model 1006 Serial Number 16843009
Made week 0 of 2013
EDID version: 1.3
Digital display
Maximum image size: 88 cm x 50 cm
Gamma: 2.20
Supported color formats: RGB 4:4:4, YCrCb 4:2:2
First detailed timing is preferred timing
Established timings supported:
720x400@70Hz
640x480@60Hz
640x480@75Hz
800x600@60Hz
800x600@72Hz
800x600@75Hz
1024x768@60Hz
1024x768@70Hz
1024x768@75Hz
Standard timings supported:
1280x800@60Hz
1280x720@60Hz
Detailed mode: Clock 148.500 MHz, 885 mm x 498 mm
1920 2008 2052 2200 hborder 0
1080 1084 1089 1125 vborder 0
+hsync +vsync
Monitor ranges (GTF): 50-77Hz V, 31-70kHz H, max dotclock 150MHz
ASCII string: VIZIO
Monitor name: M401i
Has 1 extension blocks
Checksum: 0xba (valid)
CEA extension block
Extension version: 3
34 bytes of CEA data
Video data block
VIC 01
VIC 03
VIC 04
VIC 05
VIC 16 (native)
VIC 32
VIC 17
VIC 18
VIC 19
VIC 20
Audio data block
Linear PCM, max channels 1
Supported sample rates (kHz): 48 44.1 32
Supported sample sizes (bits): 24 20 16
AC-3, max channels 5
Supported sample rates (kHz): 192 96 48 44.1 32
Maximum bit rate: 56 kHz
RESERVED, max channels 0
Supported sample rates (kHz):
Maximum bit rate: 56 kHz
Speaker allocation data block
Vendor-specific data block, OUI 000c03 (HDMI)
Source physical address 2.0.0.0
DC_36bit
DC_Y444
Maximum TMDS clock: 225MHz
Basic audio support
Supports YCbCr 4:4:4
Supports YCbCr 4:2:2
1 native detailed modes
Detailed mode: Clock 148.500 MHz, 885 mm x 498 mm
1920 2008 2052 2200 hborder 0
1080 1085 1090 1125 vborder 0
+hsync +vsync
Detailed mode: Clock 74.250 MHz, 885 mm x 498 mm
1280 1390 1430 1650 hborder 0
720 725 730 750 vborder 0
+hsync +vsync
Checksum: 0x81 (valid)
EDID block does NOT conform to EDID 1.3!
Detailed block string not properly terminated
This explains the 50-77 Hz refresh rates from your xorg.conf. Nvidia software probably decodes EDID and puts those in xorg.conf.
The EDID data you posted is for the same monitor (screen 1). The other one on DVI-D-0 should produce something else. You probably run it on screen 1, so using the DISPLAY variable or the display switch with xrandr set to screen 0 should get that output.
env DISPLAY=:0.0 xrandr --props;
#or
xrandr -display :0.0 --props;
You can export the variable in ~/.profile (add it to the file if it exists, create with that content if it does not) or start the frontend with the variable exported in the shell. To test, playing a video file should be sufficient:
env SDL_VIDEO_X11_BACKINGSTORE=1 mpv video-file.mp4
So you are not going to post those xrandr results?
Ooops. Sorry!
$ xrandr --props; env DISPLAY=:0.1 xrandr --props
Screen 1: minimum 8 x 8, current 1920 x 1080, maximum 16384 x 16384
HDMI-0 connected primary 1920x1080+0+0 (normal left inverted right x axis y axis) 885mm x 498mm
EDID:
00ffffffffffff00593a061001010101
00170103805832780ad81da25a50a126
0f474aa5ce00810081c0010101010101
010101010101023a801871382d40582c
450075f23100001e000000fd00324d1f
460f000a202020202020000000fe0056
495a494f0a20202020202020000000fc
004d343031692d41330a2020202001ba
020326714b010304059020111213141f
29090705155750000000830100006703
0c002000282d023a801871382d40582c
550075f23100001e011d007251d01e20
6e28550075f23100001e000000000000
00000000000000000000000000000000
00000000000000000000000000000000
00000000000000000000000000000081
BorderDimensions: 4
supported: 4
Border: 0 0 0 0
range: (0, 65535)
SignalFormat: TMDS
supported: TMDS
ConnectorType: HDMI
ConnectorNumber: 1
_ConnectorLocation: 1
1920x1080 60.00*+ 60.00 59.94 50.00 23.97 60.00 50.04
1280x800 59.81
1280x720 60.00 59.94 50.00
1024x768 75.03 70.07 60.00
800x600 75.00 72.19 60.32
720x576 50.00
720x480 59.94
640x480 75.00 59.94 59.93
Screen 1: minimum 8 x 8, current 1920 x 1080, maximum 16384 x 16384
HDMI-0 connected primary 1920x1080+0+0 (normal left inverted right x axis y axis) 885mm x 498mm
EDID:
00ffffffffffff00593a061001010101
00170103805832780ad81da25a50a126
0f474aa5ce00810081c0010101010101
010101010101023a801871382d40582c
450075f23100001e000000fd00324d1f
460f000a202020202020000000fe0056
495a494f0a20202020202020000000fc
004d343031692d41330a2020202001ba
020326714b010304059020111213141f
29090705155750000000830100006703
0c002000282d023a801871382d40582c
550075f23100001e011d007251d01e20
6e28550075f23100001e000000000000
00000000000000000000000000000000
00000000000000000000000000000000
00000000000000000000000000000081
BorderDimensions: 4
supported: 4
Border: 0 0 0 0
range: (0, 65535)
SignalFormat: TMDS
supported: TMDS
ConnectorType: HDMI
ConnectorNumber: 1
_ConnectorLocation: 1
1920x1080 60.00*+ 60.00 59.94 50.00 23.97 60.00 50.04
1280x800 59.81
1280x720 60.00 59.94 50.00
1024x768 75.03 70.07 60.00
800x600 75.00 72.19 60.32
720x576 50.00
720x480 59.94
640x480 75.00 59.94 59.93
I'm not exactly sure what that's telling me--but it looks like it's confirming that both monitors are running at 60Hz, yes?
You probably want to set the sdl variable to use the feature:
export SDL_VIDEO_X11_BACKINGSTORE=1
I see on that page,
if you want backingstore back, then run (before launching the sdl app):
export SDL_VIDEO_X11_BACKINGSTORE=1
Would the "sdl app" in my case be the mythfrontend, or...? And does that export command just go into a terminal, or does it belong in a config somewhere...?
Thanks for the ongoing help!
]]>export SDL_VIDEO_X11_BACKINGSTORE=1
I'm using XFCE--I wonder if that has something to do with the video tearing? (Although I'm not using any compositing--that I know of!)
Well, running compton with the settings from that thread has had no effect on my tearing... :-[
]]>