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 972
    • Issues 972
    • List
    • Boards
    • Service Desk
    • Milestones
  • Merge requests 105
    • Merge requests 105
  • 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
  • #330
Closed
Open
Issue created Nov 25, 2015 by Bugzilla Migration User@bugzilla-migration

h264parse: failed to encode MVC h264 streams in GStreamer-1.6

Submitted by Sreerenj Balachandran @sree

Link to original bug (#758656)

Description

MVC encoding is failing when adding a videoparser element in the pipeline.
Seems to be a regression with recent MVC specific patches landed in upstream h264parser (>= 1.5).

Encode(run with out any error):
GST_DEBUG=3 gst-launch-1.0 videotestsrc num-buffers=900 ! vaapiencode_h264 num-views=2 ! h264parse ! filesink location=enc_mvc.h264

Decoding will fail:
GST_DEBUG=3 gst-launch-1.0 filesrc location= enc_mvc.h264 ! h264parse ! "video/x-h264, stream-format=(string)byte-stream" ! vaapidecode ! vaapisink

Blocking

  • Bug 758397
Assignee
Assign to
Time tracking