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

Fix refresrate changing #16034

Closed
wants to merge 4 commits into from
Closed

Fix refresrate changing #16034

wants to merge 4 commits into from

Conversation

fritsch
Copy link
Member

@fritsch fritsch commented May 2, 2019

During below additions the logic was flawed in a sense that 3:2 pulldown was evaluated too early. Means if you run at 60hz it would never switch to 24 hz and if you run at 59.94 hz it would never switch to 23.976, etc.

This reverts the mixed in logic, corrects the prints and uses the 3:2 as a final path.

@fritsch fritsch requested review from lrusak and peak3d May 2, 2019 04:55
@fritsch
Copy link
Member Author

fritsch commented May 2, 2019

@fritsch
Copy link
Member Author

fritsch commented May 2, 2019

@lrusak okay with the added commit?

@lrusak
Copy link
Contributor

lrusak commented May 2, 2019

@lrusak okay with the added commit?

Yes thanks :) I didn't realize that the the code was part of a revert initially

Also, my 2 cents, I feel that the whitelist has become abused and turned into something it wasn't supposed to be (the catch all solution like we had before). The whole point of the whitelist was to add control and predictability to mode switching. I feel that we have lost this.

I think we need to look at it again and take a look at all the possible problems with mode switching and what solutions are available. If we need to add an extra setting or some other custom controls then so be it. We cannot keep adding exceptions to the whitelist.

@fritsch
Copy link
Member Author

fritsch commented May 2, 2019

I concurr here a bit.

Whitelist: Add modes you like to switch to
Resolution.cpp: Find the best mode depending on the selected modes. This is currently: direct, double, pulldown.

What exception do you see?

@fritsch
Copy link
Member Author

fritsch commented May 2, 2019

After discussion with @peak3d I close this one. There is no sense in deciding between "half bullshittish solutions" and "40% bullshittish solutions".

For Leia - please decide what the team likes best :-)

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

Successfully merging this pull request may close these issues.

None yet

2 participants