(2012-07-12 19:00)robo989 Wrote:
(2012-07-08 10:31)FernetMenta Wrote: This xorg.conf has worked on all systems TV I have tried:
DFP-0 might be changed to DFP-1
(2012-07-11 17:31)Rachel Wrote:
(2012-07-11 17:26)robo989 Wrote: Hang on there, does that mean this guide isn't needed and this is all dealt with no intervention, or the guide doesn't work for 302.17!?
It seems it wants the modeline added to an xorg.conf (which therefore needs to exist) so it's not all working with no intervention, but it's an alternative approach to the fix at the top of this thread and basically amounts to "use *this* xorg.conf and install nvidia 302.17+"
That xorg.conf gives me an "unsupported mode" message on my Samsung 5 series plasma, about 3 years old. Fired up a 1920x800 24fps MKV and appears to work fine for about 10 seconds with correct frame rate of 24fps and not 23.976fps.
Going to try my old xorg.conf and see if it works with the 302.17 drivers...
Thanks for posting it though, and thanks for the pointer Rachel.
Mine is a Panasonic Viera plasma of about the same vintage. It's EDID (posted above somewhere) shows:
# "1920x1080_24" : 1920 x 1080 @ 23.97/24 Hz (CEA-861B Format 32)
ie: it's the same actual mode on the TV that handles both, presumably by being flexible about locking onto what the source is giving out? So what we're basically doing is giving X and XBMC the choices to send either.
Anyway the supplied xorg.conf (with DFP-0 changed to DFP-1 I think because the hardware is a mac mini and DFP-0 is the displayport interface) works for me in that it gives me the 23.974Hz mode that allows most movies to play.
I remembered I was going to test the one movie I know I have that is at exactly 24Hz (Coriolanus blu-ray rip) and sure enough I get a periodic skipped frame which I expect is this issue. I've already watched this movie on a different configuration but on the same TV and had no such issues so I know the TV can handle it.
We probably need a modeline to exactly define 24Hz. However that's done.
I think the main advantages of the newer software all round is that XMBC and X and the nvidia drivers all can choose modes from those available with exactitude, but no exact 24Hz mode has been autodetected in my case.
I look at the output of xbmc-xrandr and I notice:
<mode id="0x1c6" name="1920x1080" w="1920" h="1080" hz="23.97576" current="false" preferred="false"/>
... which is the mode added by the modeline given in the earlier post. And:
<mode id="0x1c9" name="1920x1080" w="1920" h="1080" hz="23.97091" current="false" preferred="false"/>
... which I believe is the autodetected mode from the EDID line above. It's presumably made a mode based on the lower end of the range EDID is saying it can do.
So I expect in my case at least - and possibly others, it presumably depends on the TV model - that I need that exact 24Hz modeline.
Bloody NTSC. It's only the dark and sorry legacy of that format that's why non-integer framerates even exist. You'll notice PAL is quite happy and perfect on an exact 50Hz!