-
Notifications
You must be signed in to change notification settings - Fork 13
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
[Enhancement] Add Overscan/Underscan support #156
Comments
Unfortunately there doesn't appear to be API to do this in wlroots or wayland. My guess is that it's not a necessary use case ~2018. It would likely result in a distorted image on an LCD monitor, only being appropriate for a CRT monitor. What's your use case here? What video card / laptop / machine are you using? Which monitor are you using? Can you experiment with a different machine and a different monitor? |
It may be possible with some hackitry around a custom mode and position however sway would get upset with that as it assumes contiguous displays - any gap will result in difficulties like #146 |
I see, I've been tinkering for a while now but haven't figured anything out. Short of buying a display that supports software overscan settings. The current display I'm using is a Toshiba 40CV550A, from 2009. Maybe I can find a new one that works from this decade that is affordable. |
I see. Looking at the manual that TV doesn't mention overscan. Smart features are Bad News. I don't think I can justify writing a lot of hacky code to support 15 year old hardware. Overscan seems like a bizarre feature from marketing rather than product management... If you're short on money could you look at a more recent TV at, say, a thrift shop? My neighbours just gave away their old TV when they upgraded! |
Currently, it seems only X11 tools have overscan support.
Using way-displays on a 1080p external monitor, set to 1080p, has the edges cut off.
Scaling to 0.75 doesn't seem to work as a way to mitigate the cropping.
Not many displays offer a setting for overscan or "pc mode", so a software solution would be needed in this case.
The text was updated successfully, but these errors were encountered: