-
Notifications
You must be signed in to change notification settings - Fork 423
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Can't specify individual monitor #23
Comments
I have marked this as a bug since the example where you set randr:screen=0 or randr:screen=1 should work as far as I can tell given your setup. What output do you get when you run |
It doesn't. It just mentions Screen 0, which I think is the single X screen that I have configured.
|
Ok, so it seems that you have one screen that spans multiple outputs. I don't really have a multidisplay setup myself so I don't know if this is the normal way of configuring the screens. Currently Redshift works by screen so it will apply the effect on all outputs associated with a screen. It's quite likely that Redshift could be changed to work by output instead because it seems that gamma ramp correction is applied by output anyway, when using randr. So, to answer your question: No, with your current setup it seems that you have to enable Redshift on both outputs. Redshift would have to be updated to only apply corrections to one randr output. |
jonls, thanks for your reply! Perhaps some future traffic from Google will find this conversation as helpful as I have. Thanks again for a great piece of software. |
Greetings! I have a HDTV connected to my computer and I didn't want redshift to dim the TV. After trying many settings I found the right way: gtk-redshift -l 38.7:9.1 -t 5700:4700 -g 0.8 -o -m vidmode:screen=0 The ' -m vidmore:screen=0 ' did the trick. I'm using Linux Maya 13. Cheers |
I want to update this for future reference, in case anyone else stumbles upon it as I have. When you have two outputs on one randr screen, you can now use |
Everything is the best! Thank you so much! I've confirmed that it works perfectly for me! |
It worked for me using 0 for the first screen and 1 for the second "redshift -m randr:crtc=1 -O 5000" |
This is working fairly well for me. I'm using a configuration file and appreciate the intricate options. Here's my xrandr output... |
I am using i3. Screen 0 with 3 monitors i.e. LVDS, DisplayPort-1, DVI-I-1-1. Redshift only affects LVDS and DisplayPort, leaving DVI-I-1-1 as is. Also randr:crtc=output affects only LVDS does not matter whichever output I specify. $ xrandr |
The ability to specify individual monitors at any time via menu option would be nice. Sometimes I want my second or third monitor's to shift, sometimes I don't (code on middle monitor and want shift, movie on either side and may not want shift, reference resources on either side and may not want shift)... Configuring via menu options would allow changing shift on the fly. |
Agree with this, also would be happy if I could even just set this in the config file! One of my monitors is a TV that looks very bad with the temperature adjustments, on Windows with f.lux I'm able to just disable it on that monitor only very easily, but using a command like |
Hi! Sorry if this is an inappropriate place to ask this, but I can't seem to target a particular monitor when running Redshift.
Here's my setup:
They're set up on the same X screen, :0. I use awesome window manager to treat the monitors as separate screens.
I can interact with the monitors using xrandr just fine. I use xrandr to set up their display resolutions and relative positions with no problem.
However, running gtk-redshift (v1.7), I can't seem to get the shift on just HDMI-1.
All of these commands turn on redshift on both monitors:
$ gtk-redshift -l 40.6:-74 -m randr:screen=HDMI-1
$ gtk-redshift -l 40.6:-74 -m randr:screen=DVI-I-1
$ gtk-redshift -l 40.6:-74 -m randr:screen=0
And, as one might expect, this is the output of -m randr:screen=1:
Must I set up a separate X screen to run Redshift only on HDMI-1? What am I missing?
Thanks for a wonderful piece of software!
The text was updated successfully, but these errors were encountered: