Commen=
t # 13
on bug 98005<=
/a>
from Boyuan Zhang
(In reply to Andy Furniss from comment #11)
> It turns out with more time + different tests th=
at these patches don't fix
> the original issue.
>=20
> 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) disa=
bling
> dual instance does seem to always produce the correct bitrate.
>=20
> I also found another bug =3D ntsc framerates are not handled. I live i=
n PAL
> land, so didn't notice this sooner, though we still get /1001 framerat=
es on
> blu-ray which is how I belatedly noticed.
>=20
> 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 w=
hat
> you think (it only applies to vanilla mesa). Seems to work OK with avc=
onv
> 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