Comment # 5
on bug 102203
from Andy Furniss
VCE does seen to have suffered some regressions recently - I stopped testing it in March due to one in mesa that broke my normal testing. It's possible that gstreamer regressed and the mesa commit just exposed its deficiencies. Whatever the reason there are more issues now and I don't know what caused them or when they started due to ignoring VCE for so long. ffmpeg was OK last time I tried - but it clearly isn't for you. On the 4K speed - even when everything was working perfectly ffmpeg always was half the speed of gstreamer for me. I could in a very artificial test get 4K60p encode with gstreamer (pre-prepared raw nv12 video in ram). Getting that speed in other circumstances gets tricky as CPU bottlenecks get involved for things like making the nv12 from other formats to feed the encoder.
You are receiving this mail because:
- You are the assignee for the bug.
_______________________________________________ dri-devel mailing list dri-devel@xxxxxxxxxxxxxxxxxxxxx https://lists.freedesktop.org/mailman/listinfo/dri-devel
