Skip to content
GitLab
Projects Groups Snippets
  • /
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in / Register
  • gstreamer-vaapi gstreamer-vaapi
  • Project information
    • Project information
    • Activity
    • Labels
    • Members
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
  • Issues 147
    • Issues 147
    • List
    • Boards
    • Service Desk
    • Milestones
  • Merge requests 8
    • Merge requests 8
  • 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
  • gstreamer-vaapigstreamer-vaapi
  • Issues
  • #167
Closed
Open
Issue created May 30, 2019 by Víctor Manuel Jáquez Leal@vjaquezMaintainer

vaapiencode: Rethink when to start, stop and pause the src pad task

Right now the start/stop/pause of the src pad's task is a bit convoluted and leads to hacks like !95 (merged) (it is a hack in the sense it doesn't follow the GstVideoEncode API logic).

My idea is try to mimic the v4l2 encoder strategy.

Assignee
Assign to
Time tracking