Could I have black bars (a.k.a. overscan) on my monitor please?
I have a monitor that is too big and too bright to work on in the night-time. (but I want to keep it for gaming). For work, I am wondering if there is a way to resize ALL of the content down on the screen, effectively give myself black bars (increase overscan) through software, since my monitor does not support such a feature.
I don't see any such scaling options in the Display settings, lowering the resolution will still stretch it out across the entire screen.
It is a Intel HD Graphics 5500 graphics card on a laptop with an external monitor.
Can this be done?
graphics display display-resolution monitor
|
show 2 more comments
I have a monitor that is too big and too bright to work on in the night-time. (but I want to keep it for gaming). For work, I am wondering if there is a way to resize ALL of the content down on the screen, effectively give myself black bars (increase overscan) through software, since my monitor does not support such a feature.
I don't see any such scaling options in the Display settings, lowering the resolution will still stretch it out across the entire screen.
It is a Intel HD Graphics 5500 graphics card on a laptop with an external monitor.
Can this be done?
graphics display display-resolution monitor
If your game does not need to be played in fullscreen, maybe setting a black background may help. If you are using a desktop environment that supports it (I don't think Unity does), enable auto-hide on your panels.
– luk3yx
Apr 20 '17 at 0:07
No it's not for the game, it's the opposite. Sorry if I explained it wrong, the game is not important here. I was just justifying why I wanted to keep the big monitor, as opposed to just buying a smaller one.
– 3Nex
Apr 20 '17 at 0:11
As far as brightness is concerned, have you considered something like redshift? For the "black bars" I would try searching through items related to overscan. Typically, this is something people are trying to get rid of, not create, but you might be able to use the same advice to increase overscan.
– b_laoshi
Apr 20 '17 at 0:41
Something along these lines might get you going in the right direction.
– b_laoshi
Apr 20 '17 at 0:50
Redshift is actually an even better solution that I hoped for.xrandr
gave me nothing but errors sayingBadName (named color or font does not exist)
, but I'm more than okay with using Redshift.
– 3Nex
Apr 21 '17 at 1:12
|
show 2 more comments
I have a monitor that is too big and too bright to work on in the night-time. (but I want to keep it for gaming). For work, I am wondering if there is a way to resize ALL of the content down on the screen, effectively give myself black bars (increase overscan) through software, since my monitor does not support such a feature.
I don't see any such scaling options in the Display settings, lowering the resolution will still stretch it out across the entire screen.
It is a Intel HD Graphics 5500 graphics card on a laptop with an external monitor.
Can this be done?
graphics display display-resolution monitor
I have a monitor that is too big and too bright to work on in the night-time. (but I want to keep it for gaming). For work, I am wondering if there is a way to resize ALL of the content down on the screen, effectively give myself black bars (increase overscan) through software, since my monitor does not support such a feature.
I don't see any such scaling options in the Display settings, lowering the resolution will still stretch it out across the entire screen.
It is a Intel HD Graphics 5500 graphics card on a laptop with an external monitor.
Can this be done?
graphics display display-resolution monitor
graphics display display-resolution monitor
edited Apr 20 '17 at 5:51
b_laoshi
2,642928
2,642928
asked Apr 20 '17 at 0:04
3Nex3Nex
1133
1133
If your game does not need to be played in fullscreen, maybe setting a black background may help. If you are using a desktop environment that supports it (I don't think Unity does), enable auto-hide on your panels.
– luk3yx
Apr 20 '17 at 0:07
No it's not for the game, it's the opposite. Sorry if I explained it wrong, the game is not important here. I was just justifying why I wanted to keep the big monitor, as opposed to just buying a smaller one.
– 3Nex
Apr 20 '17 at 0:11
As far as brightness is concerned, have you considered something like redshift? For the "black bars" I would try searching through items related to overscan. Typically, this is something people are trying to get rid of, not create, but you might be able to use the same advice to increase overscan.
– b_laoshi
Apr 20 '17 at 0:41
Something along these lines might get you going in the right direction.
– b_laoshi
Apr 20 '17 at 0:50
Redshift is actually an even better solution that I hoped for.xrandr
gave me nothing but errors sayingBadName (named color or font does not exist)
, but I'm more than okay with using Redshift.
– 3Nex
Apr 21 '17 at 1:12
|
show 2 more comments
If your game does not need to be played in fullscreen, maybe setting a black background may help. If you are using a desktop environment that supports it (I don't think Unity does), enable auto-hide on your panels.
– luk3yx
Apr 20 '17 at 0:07
No it's not for the game, it's the opposite. Sorry if I explained it wrong, the game is not important here. I was just justifying why I wanted to keep the big monitor, as opposed to just buying a smaller one.
– 3Nex
Apr 20 '17 at 0:11
As far as brightness is concerned, have you considered something like redshift? For the "black bars" I would try searching through items related to overscan. Typically, this is something people are trying to get rid of, not create, but you might be able to use the same advice to increase overscan.
– b_laoshi
Apr 20 '17 at 0:41
Something along these lines might get you going in the right direction.
– b_laoshi
Apr 20 '17 at 0:50
Redshift is actually an even better solution that I hoped for.xrandr
gave me nothing but errors sayingBadName (named color or font does not exist)
, but I'm more than okay with using Redshift.
– 3Nex
Apr 21 '17 at 1:12
If your game does not need to be played in fullscreen, maybe setting a black background may help. If you are using a desktop environment that supports it (I don't think Unity does), enable auto-hide on your panels.
– luk3yx
Apr 20 '17 at 0:07
If your game does not need to be played in fullscreen, maybe setting a black background may help. If you are using a desktop environment that supports it (I don't think Unity does), enable auto-hide on your panels.
– luk3yx
Apr 20 '17 at 0:07
No it's not for the game, it's the opposite. Sorry if I explained it wrong, the game is not important here. I was just justifying why I wanted to keep the big monitor, as opposed to just buying a smaller one.
– 3Nex
Apr 20 '17 at 0:11
No it's not for the game, it's the opposite. Sorry if I explained it wrong, the game is not important here. I was just justifying why I wanted to keep the big monitor, as opposed to just buying a smaller one.
– 3Nex
Apr 20 '17 at 0:11
As far as brightness is concerned, have you considered something like redshift? For the "black bars" I would try searching through items related to overscan. Typically, this is something people are trying to get rid of, not create, but you might be able to use the same advice to increase overscan.
– b_laoshi
Apr 20 '17 at 0:41
As far as brightness is concerned, have you considered something like redshift? For the "black bars" I would try searching through items related to overscan. Typically, this is something people are trying to get rid of, not create, but you might be able to use the same advice to increase overscan.
– b_laoshi
Apr 20 '17 at 0:41
Something along these lines might get you going in the right direction.
– b_laoshi
Apr 20 '17 at 0:50
Something along these lines might get you going in the right direction.
– b_laoshi
Apr 20 '17 at 0:50
Redshift is actually an even better solution that I hoped for.
xrandr
gave me nothing but errors saying BadName (named color or font does not exist)
, but I'm more than okay with using Redshift.– 3Nex
Apr 21 '17 at 1:12
Redshift is actually an even better solution that I hoped for.
xrandr
gave me nothing but errors saying BadName (named color or font does not exist)
, but I'm more than okay with using Redshift.– 3Nex
Apr 21 '17 at 1:12
|
show 2 more comments
2 Answers
2
active
oldest
votes
I have nvidia, so I can't say for sure that what worked for me will work for you. Differences in capability may also come down to available features offered by the actual monitor as well.
I'll address brightness and overscan separately
Brightness:
If your screen is too bright at night, try a program like redshift. It doesn't reduce backlight. It's a software-based approach to "[adjusting] the color temperature of your screen according to your surroundings." Basically, the screen is less harsh to look at when the sun goes down and there's less ambient light.
Overscan*:
xrandr
is your friend here. Basically, you want to open a terminal, use xrandr to find the overscan property and then set the overscan. Here's how I did it on mine.
In a terminal, run
xrandr --prop
. This will spit out properties for all video output devices, connected or disconnected. Look for the the section pertaining to your connected display. Mine looks like this...
HDMI-0 connected primary 1680x1050+0+0 (normal left inverted right x axis y axis) 474mm x 296mm
CscMatrix: 65536 0 0 0 0 65536 0 0 0 0 65536 0
EDID:
00ffffffffffff005a63248201010101
14140103802f1e782e78f5a655489b26
125054bfef80a940950f950081808140
714f0101010121399030621a274068b0
3600da281100001c000000ff00524d41
3130323030353632390a000000fd0032
4b185211000a202020202020000000fc
00564132323332205365726965730031
BorderDimensions: 4
supported: 4
Border: 0 0 0 0
range: (0, 65535)
SignalFormat: TMDS
supported: TMDS
ConnectorType: HDMI
ConnectorNumber: 1
_ConnectorLocation: 1
1680x1050 59.95*+
1600x1200 60.00
1440x900 74.98 59.89
1280x1024 75.02 60.02
1280x960 60.00
1152x864 75.00
1024x768 75.03 70.07 60.00
800x600 75.00 72.19 60.32 56.25
640x480 75.00 72.81 59.94
HDMI-0
is my output andBorder: 0 0 0 0
is property of interest to me. Beware, properties appear to be case sensitive!
- Now I run
xrandr --output HDMI-0 --set Border 100,100,100,100
, and it creates a 100-pixel black border all the way around my screen. - To reset, I run
xrandr --output HDMI-0 --set Border 0,0,0,0
, and the border is gone.
If you wanted, you could bind these to keyboard shortcuts to turn the overscan on or off.
*Warning: I noticed that when I maximize windows on my screen, the rightmost edge of the window is not visible and falls under the black border. This may be because I have dual monitors though. This is not a problem so long as I do not maximize windows and keep the window moved and resized such that it fits within the visible workspace.
Seems this Borded option is nvidia-specific. I'd like to solve the same issue. But minexrandr --prop
look likeHDMI2 connected primary EDID: 0000.. aspect ratio: Automatic supported: Automatic, 4:3, 16:9 Broadcast RGB: Automatic supported: Automatic, Full, Limited 16:235 audio: auto supported: force-dvi, off, auto, on 1920x1080 ...
and on--set Broders
it threw errorX Error of failed request: BadName (named color or font does not exist)
– Dima Fomin
Apr 23 '17 at 11:45
@DimaFomin, sorry, I don't see any properties there that look like they would accomplish what you're looking for. You might have better luck creating a new question and including the full output ofxrandr --prop
with your question.
– b_laoshi
Apr 25 '17 at 1:57
add a comment |
My xrandr does not support the "Border" prop for HDMI-0.
Attempting this will result in the following error:
$ xrandr --output HDMI-0 --set Border 100,0,100,0
X Error of failed request: BadName (named color or font does not exist)
Major opcode of failed request: 140 (RANDR)
Minor opcode of failed request: 11 (RRQueryOutputProperty)
Serial number of failed request: 41
Current serial number in output stream: 41
However to "shrink" the screen to give yourself black bars, sometimes referred to as pillarboxing, one method is to set a resolution which does not take up the full width of the monitor (e.g. 1024x768 w/ aspect ration 4:3) then set the 'scaling mode' with xrandr
xrandr --output HDMI-0 --set 'scaling mode' 'Full aspect'
This gives me black bars on sides when screen is too wide. I think this will work with any resolution with aspect ratio 4:3. You can also check here for using xrandr to add resolutions not available by default in the display setting.
Also check xrandr --prop
for other properties that might help.
New contributor
add a comment |
Your Answer
StackExchange.ready(function() {
var channelOptions = {
tags: "".split(" "),
id: "89"
};
initTagRenderer("".split(" "), "".split(" "), channelOptions);
StackExchange.using("externalEditor", function() {
// Have to fire editor after snippets, if snippets enabled
if (StackExchange.settings.snippets.snippetsEnabled) {
StackExchange.using("snippets", function() {
createEditor();
});
}
else {
createEditor();
}
});
function createEditor() {
StackExchange.prepareEditor({
heartbeatType: 'answer',
autoActivateHeartbeat: false,
convertImagesToLinks: true,
noModals: true,
showLowRepImageUploadWarning: true,
reputationToPostImages: 10,
bindNavPrevention: true,
postfix: "",
imageUploader: {
brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
allowUrls: true
},
onDemand: true,
discardSelector: ".discard-answer"
,immediatelyShowMarkdownHelp:true
});
}
});
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2faskubuntu.com%2fquestions%2f906816%2fcould-i-have-black-bars-a-k-a-overscan-on-my-monitor-please%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
2 Answers
2
active
oldest
votes
2 Answers
2
active
oldest
votes
active
oldest
votes
active
oldest
votes
I have nvidia, so I can't say for sure that what worked for me will work for you. Differences in capability may also come down to available features offered by the actual monitor as well.
I'll address brightness and overscan separately
Brightness:
If your screen is too bright at night, try a program like redshift. It doesn't reduce backlight. It's a software-based approach to "[adjusting] the color temperature of your screen according to your surroundings." Basically, the screen is less harsh to look at when the sun goes down and there's less ambient light.
Overscan*:
xrandr
is your friend here. Basically, you want to open a terminal, use xrandr to find the overscan property and then set the overscan. Here's how I did it on mine.
In a terminal, run
xrandr --prop
. This will spit out properties for all video output devices, connected or disconnected. Look for the the section pertaining to your connected display. Mine looks like this...
HDMI-0 connected primary 1680x1050+0+0 (normal left inverted right x axis y axis) 474mm x 296mm
CscMatrix: 65536 0 0 0 0 65536 0 0 0 0 65536 0
EDID:
00ffffffffffff005a63248201010101
14140103802f1e782e78f5a655489b26
125054bfef80a940950f950081808140
714f0101010121399030621a274068b0
3600da281100001c000000ff00524d41
3130323030353632390a000000fd0032
4b185211000a202020202020000000fc
00564132323332205365726965730031
BorderDimensions: 4
supported: 4
Border: 0 0 0 0
range: (0, 65535)
SignalFormat: TMDS
supported: TMDS
ConnectorType: HDMI
ConnectorNumber: 1
_ConnectorLocation: 1
1680x1050 59.95*+
1600x1200 60.00
1440x900 74.98 59.89
1280x1024 75.02 60.02
1280x960 60.00
1152x864 75.00
1024x768 75.03 70.07 60.00
800x600 75.00 72.19 60.32 56.25
640x480 75.00 72.81 59.94
HDMI-0
is my output andBorder: 0 0 0 0
is property of interest to me. Beware, properties appear to be case sensitive!
- Now I run
xrandr --output HDMI-0 --set Border 100,100,100,100
, and it creates a 100-pixel black border all the way around my screen. - To reset, I run
xrandr --output HDMI-0 --set Border 0,0,0,0
, and the border is gone.
If you wanted, you could bind these to keyboard shortcuts to turn the overscan on or off.
*Warning: I noticed that when I maximize windows on my screen, the rightmost edge of the window is not visible and falls under the black border. This may be because I have dual monitors though. This is not a problem so long as I do not maximize windows and keep the window moved and resized such that it fits within the visible workspace.
Seems this Borded option is nvidia-specific. I'd like to solve the same issue. But minexrandr --prop
look likeHDMI2 connected primary EDID: 0000.. aspect ratio: Automatic supported: Automatic, 4:3, 16:9 Broadcast RGB: Automatic supported: Automatic, Full, Limited 16:235 audio: auto supported: force-dvi, off, auto, on 1920x1080 ...
and on--set Broders
it threw errorX Error of failed request: BadName (named color or font does not exist)
– Dima Fomin
Apr 23 '17 at 11:45
@DimaFomin, sorry, I don't see any properties there that look like they would accomplish what you're looking for. You might have better luck creating a new question and including the full output ofxrandr --prop
with your question.
– b_laoshi
Apr 25 '17 at 1:57
add a comment |
I have nvidia, so I can't say for sure that what worked for me will work for you. Differences in capability may also come down to available features offered by the actual monitor as well.
I'll address brightness and overscan separately
Brightness:
If your screen is too bright at night, try a program like redshift. It doesn't reduce backlight. It's a software-based approach to "[adjusting] the color temperature of your screen according to your surroundings." Basically, the screen is less harsh to look at when the sun goes down and there's less ambient light.
Overscan*:
xrandr
is your friend here. Basically, you want to open a terminal, use xrandr to find the overscan property and then set the overscan. Here's how I did it on mine.
In a terminal, run
xrandr --prop
. This will spit out properties for all video output devices, connected or disconnected. Look for the the section pertaining to your connected display. Mine looks like this...
HDMI-0 connected primary 1680x1050+0+0 (normal left inverted right x axis y axis) 474mm x 296mm
CscMatrix: 65536 0 0 0 0 65536 0 0 0 0 65536 0
EDID:
00ffffffffffff005a63248201010101
14140103802f1e782e78f5a655489b26
125054bfef80a940950f950081808140
714f0101010121399030621a274068b0
3600da281100001c000000ff00524d41
3130323030353632390a000000fd0032
4b185211000a202020202020000000fc
00564132323332205365726965730031
BorderDimensions: 4
supported: 4
Border: 0 0 0 0
range: (0, 65535)
SignalFormat: TMDS
supported: TMDS
ConnectorType: HDMI
ConnectorNumber: 1
_ConnectorLocation: 1
1680x1050 59.95*+
1600x1200 60.00
1440x900 74.98 59.89
1280x1024 75.02 60.02
1280x960 60.00
1152x864 75.00
1024x768 75.03 70.07 60.00
800x600 75.00 72.19 60.32 56.25
640x480 75.00 72.81 59.94
HDMI-0
is my output andBorder: 0 0 0 0
is property of interest to me. Beware, properties appear to be case sensitive!
- Now I run
xrandr --output HDMI-0 --set Border 100,100,100,100
, and it creates a 100-pixel black border all the way around my screen. - To reset, I run
xrandr --output HDMI-0 --set Border 0,0,0,0
, and the border is gone.
If you wanted, you could bind these to keyboard shortcuts to turn the overscan on or off.
*Warning: I noticed that when I maximize windows on my screen, the rightmost edge of the window is not visible and falls under the black border. This may be because I have dual monitors though. This is not a problem so long as I do not maximize windows and keep the window moved and resized such that it fits within the visible workspace.
Seems this Borded option is nvidia-specific. I'd like to solve the same issue. But minexrandr --prop
look likeHDMI2 connected primary EDID: 0000.. aspect ratio: Automatic supported: Automatic, 4:3, 16:9 Broadcast RGB: Automatic supported: Automatic, Full, Limited 16:235 audio: auto supported: force-dvi, off, auto, on 1920x1080 ...
and on--set Broders
it threw errorX Error of failed request: BadName (named color or font does not exist)
– Dima Fomin
Apr 23 '17 at 11:45
@DimaFomin, sorry, I don't see any properties there that look like they would accomplish what you're looking for. You might have better luck creating a new question and including the full output ofxrandr --prop
with your question.
– b_laoshi
Apr 25 '17 at 1:57
add a comment |
I have nvidia, so I can't say for sure that what worked for me will work for you. Differences in capability may also come down to available features offered by the actual monitor as well.
I'll address brightness and overscan separately
Brightness:
If your screen is too bright at night, try a program like redshift. It doesn't reduce backlight. It's a software-based approach to "[adjusting] the color temperature of your screen according to your surroundings." Basically, the screen is less harsh to look at when the sun goes down and there's less ambient light.
Overscan*:
xrandr
is your friend here. Basically, you want to open a terminal, use xrandr to find the overscan property and then set the overscan. Here's how I did it on mine.
In a terminal, run
xrandr --prop
. This will spit out properties for all video output devices, connected or disconnected. Look for the the section pertaining to your connected display. Mine looks like this...
HDMI-0 connected primary 1680x1050+0+0 (normal left inverted right x axis y axis) 474mm x 296mm
CscMatrix: 65536 0 0 0 0 65536 0 0 0 0 65536 0
EDID:
00ffffffffffff005a63248201010101
14140103802f1e782e78f5a655489b26
125054bfef80a940950f950081808140
714f0101010121399030621a274068b0
3600da281100001c000000ff00524d41
3130323030353632390a000000fd0032
4b185211000a202020202020000000fc
00564132323332205365726965730031
BorderDimensions: 4
supported: 4
Border: 0 0 0 0
range: (0, 65535)
SignalFormat: TMDS
supported: TMDS
ConnectorType: HDMI
ConnectorNumber: 1
_ConnectorLocation: 1
1680x1050 59.95*+
1600x1200 60.00
1440x900 74.98 59.89
1280x1024 75.02 60.02
1280x960 60.00
1152x864 75.00
1024x768 75.03 70.07 60.00
800x600 75.00 72.19 60.32 56.25
640x480 75.00 72.81 59.94
HDMI-0
is my output andBorder: 0 0 0 0
is property of interest to me. Beware, properties appear to be case sensitive!
- Now I run
xrandr --output HDMI-0 --set Border 100,100,100,100
, and it creates a 100-pixel black border all the way around my screen. - To reset, I run
xrandr --output HDMI-0 --set Border 0,0,0,0
, and the border is gone.
If you wanted, you could bind these to keyboard shortcuts to turn the overscan on or off.
*Warning: I noticed that when I maximize windows on my screen, the rightmost edge of the window is not visible and falls under the black border. This may be because I have dual monitors though. This is not a problem so long as I do not maximize windows and keep the window moved and resized such that it fits within the visible workspace.
I have nvidia, so I can't say for sure that what worked for me will work for you. Differences in capability may also come down to available features offered by the actual monitor as well.
I'll address brightness and overscan separately
Brightness:
If your screen is too bright at night, try a program like redshift. It doesn't reduce backlight. It's a software-based approach to "[adjusting] the color temperature of your screen according to your surroundings." Basically, the screen is less harsh to look at when the sun goes down and there's less ambient light.
Overscan*:
xrandr
is your friend here. Basically, you want to open a terminal, use xrandr to find the overscan property and then set the overscan. Here's how I did it on mine.
In a terminal, run
xrandr --prop
. This will spit out properties for all video output devices, connected or disconnected. Look for the the section pertaining to your connected display. Mine looks like this...
HDMI-0 connected primary 1680x1050+0+0 (normal left inverted right x axis y axis) 474mm x 296mm
CscMatrix: 65536 0 0 0 0 65536 0 0 0 0 65536 0
EDID:
00ffffffffffff005a63248201010101
14140103802f1e782e78f5a655489b26
125054bfef80a940950f950081808140
714f0101010121399030621a274068b0
3600da281100001c000000ff00524d41
3130323030353632390a000000fd0032
4b185211000a202020202020000000fc
00564132323332205365726965730031
BorderDimensions: 4
supported: 4
Border: 0 0 0 0
range: (0, 65535)
SignalFormat: TMDS
supported: TMDS
ConnectorType: HDMI
ConnectorNumber: 1
_ConnectorLocation: 1
1680x1050 59.95*+
1600x1200 60.00
1440x900 74.98 59.89
1280x1024 75.02 60.02
1280x960 60.00
1152x864 75.00
1024x768 75.03 70.07 60.00
800x600 75.00 72.19 60.32 56.25
640x480 75.00 72.81 59.94
HDMI-0
is my output andBorder: 0 0 0 0
is property of interest to me. Beware, properties appear to be case sensitive!
- Now I run
xrandr --output HDMI-0 --set Border 100,100,100,100
, and it creates a 100-pixel black border all the way around my screen. - To reset, I run
xrandr --output HDMI-0 --set Border 0,0,0,0
, and the border is gone.
If you wanted, you could bind these to keyboard shortcuts to turn the overscan on or off.
*Warning: I noticed that when I maximize windows on my screen, the rightmost edge of the window is not visible and falls under the black border. This may be because I have dual monitors though. This is not a problem so long as I do not maximize windows and keep the window moved and resized such that it fits within the visible workspace.
edited Apr 21 '17 at 1:29
answered Apr 20 '17 at 1:50
b_laoshib_laoshi
2,642928
2,642928
Seems this Borded option is nvidia-specific. I'd like to solve the same issue. But minexrandr --prop
look likeHDMI2 connected primary EDID: 0000.. aspect ratio: Automatic supported: Automatic, 4:3, 16:9 Broadcast RGB: Automatic supported: Automatic, Full, Limited 16:235 audio: auto supported: force-dvi, off, auto, on 1920x1080 ...
and on--set Broders
it threw errorX Error of failed request: BadName (named color or font does not exist)
– Dima Fomin
Apr 23 '17 at 11:45
@DimaFomin, sorry, I don't see any properties there that look like they would accomplish what you're looking for. You might have better luck creating a new question and including the full output ofxrandr --prop
with your question.
– b_laoshi
Apr 25 '17 at 1:57
add a comment |
Seems this Borded option is nvidia-specific. I'd like to solve the same issue. But minexrandr --prop
look likeHDMI2 connected primary EDID: 0000.. aspect ratio: Automatic supported: Automatic, 4:3, 16:9 Broadcast RGB: Automatic supported: Automatic, Full, Limited 16:235 audio: auto supported: force-dvi, off, auto, on 1920x1080 ...
and on--set Broders
it threw errorX Error of failed request: BadName (named color or font does not exist)
– Dima Fomin
Apr 23 '17 at 11:45
@DimaFomin, sorry, I don't see any properties there that look like they would accomplish what you're looking for. You might have better luck creating a new question and including the full output ofxrandr --prop
with your question.
– b_laoshi
Apr 25 '17 at 1:57
Seems this Borded option is nvidia-specific. I'd like to solve the same issue. But mine
xrandr --prop
look like HDMI2 connected primary EDID: 0000.. aspect ratio: Automatic supported: Automatic, 4:3, 16:9 Broadcast RGB: Automatic supported: Automatic, Full, Limited 16:235 audio: auto supported: force-dvi, off, auto, on 1920x1080 ...
and on --set Broders
it threw error X Error of failed request: BadName (named color or font does not exist)
– Dima Fomin
Apr 23 '17 at 11:45
Seems this Borded option is nvidia-specific. I'd like to solve the same issue. But mine
xrandr --prop
look like HDMI2 connected primary EDID: 0000.. aspect ratio: Automatic supported: Automatic, 4:3, 16:9 Broadcast RGB: Automatic supported: Automatic, Full, Limited 16:235 audio: auto supported: force-dvi, off, auto, on 1920x1080 ...
and on --set Broders
it threw error X Error of failed request: BadName (named color or font does not exist)
– Dima Fomin
Apr 23 '17 at 11:45
@DimaFomin, sorry, I don't see any properties there that look like they would accomplish what you're looking for. You might have better luck creating a new question and including the full output of
xrandr --prop
with your question.– b_laoshi
Apr 25 '17 at 1:57
@DimaFomin, sorry, I don't see any properties there that look like they would accomplish what you're looking for. You might have better luck creating a new question and including the full output of
xrandr --prop
with your question.– b_laoshi
Apr 25 '17 at 1:57
add a comment |
My xrandr does not support the "Border" prop for HDMI-0.
Attempting this will result in the following error:
$ xrandr --output HDMI-0 --set Border 100,0,100,0
X Error of failed request: BadName (named color or font does not exist)
Major opcode of failed request: 140 (RANDR)
Minor opcode of failed request: 11 (RRQueryOutputProperty)
Serial number of failed request: 41
Current serial number in output stream: 41
However to "shrink" the screen to give yourself black bars, sometimes referred to as pillarboxing, one method is to set a resolution which does not take up the full width of the monitor (e.g. 1024x768 w/ aspect ration 4:3) then set the 'scaling mode' with xrandr
xrandr --output HDMI-0 --set 'scaling mode' 'Full aspect'
This gives me black bars on sides when screen is too wide. I think this will work with any resolution with aspect ratio 4:3. You can also check here for using xrandr to add resolutions not available by default in the display setting.
Also check xrandr --prop
for other properties that might help.
New contributor
add a comment |
My xrandr does not support the "Border" prop for HDMI-0.
Attempting this will result in the following error:
$ xrandr --output HDMI-0 --set Border 100,0,100,0
X Error of failed request: BadName (named color or font does not exist)
Major opcode of failed request: 140 (RANDR)
Minor opcode of failed request: 11 (RRQueryOutputProperty)
Serial number of failed request: 41
Current serial number in output stream: 41
However to "shrink" the screen to give yourself black bars, sometimes referred to as pillarboxing, one method is to set a resolution which does not take up the full width of the monitor (e.g. 1024x768 w/ aspect ration 4:3) then set the 'scaling mode' with xrandr
xrandr --output HDMI-0 --set 'scaling mode' 'Full aspect'
This gives me black bars on sides when screen is too wide. I think this will work with any resolution with aspect ratio 4:3. You can also check here for using xrandr to add resolutions not available by default in the display setting.
Also check xrandr --prop
for other properties that might help.
New contributor
add a comment |
My xrandr does not support the "Border" prop for HDMI-0.
Attempting this will result in the following error:
$ xrandr --output HDMI-0 --set Border 100,0,100,0
X Error of failed request: BadName (named color or font does not exist)
Major opcode of failed request: 140 (RANDR)
Minor opcode of failed request: 11 (RRQueryOutputProperty)
Serial number of failed request: 41
Current serial number in output stream: 41
However to "shrink" the screen to give yourself black bars, sometimes referred to as pillarboxing, one method is to set a resolution which does not take up the full width of the monitor (e.g. 1024x768 w/ aspect ration 4:3) then set the 'scaling mode' with xrandr
xrandr --output HDMI-0 --set 'scaling mode' 'Full aspect'
This gives me black bars on sides when screen is too wide. I think this will work with any resolution with aspect ratio 4:3. You can also check here for using xrandr to add resolutions not available by default in the display setting.
Also check xrandr --prop
for other properties that might help.
New contributor
My xrandr does not support the "Border" prop for HDMI-0.
Attempting this will result in the following error:
$ xrandr --output HDMI-0 --set Border 100,0,100,0
X Error of failed request: BadName (named color or font does not exist)
Major opcode of failed request: 140 (RANDR)
Minor opcode of failed request: 11 (RRQueryOutputProperty)
Serial number of failed request: 41
Current serial number in output stream: 41
However to "shrink" the screen to give yourself black bars, sometimes referred to as pillarboxing, one method is to set a resolution which does not take up the full width of the monitor (e.g. 1024x768 w/ aspect ration 4:3) then set the 'scaling mode' with xrandr
xrandr --output HDMI-0 --set 'scaling mode' 'Full aspect'
This gives me black bars on sides when screen is too wide. I think this will work with any resolution with aspect ratio 4:3. You can also check here for using xrandr to add resolutions not available by default in the display setting.
Also check xrandr --prop
for other properties that might help.
New contributor
New contributor
answered 3 hours ago
jason120jason120
11
11
New contributor
New contributor
add a comment |
add a comment |
Thanks for contributing an answer to Ask Ubuntu!
- Please be sure to answer the question. Provide details and share your research!
But avoid …
- Asking for help, clarification, or responding to other answers.
- Making statements based on opinion; back them up with references or personal experience.
To learn more, see our tips on writing great answers.
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2faskubuntu.com%2fquestions%2f906816%2fcould-i-have-black-bars-a-k-a-overscan-on-my-monitor-please%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
If your game does not need to be played in fullscreen, maybe setting a black background may help. If you are using a desktop environment that supports it (I don't think Unity does), enable auto-hide on your panels.
– luk3yx
Apr 20 '17 at 0:07
No it's not for the game, it's the opposite. Sorry if I explained it wrong, the game is not important here. I was just justifying why I wanted to keep the big monitor, as opposed to just buying a smaller one.
– 3Nex
Apr 20 '17 at 0:11
As far as brightness is concerned, have you considered something like redshift? For the "black bars" I would try searching through items related to overscan. Typically, this is something people are trying to get rid of, not create, but you might be able to use the same advice to increase overscan.
– b_laoshi
Apr 20 '17 at 0:41
Something along these lines might get you going in the right direction.
– b_laoshi
Apr 20 '17 at 0:50
Redshift is actually an even better solution that I hoped for.
xrandr
gave me nothing but errors sayingBadName (named color or font does not exist)
, but I'm more than okay with using Redshift.– 3Nex
Apr 21 '17 at 1:12