Skip to content
GitLab
Projects Groups Topics Snippets
  • /
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Register
  • Sign in
  • gst-plugins-base gst-plugins-base
  • Project information
    • Project information
    • Activity
    • Labels
    • Members
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributor statistics
    • Graph
    • Compare revisions
  • Issues 637
    • Issues 637
    • List
    • Boards
    • Service Desk
    • Milestones
  • Merge requests 69
    • Merge requests 69
  • 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
  • #382
Closed
Open
Issue created Sep 21, 2017 by Bugzilla Migration User@bugzilla-migration

playbin: read the initial state of internal color balance interface

Submitted by Ung, Teng En

Link to original bug (#787973)

Description

In linux with gstreamer 1.8.3, when try using playbin and assign the color balance with video-sink. The value got reset to other value.

Run the test with gstreamer vaapi, when we don't use playbin the color balance value will apply :-
gst-launch-1.0 filesrc location=<Video> ! qtdemux ! queue ! h264parse ! vaapidecode ! queue ! vaapisink hue=180

But when use playbin and change the video-sink to include color balance value; it will be reset to default :-
gst-launch-1.0 playbin2 uri=<Video> video-sink="vaapisink hue=180"

Version: 1.12.3

Assignee
Assign to
Time tracking