Skip to content
GitLab
Projects Groups Snippets
  • /
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Register
  • Sign in
  • A aom-rav1e
  • Project information
    • Project information
    • Activity
    • Labels
    • Members
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
  • Issues 0
    • Issues 0
    • List
    • Boards
    • Service Desk
    • Milestones
  • Merge requests 0
    • Merge requests 0
  • CI/CD
    • CI/CD
    • Pipelines
    • Jobs
    • Schedules
  • Deployments
    • Deployments
    • Environments
    • Releases
  • Packages and registries
    • Packages and registries
    • Container 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
  • Guillaume Martres
  • aom-rav1e
  • Repository
Switch branch/tag
  • aom-rav1e
  • vpxenc.c
Find file BlameHistoryPermalink
  • Ralph Giles's avatar
    Have vpxenc use a default kf_max_rate of 5 seconds. · 061a16d9
    Ralph Giles authored Jan 05, 2012
    Rather than using the static default maximum keyframe spacing
    provided by vpx_codec_enc_config_default() set the default
    value to 5 times the frame rate. Five seconds is too long for
    live streaming applications, but is a compromise between seek
    efficiency and giving the encoder freedom to choose keyframe
    locations.
    
    The five second value is from James Zern's suggestion in
    http://article.gmane.org/gmane.comp.multimedia.webm.user/2945
    
    Change-Id: Ib7274dc248589c433c06e68ca07232e97f7ce17f
    061a16d9