[Bug 768122] [gstreamer-vaapi-master][h264] run2run is not bit match in h264 encoder

[GStreamer (GNOME Bugzilla)]

https://bugzilla.gnome.org/show_bug.cgi?id=768122

sreerenj <bsreerenj at gmail.com> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|NEW                         |NEEDINFO
           Severity|critical                    |normal

--- Comment #1 from sreerenj <bsreerenj at gmail.com> ---
(In reply to Jun Zhao from comment #0)
> This is the reproduce step for this issue.
> 
> DISPLAY=:0 gst-launch-1.0 filesrc location=~/bits/320x240.264 ! h264parse !
> vaapidecode ! vaapiencode_h264 ! filesink location=a.264
> 
> DISPLAY=:0 gst-launch-1.0 filesrc location=~/bits/320x240.264 ! h264parse !
> vaapidecode ! vaapiencode_h264 ! filesink location=b.264
> 
> diff a.264 b.264, sometimes a.264 and b.264 is not same.
> 
> CPU: BSW
> OS : Ubuntu 14.04
> An used inter-driver/libva master branch.

I am not sure whether the output of encoders are deterministic all the time.

In case of a decoding scenario, Output of decoded frames should be bit exact
similar for any decoder implementations , at any time.

But for encoders, this is not the case. For eg: If you run the x264encoder on
same input multiple times, the output encoded stream won't have similar md5 all
the time (explicitly making thread count to one may give the same output
though).


Are you getting the bit exact match when encoding with x264enc?

gst-launch-1.0 filesrc location= sample_i420_320_240_30.yuv ! videoparse
format=i420 width=320 height=240 framerate=30 !   x264enc !  filesink
location=out1.264

md5sum out*

-- 
You are receiving this mail because:
You are the QA Contact for the bug.
You are the assignee for the bug.