Skip to content
GitLab
Projects Groups Snippets
  • /
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in / Register
  • gst-plugins-bad gst-plugins-bad
  • Project information
    • Project information
    • Activity
    • Labels
    • Members
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
  • Issues 973
    • Issues 973
    • List
    • Boards
    • Service Desk
    • Milestones
  • Merge requests 104
    • Merge requests 104
  • 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-plugins-badgst-plugins-bad
  • Issues
  • #1177
Closed
Open
Issue created Jan 14, 2020 by Niels De Graef@nielsdg😁Reporter

nvenc plugin initialization should be optional

Use case: we're running a video decoder which needs to "instantly" start up to 16 video decoding pipelines (with NVIDIA HW-acceleration) at once.

Problem: We're seeing quite a delay (10 seconds and more) to start up all players. One issue we found was the nvdec plugin creating a large amount of CUDA contexts (#1130 (closed)), which got solved and got the delay closer to ≅ 5 seconds. However, this is still quite a lot.

Upon closer investigation, we found that nvenc is also loading its own CUDA contexts (to know which caps it supports). Given the fact that we don't really need HW-accelerating encoding, we need a way to either disable the nvenc plugin, or to somehow avoid loading the contexts.

Assignee
Assign to
Time tracking