Skip to content

Conversation

@koying
Copy link
Contributor

@koying koying commented Mar 21, 2019

@davilla You opinion on this?
The idea is:

  1. try harder to find out interlaced
  2. if interlaced, double the fps
  3. if not, adjust refresh rate to closest, not doubled

If think those "motion smoother" TV algorithms get confused with, eg 25 fps on 50Hz, so induce hiccups

@koying koying requested a review from davilla March 21, 2019 10:40
@davilla
Copy link
Collaborator

davilla commented Mar 21, 2019

Sure, defaulting to a double value was originally to keep gui updates smooth.
The only real issue with interlace detection are those odd h264's that 'might' be interlaced and you can only tell when actually decoding.

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.

3 participants