Skip to content

GitLab

  • Projects
  • Groups
  • Snippets
  • Help
    • Loading...
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in / Register
gst-plugins-bad
gst-plugins-bad
  • Project overview
    • Project overview
    • Details
    • Activity
    • Releases
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
  • Issues 1,012
    • Issues 1,012
    • List
    • Boards
    • Labels
    • Service Desk
    • Milestones
  • Merge Requests 199
    • Merge Requests 199
  • CI / CD
    • CI / CD
    • Pipelines
    • Jobs
    • Schedules
  • Operations
    • Operations
    • Incidents
    • Environments
  • Packages & Registries
    • Packages & Registries
    • Container Registry
  • Analytics
    • Analytics
    • CI / CD
    • Repository
    • Value Stream
  • Snippets
    • Snippets
  • Members
    • Members
  • Activity
  • Graph
  • Create a new issue
  • Jobs
  • Commits
  • Issue Boards
Collapse sidebar
  • GStreamer
  • gst-plugins-badgst-plugins-bad
  • Issues
  • #312

Closed
Open
Opened Oct 15, 2015 by Bugzilla Migration User@bugzilla-migration

nvenc: Use NVENC API-capable devices in a loop by default

Submitted by Kyrylo V. Polezhaiev

Link to original bug (#756635)

Description

Default device ID is now 0. In case we have several NVIDIA video cards, user should manually specify device ID for particular encoding element so he should dive into NVENC API level to find out the number of devices and ID of devices with NVENC support.

In pre-LGPLed version of gst-nvenc new nvh264enc elements just take next (or first, if current one is last) device in a bit ugly way.

Maybe we should set device ID to next (first) device by default?

Assignee
Assign to
None
Milestone
None
Assign milestone
Time tracking
None
Due date
None
Reference: gstreamer/gst-plugins-bad#312