https://bugs.freedesktop.org/show_bug.cgi?id=98005
--- Comment #13 from Boyuan Zhang <boyuan.zhang at amd.com> --- (In reply to Andy Furniss from comment #11) > 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. Hi Andy, Please take a look at the new patch set I just submitted: 1. https://lists.freedesktop.org/archives/mesa-dev/2016-November/135815.html 2. https://lists.freedesktop.org/archives/mesa-dev/2016-November/135813.html With these 2 patches, the vbr dual instance bit-rate issue should be solved. Please give a try. If you still see bit-rate failure, please send me the command which can reproduce the issue. In the meantime, I will look at the ntsc framerate. Thanks -- You are receiving this mail because: You are the assignee for the bug. -------------- next part -------------- An HTML attachment was scrubbed... URL: <https://lists.freedesktop.org/archives/dri-devel/attachments/20161118/2d46c50c/attachment.html>
