dri-devel Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: bugzilla-daemon@freedesktop.org
To: dri-devel@lists.freedesktop.org
Subject: [Bug 99029] VCE VAAPI segfault using ffmpeg
Date: Tue, 09 May 2017 15:40:56 +0000	[thread overview]
Message-ID: <bug-99029-502-pZuOnRy62N@http.bugs.freedesktop.org/> (raw)
In-Reply-To: <bug-99029-502@http.bugs.freedesktop.org/>


[-- Attachment #1.1: Type: text/plain, Size: 1494 bytes --]

https://bugs.freedesktop.org/show_bug.cgi?id=99029

--- Comment #3 from Andy Furniss <adf.lists@gmail.com> ---
Hmm, I haven't tested yet, but if you hit the division by zero, I guess there
is something special about thet file (or ffmpeg/something changed since I last
looked). Before reading your other bug the only way I thought would trigger
that one was to explicitly add -g 0 to the command line.

On speed - I would get rid of the yuv420p, maybe add -g 48 as for some reason
things don't seem quite right with the gop, or you shouldn't hit the division
by zero.

Your fix seems to change the intent of that code a little bit - I don't know if
it makes any difference. That code got added to correct some corner case rate
control cbr issue - ffmpeg switched to using vbr by default so may not show it
anyway. I don't recall what rate (maybe it's cqp) you'll get if you don't ask
for anything like your example. There may be a better place to check if gop is
0.

-profile:v 77 doesn't quite work properly IIRC (well it doesn't change anything
encoding wise but the file will not show as main).

You may get more perf if you force your GPU to high.

I guess this is just a test, but for real world use, using your h/w to
transcode without b-frames is not really an optimum solution and it's up to the
firmware team whether b-frames ever work (They don't work on windows either
AFAICT).

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

[-- Attachment #1.2: Type: text/html, Size: 2239 bytes --]

[-- Attachment #2: Type: text/plain, Size: 160 bytes --]

_______________________________________________
dri-devel mailing list
dri-devel@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/dri-devel

  parent reply	other threads:[~2017-05-09 15:40 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-12-08 14:37 [Bug 99029] VCE VAAPI segfault using ffmpeg bugzilla-daemon
2016-12-08 14:41 ` bugzilla-daemon
2016-12-08 14:54 ` bugzilla-daemon
2017-05-09 14:15 ` bugzilla-daemon
2017-05-09 15:40 ` bugzilla-daemon [this message]
2017-05-11 13:40 ` bugzilla-daemon
2017-05-11 14:03 ` bugzilla-daemon
2017-05-11 16:32 ` bugzilla-daemon
2019-09-18 19:22 ` bugzilla-daemon

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=bug-99029-502-pZuOnRy62N@http.bugs.freedesktop.org/ \
    --to=bugzilla-daemon@freedesktop.org \
    --cc=dri-devel@lists.freedesktop.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox