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

PP not choosing the best screen mode when specifying screen_mode #44

Open
zhouruixi opened this issue Jan 2, 2025 · 2 comments
Open

Comments

@zhouruixi
Copy link

zhouruixi commented Jan 2, 2025

Using drm_info, It shows my monitor supports the following modes:
│ │ ├───1920x1080@59.94 preferred driver phsync pvsync 16:9
│ │ ├───1920x1080@60.00 driver phsync pvsync
│ │ ├───1920x1080@60.00 driver phsync pvsync 16:9
│ │ ├───1920x1080@60.00 driver phsync pvsync interlace 16:9
│ │ ├───1920x1080@59.94 driver phsync pvsync interlace 16:9

Run pp without specifying screm_mode, The monitor shows 1920x1080@60Hz.
Run pp with --screen-mode 1920x1080@60Hz, The monitor shows 1080i60.

So, PixelPilot_rk choosing the 1920x1080@60.00 interlace mode, which is not the best. We should prefer using non-interlaced mode at the same resolution and refresh rate. And PixelPilot_rk not support --screen-mode 1920x1080@59.94

@henkwiedig
Copy link
Contributor

I already implemented a fallback mode here: b346c44

@zhouruixi
Copy link
Author

zhouruixi commented Jan 4, 2025

I already implemented a fallback mode here: b346c44

What I want to talk about is not the fallback screen mode. 1920x1080@60.00 driver phsync pvsync, 1920x1080@60.00 driver phsync pvsync 16:9 and 1920x1080@60.00 driver phsync pvsync interlace 16:9 are all named 1920x1080@60, when using --screen-mode 1920x1080@60, PP_rk is working but use 1920x1080@60.00 driver phsync pvsync interlace 16:9, however 1920x1080@60.00 driver phsync pvsync or 1920x1080@60.00 driver phsync pvsync 16:9 which without interlace is better.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants