All of lore.kernel.org
 help / color / mirror / Atom feed
From: bugzilla-daemon@freedesktop.org
To: dri-devel@lists.freedesktop.org
Subject: [Bug 98005] VCE dual instance encoding inconsistent since st/va: enable dual instances encode by sync surface
Date: Sun, 13 Nov 2016 00:03:24 +0000	[thread overview]
Message-ID: <bug-98005-502-C1Q8e6WAnT@http.bugs.freedesktop.org/> (raw)
In-Reply-To: <bug-98005-502@http.bugs.freedesktop.org/>


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

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

--- Comment #11 from Andy Furniss <adf.lists@gmail.com> ---
It turns out with more time + different tests that these patches don't fix the
original issue.

I can still get too low bitrates depending on timing/luck eg. forcing
powerplay/cpufreq to high with the right test stream can get different results
from auto. This is testing with the same GOP and (so far) disabling dual
instance does seem to always produce the correct bitrate.

I also found another bug = ntsc framerates are not handled. I live in PAL land,
so didn't notice this sooner, though we still get /1001 framerates on blu-ray
which is how I belatedly noticed.

I made a hacky fix - maybe working out where (if anywhere) the players pass
framerate den would be better, but I'll attach it anyway just to see what you
think (it only applies to vanilla mesa). Seems to work OK with avconv and
gstreamer.

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

[-- Attachment #1.2: Type: text/html, Size: 1916 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:[~2016-11-13  0:03 UTC|newest]

Thread overview: 41+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-10-01 15:06 [Bug 98005] VCE dual instance encoding inconsistent since st/va: enable dual instances encode by sync surface bugzilla-daemon
2016-10-03 22:16 ` bugzilla-daemon
2016-10-17 20:20 ` bugzilla-daemon
2016-10-17 23:59 ` bugzilla-daemon
2016-10-18 17:58 ` bugzilla-daemon
2016-10-18 20:25 ` bugzilla-daemon
2016-11-10 22:57 ` bugzilla-daemon
2016-11-10 23:35 ` bugzilla-daemon
2016-11-11 16:31 ` bugzilla-daemon
2016-11-11 21:40 ` bugzilla-daemon
2016-11-11 21:51 ` bugzilla-daemon
2016-11-13  0:03 ` bugzilla-daemon [this message]
2016-11-13  0:04 ` bugzilla-daemon
2016-11-18 21:17 ` bugzilla-daemon
2016-11-19  0:37 ` bugzilla-daemon
2016-11-20 14:01 ` bugzilla-daemon
2016-11-20 14:03 ` bugzilla-daemon
2016-11-20 23:25 ` bugzilla-daemon
2016-11-21 19:54 ` bugzilla-daemon
2016-11-21 22:01 ` bugzilla-daemon
2016-11-21 22:51 ` bugzilla-daemon
2016-11-22  0:29 ` bugzilla-daemon
2016-11-22  0:51 ` bugzilla-daemon
2016-11-22  1:03 ` bugzilla-daemon
2016-11-24 19:53 ` bugzilla-daemon
2016-11-24 22:04 ` bugzilla-daemon
2016-11-25  0:53 ` bugzilla-daemon
2016-11-25 21:15 ` bugzilla-daemon
2016-11-26 19:45 ` bugzilla-daemon
2016-11-26 21:59 ` bugzilla-daemon
2016-11-26 23:23 ` bugzilla-daemon
2016-11-27  0:53 ` bugzilla-daemon
2016-11-28 22:34 ` bugzilla-daemon
2016-11-28 23:47 ` bugzilla-daemon
2016-11-29 20:02 ` bugzilla-daemon
2016-11-30 19:35 ` bugzilla-daemon
2016-11-30 20:53 ` bugzilla-daemon
2016-12-06  0:25 ` bugzilla-daemon
2016-12-06 15:23 ` bugzilla-daemon
2016-12-08 11:54 ` bugzilla-daemon
2019-09-25 17:55 ` 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-98005-502-C1Q8e6WAnT@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.