Linux HOW-TO achieve perfect playback at 23.97 or 59.94 Hz with NVIDIA GPU hardware

  Thread Rating:
  • 15 Votes - 5 Average
  • 1
  • 2
  • 3
  • 4
  • 5
Post Reply
robo989 Offline
Senior Member
Posts: 176
Joined: Apr 2010
Reputation: 2
Post: #471
(2012-07-08 10:31)FernetMenta Wrote:  This xorg.conf has worked on all systems TV I have tried:
http://xbmclogs.com/show.php?id=4386

DFP-0 might be changed to DFP-1

(2012-07-11 17:31)Rachel Wrote:  
(2012-07-11 17:26)robo989 Wrote:  
(2010-03-17 16:12)JumJum Wrote:  OUTDATED with NVidia driver 302.17!!!!!
(It has support for xrandr 1.2/1.3 and can distinguish between 23.976 and 24)

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 when playing some SD xvid tv series. 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. Another attempt just gave a blank screen, then a crash.

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.
(This post was last modified: 2012-07-12 19:05 by robo989.)
find quote
Rachel Offline
Senior Member
Posts: 157
Joined: Jun 2009
Reputation: 0
Post: #472
(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:
http://xbmclogs.com/show.php?id=4386

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:

Code:
# "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. Smile 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:

Code:
<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:

Code:
<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!
find quote
robo989 Offline
Senior Member
Posts: 176
Joined: Apr 2010
Reputation: 2
Post: #473
Thanks for posting again, it looks like I went into a daydream and didn't finish the sentence. Basically, SD tv show = no picture, tv states "unsupported mode". HD MKV at 24fps, switches correctly to 24fps, plays at 24.00fps too (so it does work), but after a few seconds it drops to about 2-3fps like a slideshow, it also takes around 10 seconds for the MKV to actually start playing...

Ridiculous anaolgy but it feels like I've put petrol in a diesel engine with these 302.17 drivers and suspect there's a lot more wrong than just an xorg.conf.

Although I suspect this could well be down to the new AudioEngine.

If I use my old xorg.conf that plays happy with 295.40 then the tv doesn't even switch to 24p, but goes to 60hz mode instead, plays at super high speed for 10 seconds then crashes.

I have now reverted back to 295.40 easily enough and everything works again (obviously except 24.000 material).

I guess will just have to way, thanks for posting the info you have but I don't think it's relevent in my situation, sorry my fault for the vauge details in previous post.
find quote
ialand Offline
Senior Member
Posts: 231
Joined: May 2011
Reputation: 0
Post: #474
(2012-07-11 17:31)Rachel Wrote:  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+"

*this* Confused
find quote
Rachel Offline
Senior Member
Posts: 157
Joined: Jun 2009
Reputation: 0
Post: #475
(2012-07-13 00:18)ialand Wrote:  
(2012-07-11 17:31)Rachel Wrote:  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+"

*this* Confused

This: http://xbmclogs.com/show.php?id=4386 (posted a few posts ago)
find quote
szafir51 Offline
Junior Member
Posts: 5
Joined: Jul 2012
Reputation: 0
Post: #476
Hello,

I'm using XBMC 11.0 installed on Ubuntu 12.04 x86, running on nVidia ION HTPC with nvidia 302.17 driver installed. My HTPC is connected to Panasonic Viera TH-37PV80 through Onkyo TX-SR308. My TV is only HDready (720p), so I using 1280x720 resolution in Ubuntu. I've tested available modes for my configuration and I can't find 1280x720@23.97.
Here is output of xbmc-xrandr command:

Quote: <mode id="0x1c6" name="1280x720" w="1280" h="720" hz="50.00000" current="true" preferred="true"/>
<mode id="0x1cc" name="1280x720" w="1280" h="720" hz="60.00000" current="false" preferred="false"/>
<mode id="0x1cd" name="1280x720" w="1280" h="720" hz="59.94343" current="false" preferred="false"/>
<mode id="0x1c7" name="1920x1080" w="1920" h="1080" hz="59.93939" current="false" preferred="false"/>
<mode id="0x1c8" name="1920x1080" w="1920" h="1080" hz="50.00000" current="false" preferred="false"/>
<mode id="0x1c9" name="1920x1080" w="1920" h="1080" hz="23.97091" current="false" preferred="false"/>
<mode id="0x1ca" name="1920x1080" w="1920" h="1080" hz="29.99838" current="false" preferred="false"/>
<mode id="0x1cb" name="1920x1080" w="1920" h="1080" hz="25.02224" current="false" preferred="false"/>
<mode id="0x1ce" name="720x576" w="720" h="576" hz="50.00000" current="false" preferred="false"/>
<mode id="0x1cf" name="720x576" w="720" h="576" hz="25.04006" current="false" preferred="false"/>
<mode id="0x1d0" name="720x480" w="720" h="480" hz="59.94006" current="false" preferred="false"/>
<mode id="0x1d1" name="720x480" w="720" h="480" hz="30.02722" current="false" preferred="false"/>
<mode id="0x1d2" name="640x480" w="640" h="480" hz="59.92857" current="false" preferred="false"/>
<mode id="0x1d3" name="480x576" w="480" h="576" hz="50.00000" current="false" preferred="false"/>
<mode id="0x1d4" name="480x480" w="480" h="480" hz="59.94006" current="false" preferred="false"/>
<mode id="0x1d5" name="411x576" w="411" h="576" hz="50.07059" current="false" preferred="false"/>
<mode id="0x1d6" name="411x480" w="411" h="480" hz="59.97279" current="false" preferred="false"/>
<mode id="0x1d7" name="3x576" w="3" h="576" hz="29.64744" current="false" preferred="false"/>
<mode id="0x1d8" name="3x480" w="3" h="480" hz="35.30534" current="false" preferred="false"/>

Should I add modeline in xorg.conf to have 720p@23.97 ??
find quote
pyite Offline
Junior Member
Posts: 49
Joined: Mar 2010
Reputation: 0
Post: #477
could someone repost the xorg referenced several posts above?
find quote
Rachel Offline
Senior Member
Posts: 157
Joined: Jun 2009
Reputation: 0
Post: #478
further developed by its author (so 23.976Hz and 24Hz are both matched correctly):

http://xbmclogs.com/show.php?id=6030
find quote
pumkinut Offline
Posting Freak
Posts: 875
Joined: May 2006
Reputation: 9
Post: #479
I just installed the 304.32 beta drivers last night. It looks like it does an EDID scan and figures out the modeline xorg.conf entries automagically now.
find quote
robo989 Offline
Senior Member
Posts: 176
Joined: Apr 2010
Reputation: 2
Post: #480
(2012-08-08 19:21)pumkinut Wrote:  I just installed the 304.32 beta drivers last night. It looks like it does an EDID scan and figures out the modeline xorg.conf entries automagically now.

302 does that already since a while.

Or are you saying it now works for displays that give incorrect EDID info as in to incorrectly give a max resolution of 720p on displays that can do 1080p?
find quote
Post Reply