Comment # 12
on bug 98278
from Christoph Haag
Thanks for your tips, quite some new information for me. I am using this pipeline now: gst-launch-1.0 -e ximagesrc display-name=:0 use-damage=0 startx=0 starty=0 endx=1919 endy=1079 ! multiqueue ! video/x-raw,format=BGRx,framerate=60/1 ! videoconvert ! video/x-raw,format=NV12,framerate=60/1 ! multiqueue ! vaapih264enc rate-control=cqp bitrate=5000 ! video/x-h264,profile="" ! h264parse ! multiqueue ! matroskamux name=muxer. ! progressreport name=Rec_time ! filesink location=output.mkv This one runs nicely and doesn't cause GPU hangs. Are we using this bug report to talk about omx too? This is my equivalent omx pipeline: gst-launch-1.0 -e ximagesrc display-name=:0 use-damage=0 startx=0 starty=0 endx=1919 endy=1079 ! multiqueue ! video/x-raw,format=BGRx,framerate=60/1 ! videoconvert ! video/x-raw,format=NV12,framerate=60/1 ! multiqueue ! omxh264enc control-rate=2 target-bitrate=11000000 ! h264parse ! multiqueue ! matroskamux name=muxer. ! progressreport name=Rec_time ! filesink location=output.mkv omxregister-bellagio produces a broken ~/.omxregister for me, but it really only needs to be a text file with two lines: /usr/lib/bellagio/libomxvideosched.so /usr/lib/bellagio/libomx_mesa.so Sometimes (?) the gst-omx plugin is blacklisted. Check with gst-inspect-1.0 | grep omx whether there is something. If not, delete ~/.cache/gstreamer-1.0/registry.x86_64.bin and try again. That's all I know about reasons omx may not be working. For the performance, there is a chance you're also affected by bug 97075. Try running vblank_mode=0 glxgears and then starting the encoding. Make sure it's really not throttled to 60 fps. Either it improves the performance of the hardware encoder a lot or it does nothing.
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
