GNOME Bugzilla – Bug 788262
vaapisink only shows the first frame of VP8/VP9 streams.
Last modified: 2018-05-04 16:18:08 UTC
Only the first frame display on my screen for VP8/VP9 streams encoded by libyami. cmdline: : gst-launch-1.0 filesrc location=720P_tractor_1280x720_5520frames.yuv_cqp_qp120_ip.vp8 ! ivfparse ! vaapivp8dec ! vaapisink gst-launch-1.0 filesrc location=4K_tractor_3840x2160_1000frames.yuv_cbr_bt12000_ip.vp9 ! ivfparse ! vaapivp9dec ! vaapisink streams can be found by link: https://drive.google.com/open?id=0B-M3YNi0HORQd0xhMVQwaVVzZXc
(In reply to Fei from comment #0) > Only the first frame display on my screen for VP8/VP9 streams encoded by > libyami. > > cmdline: : gst-launch-1.0 filesrc > location=720P_tractor_1280x720_5520frames.yuv_cqp_qp120_ip.vp8 ! ivfparse ! > vaapivp8dec ! vaapisink > > gst-launch-1.0 filesrc > location=4K_tractor_3840x2160_1000frames.yuv_cbr_bt12000_ip.vp9 ! ivfparse ! > vaapivp9dec ! vaapisink > > streams can be found by link: > https://drive.google.com/open?id=0B-M3YNi0HORQd0xhMVQwaVVzZXc I found it drops all frames after the first frame because of invalid timestamp. And it seems to be same on every player: gst-play, ffplay, vlc. But mpv plays it, but not quite good and outputs tons of warnings about timestamp. Could you confirm the media you shared?
@guangxin, could you help to check why yamiencode gives VP8/VP9 encoded streams invalid timestamp?
The output is ivf file. yami did not write timestamp to it. @Fei, you can file bug for yami
@guangxin, bug filed: https://github.com/01org/libyami/issues/800
Closing this as invalid. If we can probe is a problem in gstreamer-vaapi please reopen.