[NVIDIA][304.43] nvidia-settings not save color correction settings

unikum · 2012-08-29 05:13:02

Hi all. After latest update I can't save brightness, contrast and gamma settings in .nvidia-settings-rc

I try adjust this settings and save current configuration to .nvidia-settings-rc. But in .nvidia-settings-rc this parametrs have a default values.

extra/nvidia 304.43-1
extra/nvidia-utils 304.43-1

http://wstaw.org/m/2012/08/29/16.png

$ cat .nvidia-settings-rc 
#
# /home/xxx/.nvidia-settings-rc
#
# Configuration file for nvidia-settings - the NVIDIA X Server Settings utility
# Generated on Wed Aug 29 12:06:22 2012
#

# ConfigProperties:

RcFileLocale = C
ToolTips = Yes
DisplayStatusBar = Yes
SliderTextEntries = Yes
IncludeDisplayNameInConfigFile = No
ShowQuitDialog = Yes
Timer = Thermal_Monitor_(GPU_0),Yes,1000
Timer = PowerMizer_Monitor_(GPU_0),Yes,1000

# Attributes:

0/CursorShadow=0
0/CursorShadowAlpha=64
0/CursorShadowRed=0
0/CursorShadowGreen=0
0/CursorShadowBlue=0
0/CursorShadowXOffset=4
0/CursorShadowYOffset=2
0/SyncToVBlank=1
0/LogAniso=0
0/FSAA=0
0/TextureSharpen=1
0/TextureClamping=1
0/FXAA=0
0/AllowFlipping=1
0/FSAAAppControlled=1
0/LogAnisoAppControlled=1
0/OpenGLImageSettings=3
0/FSAAAppEnhanced=0
0/RedBrightness=0.000000
0/GreenBrightness=0.000000
0/BlueBrightness=0.000000
0/RedContrast=0.000000
0/GreenContrast=0.000000
0/BlueContrast=0.000000
0/RedGamma=1.000000
0/GreenGamma=1.000000
0/BlueGamma=1.000000
0/DigitalVibrance[CRT-1]=0
0/XVideoSyncToDisplay=2

Last edited by unikum (2012-08-29 07:39:22)

Glinx · 2012-09-06 22:40:09

Same here.
Ive edited the .nvidia-settings-rc file by hand, set the file permission to read only (so it cant be over written), start nvidia x server settings tool which loads my settings as it opens, then just close it again.

Fingers crossed for bug fix in next release!

unikum · 2012-09-07 05:06:55

I use following script as workground:

#/bin/bash

nvidia-settings -l
nvidia-settings -a 0/Brightness[CRT-1]=0,012 -a 0/Contrast[CRT-1]=-0,11 -a 0/Gamma[CRT-1]=0,7

solamir · 2012-09-07 09:03:23

Did you try to write your settings into ~/.xinitrc?

Glinx · 2012-09-07 09:09:12

No, Ive just this minute changed it to your way by placing my script.sh in gnome3's home/.config/autostart folder along with its script.desktop file :-)

EDIT: Should have said unikum's way

Last edited by Glinx (2012-09-07 11:14:03)

unikum · 2012-09-07 11:44:42

@solamir: i put this script to $HOME/.kde4/env/

solamir · 2012-09-07 12:15:32

To: unikum: Ok, was the problem solved after you've done this?
The similar problem was solved on the russian archlinux forum about year ago. Look http://archlinux.org.ru/forum/viewtopic … ee793def97.

unikum · 2012-09-07 12:52:42

@solamir: the problem is that nvidia-settings since a last update don't save some options in .nvidia-settings-rc. Your link is not relevant this issue.

solamir · 2012-09-07 14:11:58

Your link is not relevant this issue

Why not? Did you try to write
exec nvidia-settings -l &
in ~/.xinitrc?
Or the settings were ignored after manual correction?
Or the file .nvidia-settings-rc was rewrited after reboot?
I'm sorry if I don't understand your problem.

unikum · 2012-09-07 14:36:21

@solamir: When I try save config from nvidia-settings GUI some options not changes:

0/RedBrightness=0.000000
0/GreenBrightness=0.000000
0/BlueBrightness=0.000000
0/RedContrast=0.000000
0/GreenContrast=0.000000
0/BlueContrast=0.000000
0/RedGamma=1.000000
0/GreenGamma=1.000000
0/BlueGamma=1.000000

solamir · 2012-09-07 14:52:48

it's clear. What if you change .nvidia-settings-rc manually?
Maybe the problem is with GUI.

matrs · 2013-05-14 18:53:57

Hello,

I have a similar problem using the last two nvidia drivers (right now 319.17). Changes made using the GUI are effectively written into the ~/.nvidia-settings-rc file, but after rebooting that file is overwritten coming back to the default values. For example here, using the nvidia GUI, i changed the gamma values to 0.94. This is the ~/.nvidia-settings-rc

# Attributes:

desktop:0[dpy:1]/RedGamma=0.940000
desktop:0[dpy:1]/GreenGamma=0.940000
desktop:0[dpy:1]/BlueGamma=0.940000

It is the same if i change the gamma values using Kgamma

Last edited by matrs (2013-05-14 18:55:25)

PReP · 2013-05-15 09:29:29

I am aswell having issues with this, it is quite noticable when you have spend insane amounts of time getting "the perfect picture (tm)" =/.

There is both the issue of "nvidia-settings -l" or "nvidia-settings --load-config-only (deprecated?)" not working all the time.

But there is another thing i have noticed. I generally load up the nvidia-settings itself to have it "re-set" my colour-settings when it has not automatically,
but certain applications and/games seems to reset it back to default and i have to reload the config again, and make it re-set it again.

This is tedious, i hope there is something i have missed and not another of these smaller quirks that nvidia might miss to pick up on and fix.

*david_a* · 2013-07-13 00:28:46

I think I found a usable temporary solution, thanks to nVidia developer zone forum. In short, the problem is that the GUI application writes your machine's hostname into the config file, but the driver can't parse that type of config file, making it unable to find the screen.

1. Change the settings to your liking, using the GUI as usual. Quit the GUI application to save your changes.

2. Edit the config file (~/.nvidia-settings-rc) in a text editor to remove every mention of your machine's hostname. (Leave everything else just as it is, only remove the actual letters of the hostname.)

3. Write-protect the config file when you're finished.

neoarch · 2014-02-05 14:57:52

What did the fish say, when it hit a wall? ...... Dam!!!!!

I've been looking for this complete solution for years. Why? Why? Why? Dear Nvidia... let it go open! You are only causing setup issues!

We'll get it to work after booting. Thanks contributors! THANK YOU!

Mine corrects the Color (Green cast) Gamma of an old Dell CRT, for extremely accurate photo editing.

>>>SOLUTION<<<

1. The whole root thing will confuse you. This needs to be done as user. X starts as user, and then needs Nvidia's *user* settings.

2. Make your changes from the nvidia-settings GUI (as user). That saves them in your personal ~/.nvidia-settings-rc file.

3. Now you go to whatever is your 'Startup Applications' GUI. Such as (System > Preferences > Startup Applications Mate) ...for mine. ....and....

A. Put...

nvidia-settings -l

...into the command string dialog of your newly added startup entry. That's a lower case "-L". Title it "Nvidia Load Settings" or whatever.

B. Hold the keys CTRL+H in your home directory file manager GUI, to show hidden files, and click .nvidia-settings-rc to load it into your default text editor. All as user.

or...
pluma ~/.nvidia-settings-rc
...with the Mate desktop. Use your preferred editor in place of pluma.

C. Simply use the search and REPLACE ALL to avoid typo’s (else manual edit) and replace your specific repeated host name with NOTHING in the replace box. Mine replaced several instances of my host name, with nothing. It is OK for the lines to start with only ":". SAVE it.

Reboot. It WORKS! No more having to run the nividia-settings GUI, and then close it, on every boot! Finally, that #$% nvidia-settings load option works!

Note: If you write protect the config file, then you will have to undo that to make changes. If you don't write protect the file then you may have to do this again (Just C. above), after any changes.

TESTED: Yep. Making a change in the user nividia-settings automatically adds your host name (in multiple), back into its config file, and you will need to remove them again. Setting read-only locks it out from any nvidia-settings GUI changes. You must remember to set the config back to read and write, before making further changes. Then you must remove your host name and lock it out again.

Oh nvidia, what a tangled web, and they say "Linux" is hard! Proof positive of where the difficulties lay.

I suppose a work around would be an auto running script to strip out the host name, after nvidia-settings is run; but come on Nvidia.

Last edited by neoarch (2014-02-05 15:33:58)

Arch Linux

#1 2012-08-29 05:13:02

[NVIDIA][304.43] nvidia-settings not save color correction settings

#2 2012-09-06 22:40:09

Re: [NVIDIA][304.43] nvidia-settings not save color correction settings

#3 2012-09-07 05:06:55

Re: [NVIDIA][304.43] nvidia-settings not save color correction settings

#4 2012-09-07 09:03:23

Re: [NVIDIA][304.43] nvidia-settings not save color correction settings

#5 2012-09-07 09:09:12

Re: [NVIDIA][304.43] nvidia-settings not save color correction settings

#6 2012-09-07 11:44:42

Re: [NVIDIA][304.43] nvidia-settings not save color correction settings

#7 2012-09-07 12:15:32

Re: [NVIDIA][304.43] nvidia-settings not save color correction settings

#8 2012-09-07 12:52:42

Re: [NVIDIA][304.43] nvidia-settings not save color correction settings

#9 2012-09-07 14:11:58

Re: [NVIDIA][304.43] nvidia-settings not save color correction settings

#10 2012-09-07 14:36:21

Re: [NVIDIA][304.43] nvidia-settings not save color correction settings

#11 2012-09-07 14:52:48

Re: [NVIDIA][304.43] nvidia-settings not save color correction settings

#12 2013-05-14 18:53:57

Re: [NVIDIA][304.43] nvidia-settings not save color correction settings

#13 2013-05-15 09:29:29

Re: [NVIDIA][304.43] nvidia-settings not save color correction settings

#14 2013-07-13 00:28:46

Re: [NVIDIA][304.43] nvidia-settings not save color correction settings

#15 2014-02-05 14:57:52

Re: [NVIDIA][304.43] nvidia-settings not save color correction settings

Board footer