Skip to content
GitLab
Projects Groups Snippets
  • /
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in / Register
  • P PyAV
  • Project information
    • Project information
    • Activity
    • Labels
    • Members
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
  • Issues 37
    • Issues 37
    • List
    • Boards
    • Service Desk
    • Milestones
  • Merge requests 26
    • Merge requests 26
  • CI/CD
    • CI/CD
    • Pipelines
    • Jobs
    • Schedules
  • Deployments
    • Deployments
    • Environments
    • Releases
  • Packages and registries
    • Packages and registries
    • Package Registry
    • Infrastructure Registry
  • Monitor
    • Monitor
    • Incidents
  • Analytics
    • Analytics
    • Value stream
    • CI/CD
    • Repository
  • Wiki
    • Wiki
  • Snippets
    • Snippets
  • Activity
  • Graph
  • Create a new issue
  • Jobs
  • Commits
  • Issue Boards
Collapse sidebar
  • PyAV
  • PyAV
  • Merge requests
  • !790

codec/context: Defer ticks_per_frame-calculation

  • Review changes

  • Download
  • Email patches
  • Plain diff
Closed Ulrik Mikaelsson requested to merge github/fork/rawler/deferred_ticks_per_second into main May 27, 2021
  • Overview 1
  • Commits 2
  • Pipelines 0
  • Changes 3

Current hard-coded 1 ticks_per_frame assumes that framerate = 1/time_base. This is most often fine, except when re-encoding a source with frames in non-fps intervals. Explicitly setting higher time base works out OK for some codecs (libx264), but not with libvpx, which uses ticks_per_frame and time_base to measure time for rate-control. The net effect is that encoding with high-precision frame-timing for VP8 and VP9 does not work in PyAV.

Assignee
Assign to
Reviewers
Request review from
Time tracking
Source branch: github/fork/rawler/deferred_ticks_per_second