From mboxrd@z Thu Jan 1 00:00:00 1970 From: bugzilla-daemon@freedesktop.org Subject: [Bug 98005] VCE dual instance encoding inconsistent since st/va: enable dual instances encode by sync surface Date: Tue, 22 Nov 2016 00:29:33 +0000 Message-ID: References: Mime-Version: 1.0 Content-Type: multipart/mixed; boundary="===============1243752710==" Return-path: Received: from culpepper.freedesktop.org (culpepper.freedesktop.org [131.252.210.165]) by gabe.freedesktop.org (Postfix) with ESMTP id 93BA06E631 for ; Tue, 22 Nov 2016 00:29:33 +0000 (UTC) In-Reply-To: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: dri-devel-bounces@lists.freedesktop.org Sender: "dri-devel" To: dri-devel@lists.freedesktop.org List-Id: dri-devel@lists.freedesktop.org --===============1243752710== Content-Type: multipart/alternative; boundary="14797745730.fFC50C5f.8527"; charset="UTF-8" --14797745730.fFC50C5f.8527 Date: Tue, 22 Nov 2016 00:29:33 +0000 MIME-Version: 1.0 Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable X-Bugzilla-URL: http://bugs.freedesktop.org/ Auto-Submitted: auto-generated https://bugs.freedesktop.org/show_bug.cgi?id=3D98005 --- Comment #21 from Andy Furniss --- Still the same issue with latest patches. I can sometimes get vbr to be affected as well. I made a smaller test file, it's re-coded with software to 24 fps as the re= al master is /1001 and so would be wrong without an additional patch anyway. I am just doing repeated decode/encode from/to ram and changing cpu/gpu settings to get unlucky timing - I guess on a different box you could luck = out of seeing it, just initial testing with raw video input from ram seemed to = work for me. This transcode seems to be mostly wrong with my cpu on perf and gpu on auto. for x in $(seq 1 20); do gst-launch-1.0 -f filesrc location=3D/mnt/ramdisk/in-24fps.mp4 ! qtdemux ! vaapidecode ! queue ! vaapih264enc rate-control=3Dcbr bitrate=3D5000 ! video/x-h264,profile=3Dbas= eline ! filesink location=3D/mnt/ramdisk/cbr-$x.264; done in-24fps.mp4 - https://drive.google.com/file/d/0BxP5-S1t9VEEaWNkZXdmb01GYmM/view?usp=3Dsha= ring --=20 You are receiving this mail because: You are the assignee for the bug.= --14797745730.fFC50C5f.8527 Date: Tue, 22 Nov 2016 00:29:33 +0000 MIME-Version: 1.0 Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable X-Bugzilla-URL: http://bugs.freedesktop.org/ Auto-Submitted: auto-generated

Commen= t # 21 on bug 98005<= /a> from Andy Furniss 
Still the same issue with latest patches. I can sometimes get =
vbr to be
affected as well.

I made a smaller test file, it's re-coded with software to 24 fps as the re=
al
master is /1001 and so would be wrong without an additional patch anyway.

I am just doing repeated decode/encode from/to ram and changing cpu/gpu
settings to get unlucky timing - I guess on a different box you could luck =
out
of seeing it, just initial testing with raw video input from ram seemed to =
work
for me.

This transcode seems to be mostly wrong with my cpu on perf and gpu on auto.

for x in $(seq 1 20); do gst-launch-1.0 -f filesrc
location=3D/mnt/ramdisk/in-24fps.mp4 ! qtdemux ! vaapidecode ! queue !
vaapih264enc rate-control=3Dcbr bitrate=3D5000 ! video/x-h264,profile=3Dbas=
eline !
filesink location=3D/mnt/ramdisk/cbr-$x.264; done

in-24fps.mp4 -
https://drive.google.com/file/d/0BxP5-S1t9VEEaWNkZXdmb01GY=
mM/view?usp=3Dsharing

You are receiving this mail because:
  • You are the assignee for the bug.
= --14797745730.fFC50C5f.8527-- --===============1243752710== Content-Type: text/plain; charset="utf-8" MIME-Version: 1.0 Content-Transfer-Encoding: base64 Content-Disposition: inline X19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX18KZHJpLWRldmVs IG1haWxpbmcgbGlzdApkcmktZGV2ZWxAbGlzdHMuZnJlZWRlc2t0b3Aub3JnCmh0dHBzOi8vbGlz dHMuZnJlZWRlc2t0b3Aub3JnL21haWxtYW4vbGlzdGluZm8vZHJpLWRldmVsCg== --===============1243752710==--