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

Nice script!. I get this error when running the script on my newly installed system. Anyone who can help me fix it?, because nvidia-settings --help doesnt help me much . I can add that I am new to linux.

5/6 Applying NVIDIA settings
No protocol specified

ERROR: The control display is undefined; please run `nvidia-settings --help`
for usage information.

No protocol specified

ERROR: The control display is undefined; please run `nvidia-settings --help`
for usage information.


EDIT: Hmmm everything seems to be working as it should, even with the error .

sonic Wrote:Nice script!. I get this error when running the script on my newly installed system. Anyone who can help me fix it?, because nvidia-settings --help doesnt help me much . I can add that I am new to linux.

5/6 Applying NVIDIA settings
No protocol specified

ERROR: The control display is undefined; please run `nvidia-settings --help`
for usage information.

No protocol specified

ERROR: The control display is undefined; please run `nvidia-settings --help`
for usage information.


EDIT: Hmmm everything seems to be working as it should, even with the error .

This part is acctually not needed if you have a newly installed system, so you're good!

Just a short question. I have problems with video jutter and tear and a lot people say it's due to xorg.conf, would your solution solve this?

Thank you in advance.

which refresh rate should I use for 29.97 movie? 1920x1080_30 or 1920x1080_0? Also if my tv support 25Hz, should I use it instead of 50Hz for some PAL TV show?

I have a movie that has lots of jutter and tear when use 24Hz, but played well when use 60Hz. the movie is 24p(or 23.97, not sure), any idear?

Matija Wrote:Just a short question. I have problems with video jutter and tear and a lot people say it's due to xorg.conf, would your solution solve this?

Thank you in advance.

Sorted by using your script! Worked awesome, thanks again!

thank you for this!

this solved a problem that was plaguing me. this should be sticky'd!

johnskiller Wrote:which refresh rate should I use for 29.97 movie? 1920x1080_30 or 1920x1080_0? Also if my tv support 25Hz, should I use it instead of 50Hz for some PAL TV show?

I have a movie that has lots of jutter and tear when use 24Hz, but played well when use 60Hz. the movie is 24p(or 23.97, not sure), any idear?

Using a 59.94 Hz mode is your best option for a 29.97 fps movie. On many tvs the video looks smoother, and you also get smother animations in the menus. Same applies to 25 vs 50 Hz.

Could be many reasons behind the issue with 24 Hz. If it's not fixed by performing the steps in the guide, post some more info about your setup.

Just a data point here. You said:

Quote:First of all, modelines are not a the magic solution to all your problems. Modelines are only needed with tv's that have faulty EDID information. Most TVs provide the correct modes for 29.97/59.94 Hz, but the modes are not used by xrandr by default, so XBMC can't see that they are available.

I wanted to note that I just ran into one case where a ModeLine seemed to be necessary (okay, maybe not necessary if the only software you are using is XBMC, but certainly desirable if you want to use the Ubuntu desktop, or any other software that doesn't have built-in overscan correction like XBMC does). That was on a Sharp TV that had a serious overscan issue, and apparently no "pixel by pixel" option. To make a long story short, after putting the TV model number and the word "overscan" in Google, you arrive at this page, which describes how a ModeLine is used to emulate the "CVT reduced blank" option that is apparently available on a Windows machine. Those instructions are ONLY for that particular model TV, but it makes me wonder if perhaps there are other TV's that may look at timing parameters to determine whether to make the "dot by dot" or "pixel by pixel" option visible, or usable (not grayed out).

Maybe it's my imagination, but to me the picture seemed a bit sharper when we could get the "Dot by Dot" option to work on that TV, and did not have to use the overscan correction in XBMC.

The one issue I had was that we did try JumJum's script, but in the end still had to put back the custom xorg.conf file from the above-linked article in order to get the "dot by dot" option to reappear. I wonder if only some small part of that xorg.conf could be cut and pasted into the xorg.conf returned by the script, to get the benefits of the script along with the making the "dot by dot" option available.

xbmcliveuser Wrote:Just a data point here. You said:

I wanted to note that I just ran into one case where a ModeLine seemed to be necessary (okay, maybe not necessary if the only software you are using is XBMC, but certainly desirable if you want to use the Ubuntu desktop, or any other software that doesn't have built-in overscan correction like XBMC does). That was on a Sharp TV that had a serious overscan issue, and apparently no "pixel by pixel" option. To make a long story short, after putting the TV model number and the word "overscan" in Google, you arrive at this page, which describes how a ModeLine is used to emulate the "CVT reduced blank" option that is apparently available on a Windows machine. Those instructions are ONLY for that particular model TV, but it makes me wonder if perhaps there are other TV's that may look at timing parameters to determine whether to make the "dot by dot" or "pixel by pixel" option visible, or usable (not grayed out).

Maybe it's my imagination, but to me the picture seemed a bit sharper when we could get the "Dot by Dot" option to work on that TV, and did not have to use the overscan correction in XBMC.

The one issue I had was that we did try JumJum's script, but in the end still had to put back the custom xorg.conf file from the above-linked article in order to get the "dot by dot" option to reappear. I wonder if only some small part of that xorg.conf could be cut and pasted into the xorg.conf returned by the script, to get the benefits of the script along with the making the "dot by dot" option available.

I would still call this a faulty EDID though, since it does work with a modeline and that mode is not available in the EDID. Had the manufacturer supplied the proper modes in the EDID it would have worked out of the box.

It's not your imagination. The image is sharper when your use pixel mapping or dot by dot since no resizing of the image occurs.

You can use your working xorg.conf, but replace the Device section with the one from the guide. Then, in the new device section, change the Identifier value to the value from your working config and change the ModeValidation setting to "NoVesaModes, NoXServerModes, NoEdidModes"

This is just off the top of my head, but it should work.

JumJum,

I have set my system up with your script and I use 1080p@60Hz in the XBMC menus, for smoother browsing.

But, after my HTPC (XBMC) has been suspended (sleep) and resumed, it always defaults to 1080p@24Hz.

Any way I can change that?