Skip to content
GitLab
Projects Groups Snippets
  • /
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in / Register
  • gst-plugins-base gst-plugins-base
  • Project information
    • Project information
    • Activity
    • Labels
    • Members
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
  • Issues 642
    • Issues 642
    • List
    • Boards
    • Service Desk
    • Milestones
  • Merge requests 80
    • Merge requests 80
  • 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-basegst-plugins-base
  • Issues
  • #763
Closed
Open
Issue created Jun 02, 2020 by Mathieu Duponchelle@meh🐸Maintainer

videoconvert: disregards downstream preferences for the format

With such a pipeline:

src ! videoconvert ! glupload ! glcolorconvert ! filter_element_expecting_BGRA

Videoconvert gets to fixate these caps:

video/x-raw, format=BGRA; video/x-raw, format = {all, the, formats, glcolorconvert, supports}

When fixating however, videoconvert ignores the higher preference level expressed by having two separate structures in the caps, as it simply flattens all the pixel formats and picks one according to its scoring heuristic.

Ideally, videoconvert should consider each structure independently, unclear however whether this will break existing scenarios.

Assignee
Assign to
Time tracking