After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.
Bug 751831 - encode: h264: CBR encoded streams are unplayable with vaapidecode
encode: h264: CBR encoded streams are unplayable with vaapidecode
Status: RESOLVED FIXED
Product: gstreamer-vaapi
Classification: Other
Component: general
git master
Other Linux
: Normal blocker
: ---
Assigned To: gstreamer-vaapi maintainer(s)
gstreamer-vaapi maintainer(s)
Depends on: 722734
Blocks: 743569
 
 
Reported: 2015-07-02 11:26 UTC by sreerenj
Modified: 2015-07-02 19:10 UTC
See Also:
GNOME target: ---
GNOME version: ---


Description sreerenj 2015-07-02 11:26:45 UTC 
Failing to playback the stream encoded with vaapiencode_h264.

How to reproduce the issue:
gst-launch-1.0 -v  videotestsrc num-buffers=300 ! vaapiencode_h264 rate-control=cbr  bitrate=10000 ! filesink location=sample.264

Try to playback the stream with gst-play:
gst-play-1.0 sample.264

Stream is playable with avplay but lots of SEI header truncated errors.
Comment 1 sreerenj 2015-07-02 14:31:25 UTC 
As per Initial investigation, the issue is because of SEI headers inserted by the driver itself.

It is better to insert SEI headers from vaapiencoder_h264 itself:
patch is here:
 https://bugzilla.gnome.org/show_bug.cgi?id=722734
Comment 2 sreerenj 2015-07-02 19:10:41 UTC 
commit a2604261946e0716dd2708686454d3ad6262f938
Author: Sreerenj Balachandran <sreerenj.balachandran@intel.com>
Date:   Thu Jul 2 21:00:14 2015 +0300

    encoder: h264: submit SEI buffering_period() and picture_timing() messages for CBR mode