Prevent xrandr scaling from becoming blurryxrandr doesn't detect monitor on hdmi portMirror dual monitors...
Do I have an "anti-research" personality?
What does ゆーか mean?
Was there a shared-world project before "Thieves World"?
Why did C use the -> operator instead of reusing the . operator?
A strange hotel
Should the Death Curse affect an undead PC in the Tomb of Annihilation adventure?
How to write a column outside the braces in a matrix?
Pulling the rope with one hand is as heavy as with two hands?
Aliens crash on Earth and go into stasis to wait for technology to fix their ship
Minor Revision with suggestion of an alternative proof by reviewer
Is there really no use for MD5 anymore?
How can I practically buy stocks?
Is Diceware more secure than a long passphrase?
What are the steps to solving this definite integral?
Philosophical question on logistic regression: why isn't the optimal threshold value trained?
Does a large simulator bay have standard public address announcements?
What happens to Mjolnir (Thor's hammer) at the end of Endgame?
Alignment of various blocks in tikz
Check if a string is entirely made of the same substring
Re-entry to Germany after vacation using blue card
How to not starve gigantic beasts
Could the terminal length of components like resistors be reduced?
What makes accurate emulation of old systems a difficult task?
What is causing the white spot to appear in some of my pictures
Prevent xrandr scaling from becoming blurry
xrandr doesn't detect monitor on hdmi portMirror dual monitors with different resolutionsBlurry image between Radeon / DVI-to-HDMI / LG LCD monitorxrandr not activating laptop displayReset xrandr (or: switch off the --scale-from setting at disconnect)Why xrandr numerical output is VGA-1 instead of VGA1?Cannot turn on external display with xrandrUsing xrandr to scale screen along Yxrandr “can't open display” when changing native laptop screen resolutionxrandr with second window above, maximising problem
.everyoneloves__top-leaderboard:empty,.everyoneloves__mid-leaderboard:empty,.everyoneloves__bot-mid-leaderboard:empty{ margin-bottom:0;
}
I am attempting to connect a laptop with a LVDS1 resolution of 1366x768 to a HDMI1 resolution of 1920x1080 (hardware that HDMI1 is connected to is a 4k Samsung TV).
I am trying to clone my laptops LVDS1 display to the TV without the scale blurring.
When running
xrandr --output HDMI1 --auto --scale-from 1366x768
The output does fill the entire TV with 1080p resolution but the text is a bit blurred and everything seems blown up in size.
When running
xrandr --output LVDS1 --auto --output HDMI1 --auto --right-of LVDS1
The output also fills the entire TV with 1080p resolution, but this time the text is perfectly clear and the UI and other aspects of the system is not fuzzy/blurry and seems to be proper in size (the UI is physically smaller and sharper on screen).
The problem with the second method is that it adds the TV as a new monitor on its own virtual desktop in i3. This means that if I am doing a presentation I have to make sure that I have that virtual desktop selected to manipulate it. EVEN WORSE is that I can't view the display on my laptops monitor so I have to do all the work blind.
Is there a way to clone the monitor as with the first command so that the TV replicates the vision I get on the laptop, but with the clarity and sharpness of the second command?
Thanks
linux x11 xrandr i3 hdmi
bumped to the homepage by Community♦ 32 mins ago
This question has answers that may be good or bad; the system has marked it active so that they can be reviewed.
add a comment |
I am attempting to connect a laptop with a LVDS1 resolution of 1366x768 to a HDMI1 resolution of 1920x1080 (hardware that HDMI1 is connected to is a 4k Samsung TV).
I am trying to clone my laptops LVDS1 display to the TV without the scale blurring.
When running
xrandr --output HDMI1 --auto --scale-from 1366x768
The output does fill the entire TV with 1080p resolution but the text is a bit blurred and everything seems blown up in size.
When running
xrandr --output LVDS1 --auto --output HDMI1 --auto --right-of LVDS1
The output also fills the entire TV with 1080p resolution, but this time the text is perfectly clear and the UI and other aspects of the system is not fuzzy/blurry and seems to be proper in size (the UI is physically smaller and sharper on screen).
The problem with the second method is that it adds the TV as a new monitor on its own virtual desktop in i3. This means that if I am doing a presentation I have to make sure that I have that virtual desktop selected to manipulate it. EVEN WORSE is that I can't view the display on my laptops monitor so I have to do all the work blind.
Is there a way to clone the monitor as with the first command so that the TV replicates the vision I get on the laptop, but with the clarity and sharpness of the second command?
Thanks
linux x11 xrandr i3 hdmi
bumped to the homepage by Community♦ 32 mins ago
This question has answers that may be good or bad; the system has marked it active so that they can be reviewed.
add a comment |
I am attempting to connect a laptop with a LVDS1 resolution of 1366x768 to a HDMI1 resolution of 1920x1080 (hardware that HDMI1 is connected to is a 4k Samsung TV).
I am trying to clone my laptops LVDS1 display to the TV without the scale blurring.
When running
xrandr --output HDMI1 --auto --scale-from 1366x768
The output does fill the entire TV with 1080p resolution but the text is a bit blurred and everything seems blown up in size.
When running
xrandr --output LVDS1 --auto --output HDMI1 --auto --right-of LVDS1
The output also fills the entire TV with 1080p resolution, but this time the text is perfectly clear and the UI and other aspects of the system is not fuzzy/blurry and seems to be proper in size (the UI is physically smaller and sharper on screen).
The problem with the second method is that it adds the TV as a new monitor on its own virtual desktop in i3. This means that if I am doing a presentation I have to make sure that I have that virtual desktop selected to manipulate it. EVEN WORSE is that I can't view the display on my laptops monitor so I have to do all the work blind.
Is there a way to clone the monitor as with the first command so that the TV replicates the vision I get on the laptop, but with the clarity and sharpness of the second command?
Thanks
linux x11 xrandr i3 hdmi
I am attempting to connect a laptop with a LVDS1 resolution of 1366x768 to a HDMI1 resolution of 1920x1080 (hardware that HDMI1 is connected to is a 4k Samsung TV).
I am trying to clone my laptops LVDS1 display to the TV without the scale blurring.
When running
xrandr --output HDMI1 --auto --scale-from 1366x768
The output does fill the entire TV with 1080p resolution but the text is a bit blurred and everything seems blown up in size.
When running
xrandr --output LVDS1 --auto --output HDMI1 --auto --right-of LVDS1
The output also fills the entire TV with 1080p resolution, but this time the text is perfectly clear and the UI and other aspects of the system is not fuzzy/blurry and seems to be proper in size (the UI is physically smaller and sharper on screen).
The problem with the second method is that it adds the TV as a new monitor on its own virtual desktop in i3. This means that if I am doing a presentation I have to make sure that I have that virtual desktop selected to manipulate it. EVEN WORSE is that I can't view the display on my laptops monitor so I have to do all the work blind.
Is there a way to clone the monitor as with the first command so that the TV replicates the vision I get on the laptop, but with the clarity and sharpness of the second command?
Thanks
linux x11 xrandr i3 hdmi
linux x11 xrandr i3 hdmi
asked Oct 22 '18 at 18:39
user102873891user102873891
1
1
bumped to the homepage by Community♦ 32 mins ago
This question has answers that may be good or bad; the system has marked it active so that they can be reviewed.
bumped to the homepage by Community♦ 32 mins ago
This question has answers that may be good or bad; the system has marked it active so that they can be reviewed.
add a comment |
add a comment |
1 Answer
1
active
oldest
votes
All scaling is going to look blurry. That's because it's inherently what happens if you try to make 1.3 pixels out of one pixel. You can improve the results with a bit of filtering, but it will always be worse quality.
What (likely, there's not enough info) happens with the second line is that the output won't use scaling, instead it will use the correct resolution and additional framebuffer.
Options:
- Find out the physical resolution of your TV (it's likely to be 1920x1080, but can be smaller for cheaper/smaller TVs).
- Find out what logical resolutions your TV supports (look into
Xorg.log
). It will likely be more than 1920x1080. - Find a logical resolution that will map 1366x768 to your physical TV resolution in the best way. Try this resolution. Scaler and filters in the TV will be better than than the scaler in X.
- Use this resolution to clone your complete display (centered, smaller).
Thanks for the input. A second framebuffer for the second command makes sense to me as well. With this being said I wonder if it is possible to have X create a second framebuffer that simply redraws everything in the second resolution and tell xrandr or X to output the contents of that buffer to the HDMI port. If it was so that a second frame buffer was created for the second command, I don't see why I couldn't manually tell X to draw both FB with the exact same contents only differing by resolution and present one to LVDS1 and the other to HDMI1.
– user102873891
Oct 24 '18 at 0:24
Well, you can't draw the "exact same content" in two different resolutions - the content has to be different for different resolutions. You'd have to tell each application to render each element twice, using different font sizes etc. So that won't work. You need some form of scaling to duplicate an image at different resolutions, and the best you can do is pick ratios that minimize blur, and display paths that have good scalers and filters (like the in-built resolution scaling in the TV).
– dirkt
Oct 24 '18 at 5:21
add a comment |
Your Answer
StackExchange.ready(function() {
var channelOptions = {
tags: "".split(" "),
id: "106"
};
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: false,
noModals: true,
showLowRepImageUploadWarning: true,
reputationToPostImages: null,
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%2funix.stackexchange.com%2fquestions%2f477108%2fprevent-xrandr-scaling-from-becoming-blurry%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
1 Answer
1
active
oldest
votes
1 Answer
1
active
oldest
votes
active
oldest
votes
active
oldest
votes
All scaling is going to look blurry. That's because it's inherently what happens if you try to make 1.3 pixels out of one pixel. You can improve the results with a bit of filtering, but it will always be worse quality.
What (likely, there's not enough info) happens with the second line is that the output won't use scaling, instead it will use the correct resolution and additional framebuffer.
Options:
- Find out the physical resolution of your TV (it's likely to be 1920x1080, but can be smaller for cheaper/smaller TVs).
- Find out what logical resolutions your TV supports (look into
Xorg.log
). It will likely be more than 1920x1080. - Find a logical resolution that will map 1366x768 to your physical TV resolution in the best way. Try this resolution. Scaler and filters in the TV will be better than than the scaler in X.
- Use this resolution to clone your complete display (centered, smaller).
Thanks for the input. A second framebuffer for the second command makes sense to me as well. With this being said I wonder if it is possible to have X create a second framebuffer that simply redraws everything in the second resolution and tell xrandr or X to output the contents of that buffer to the HDMI port. If it was so that a second frame buffer was created for the second command, I don't see why I couldn't manually tell X to draw both FB with the exact same contents only differing by resolution and present one to LVDS1 and the other to HDMI1.
– user102873891
Oct 24 '18 at 0:24
Well, you can't draw the "exact same content" in two different resolutions - the content has to be different for different resolutions. You'd have to tell each application to render each element twice, using different font sizes etc. So that won't work. You need some form of scaling to duplicate an image at different resolutions, and the best you can do is pick ratios that minimize blur, and display paths that have good scalers and filters (like the in-built resolution scaling in the TV).
– dirkt
Oct 24 '18 at 5:21
add a comment |
All scaling is going to look blurry. That's because it's inherently what happens if you try to make 1.3 pixels out of one pixel. You can improve the results with a bit of filtering, but it will always be worse quality.
What (likely, there's not enough info) happens with the second line is that the output won't use scaling, instead it will use the correct resolution and additional framebuffer.
Options:
- Find out the physical resolution of your TV (it's likely to be 1920x1080, but can be smaller for cheaper/smaller TVs).
- Find out what logical resolutions your TV supports (look into
Xorg.log
). It will likely be more than 1920x1080. - Find a logical resolution that will map 1366x768 to your physical TV resolution in the best way. Try this resolution. Scaler and filters in the TV will be better than than the scaler in X.
- Use this resolution to clone your complete display (centered, smaller).
Thanks for the input. A second framebuffer for the second command makes sense to me as well. With this being said I wonder if it is possible to have X create a second framebuffer that simply redraws everything in the second resolution and tell xrandr or X to output the contents of that buffer to the HDMI port. If it was so that a second frame buffer was created for the second command, I don't see why I couldn't manually tell X to draw both FB with the exact same contents only differing by resolution and present one to LVDS1 and the other to HDMI1.
– user102873891
Oct 24 '18 at 0:24
Well, you can't draw the "exact same content" in two different resolutions - the content has to be different for different resolutions. You'd have to tell each application to render each element twice, using different font sizes etc. So that won't work. You need some form of scaling to duplicate an image at different resolutions, and the best you can do is pick ratios that minimize blur, and display paths that have good scalers and filters (like the in-built resolution scaling in the TV).
– dirkt
Oct 24 '18 at 5:21
add a comment |
All scaling is going to look blurry. That's because it's inherently what happens if you try to make 1.3 pixels out of one pixel. You can improve the results with a bit of filtering, but it will always be worse quality.
What (likely, there's not enough info) happens with the second line is that the output won't use scaling, instead it will use the correct resolution and additional framebuffer.
Options:
- Find out the physical resolution of your TV (it's likely to be 1920x1080, but can be smaller for cheaper/smaller TVs).
- Find out what logical resolutions your TV supports (look into
Xorg.log
). It will likely be more than 1920x1080. - Find a logical resolution that will map 1366x768 to your physical TV resolution in the best way. Try this resolution. Scaler and filters in the TV will be better than than the scaler in X.
- Use this resolution to clone your complete display (centered, smaller).
All scaling is going to look blurry. That's because it's inherently what happens if you try to make 1.3 pixels out of one pixel. You can improve the results with a bit of filtering, but it will always be worse quality.
What (likely, there's not enough info) happens with the second line is that the output won't use scaling, instead it will use the correct resolution and additional framebuffer.
Options:
- Find out the physical resolution of your TV (it's likely to be 1920x1080, but can be smaller for cheaper/smaller TVs).
- Find out what logical resolutions your TV supports (look into
Xorg.log
). It will likely be more than 1920x1080. - Find a logical resolution that will map 1366x768 to your physical TV resolution in the best way. Try this resolution. Scaler and filters in the TV will be better than than the scaler in X.
- Use this resolution to clone your complete display (centered, smaller).
answered Oct 23 '18 at 8:41
dirktdirkt
17.6k31438
17.6k31438
Thanks for the input. A second framebuffer for the second command makes sense to me as well. With this being said I wonder if it is possible to have X create a second framebuffer that simply redraws everything in the second resolution and tell xrandr or X to output the contents of that buffer to the HDMI port. If it was so that a second frame buffer was created for the second command, I don't see why I couldn't manually tell X to draw both FB with the exact same contents only differing by resolution and present one to LVDS1 and the other to HDMI1.
– user102873891
Oct 24 '18 at 0:24
Well, you can't draw the "exact same content" in two different resolutions - the content has to be different for different resolutions. You'd have to tell each application to render each element twice, using different font sizes etc. So that won't work. You need some form of scaling to duplicate an image at different resolutions, and the best you can do is pick ratios that minimize blur, and display paths that have good scalers and filters (like the in-built resolution scaling in the TV).
– dirkt
Oct 24 '18 at 5:21
add a comment |
Thanks for the input. A second framebuffer for the second command makes sense to me as well. With this being said I wonder if it is possible to have X create a second framebuffer that simply redraws everything in the second resolution and tell xrandr or X to output the contents of that buffer to the HDMI port. If it was so that a second frame buffer was created for the second command, I don't see why I couldn't manually tell X to draw both FB with the exact same contents only differing by resolution and present one to LVDS1 and the other to HDMI1.
– user102873891
Oct 24 '18 at 0:24
Well, you can't draw the "exact same content" in two different resolutions - the content has to be different for different resolutions. You'd have to tell each application to render each element twice, using different font sizes etc. So that won't work. You need some form of scaling to duplicate an image at different resolutions, and the best you can do is pick ratios that minimize blur, and display paths that have good scalers and filters (like the in-built resolution scaling in the TV).
– dirkt
Oct 24 '18 at 5:21
Thanks for the input. A second framebuffer for the second command makes sense to me as well. With this being said I wonder if it is possible to have X create a second framebuffer that simply redraws everything in the second resolution and tell xrandr or X to output the contents of that buffer to the HDMI port. If it was so that a second frame buffer was created for the second command, I don't see why I couldn't manually tell X to draw both FB with the exact same contents only differing by resolution and present one to LVDS1 and the other to HDMI1.
– user102873891
Oct 24 '18 at 0:24
Thanks for the input. A second framebuffer for the second command makes sense to me as well. With this being said I wonder if it is possible to have X create a second framebuffer that simply redraws everything in the second resolution and tell xrandr or X to output the contents of that buffer to the HDMI port. If it was so that a second frame buffer was created for the second command, I don't see why I couldn't manually tell X to draw both FB with the exact same contents only differing by resolution and present one to LVDS1 and the other to HDMI1.
– user102873891
Oct 24 '18 at 0:24
Well, you can't draw the "exact same content" in two different resolutions - the content has to be different for different resolutions. You'd have to tell each application to render each element twice, using different font sizes etc. So that won't work. You need some form of scaling to duplicate an image at different resolutions, and the best you can do is pick ratios that minimize blur, and display paths that have good scalers and filters (like the in-built resolution scaling in the TV).
– dirkt
Oct 24 '18 at 5:21
Well, you can't draw the "exact same content" in two different resolutions - the content has to be different for different resolutions. You'd have to tell each application to render each element twice, using different font sizes etc. So that won't work. You need some form of scaling to duplicate an image at different resolutions, and the best you can do is pick ratios that minimize blur, and display paths that have good scalers and filters (like the in-built resolution scaling in the TV).
– dirkt
Oct 24 '18 at 5:21
add a comment |
Thanks for contributing an answer to Unix & Linux Stack Exchange!
- 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%2funix.stackexchange.com%2fquestions%2f477108%2fprevent-xrandr-scaling-from-becoming-blurry%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