Skip to content
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

Terminal Image display has low resolution #210672

Open
albert-ying opened this issue Apr 18, 2024 · 7 comments
Open

Terminal Image display has low resolution #210672

albert-ying opened this issue Apr 18, 2024 · 7 comments
Assignees
Labels
terminal-rendering upstream Issue identified as 'upstream' component related (exists outside of VS Code) upstream-issue-linked This is an upstream issue that has been reported upstream
Milestone

Comments

@albert-ying
Copy link

albert-ying commented Apr 18, 2024

Does this issue occur when all extensions are disabled?: Yes/No

  • VS Code Version: 1.88.1
  • OS Version: Mac: Universal Intel silicon

Steps to Reproduce:

  1. imgcat "anyimage.png"

Original image:

download

In VScode terminal

CleanShot 2024-04-18 at 12 08 01@2x

In Iterm2 terminal

CleanShot 2024-04-18 at 12 09 17@2x

@VSCodeTriageBot
Copy link
Collaborator

Thanks for creating this issue! It looks like you may be using an old version of VS Code, the latest stable release is 1.88.1. Please try upgrading to the latest version and checking whether this issue remains.

Happy Coding!

@meganrogge
Copy link
Contributor

does changing the value of terminal.integrated.gpuAcceleration fix it?

@meganrogge meganrogge added the info-needed Issue requires more information from poster label Apr 18, 2024
@albert-ying
Copy link
Author

does changing the value of terminal.integrated.gpuAcceleration fix it?

No it doesnt

@Tyriar
Copy link
Member

Tyriar commented Apr 19, 2024

Upstream: xtermjs/xterm.js#5035

@Tyriar Tyriar added upstream Issue identified as 'upstream' component related (exists outside of VS Code) upstream-issue-linked This is an upstream issue that has been reported upstream terminal-rendering and removed info-needed Issue requires more information from poster labels Apr 19, 2024
@Tyriar Tyriar added this to the Backlog milestone Apr 19, 2024
@jerch
Copy link

jerch commented Apr 19, 2024

@albert-ying Whats your screen DPR on the machine, where this happens?

@Tyriar I think this is related to css pixels vs. screen pixels. The image addon currently uses css pixels for backend size propagation, thus image will blur if DPR is really high (e.g. a css pixel gets overly stretched on the screen).

@albert-ying
Copy link
Author

It is 2 (4k screen)

@jerch
Copy link

jerch commented Apr 19, 2024

I see, so you get only half of the pixel density compared to iterm2. Imho the measurement could be changed to account for DPR in IIP (iterm's image protocol), but I am currently unsure about implications on the sixel format. The issue is that the pixel size escape sequences work with css pixels across the whole terminal, not only for images, and I am unsure if that can easily be changed to device metrics / real screen pixels.

Lets follow that in xtermjs/xterm.js#5035

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
terminal-rendering upstream Issue identified as 'upstream' component related (exists outside of VS Code) upstream-issue-linked This is an upstream issue that has been reported upstream
Projects
None yet
Development

No branches or pull requests

5 participants