Skip to content
GitLab
Projects Groups Snippets
  • /
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in / Register
  • gst-libav gst-libav
  • Project information
    • Project information
    • Activity
    • Labels
    • Members
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
  • Issues 69
    • Issues 69
    • List
    • Boards
    • Service Desk
    • Milestones
  • Merge requests 3
    • Merge requests 3
  • 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
  • Snippets
    • Snippets
  • Activity
  • Graph
  • Create a new issue
  • Jobs
  • Commits
  • Issue Boards
Collapse sidebar
  • GStreamerGStreamer
  • gst-libavgst-libav
  • Issues
  • #73
Closed
Open
Issue created May 21, 2020 by Edward Hervey@bilboed🤘Owner

Saner defaults for avvidec threading

Since !34 (merged) was merged, the default threading models of decoders is a bit painful.

If upstream is not live, it defaults to:

  • up to 16 threads
  • frame and slice threading

What actually happens is that most of the time ffmpeg will end up picking only frame-based threading and backlog up to 15 frames before outputting anything, thereby introducing a massive latency.

Furthermore, we already have frame-based threading upstream and downstream of decoders.

What I propose is that we change the defaults to:

  • Maximum of 4 threads if max-threads is 0
  • Use slice-based threading (if available) if thread-type is 0 (auto)
Assignee
Assign to
Time tracking