GNOME Bugzilla – Bug 794799
pi: OMX encoder not reaching Executing when setting target-bitrate
Last modified: 2018-11-03 13:01:57 UTC
Trying this pipeline with gst master: gst-launch-1.0 videotestsrc ! omxh264enc target-bitrate=500000 control-rate=2 ! video/x-h264, profile="high" ! fakesink The pipeline hangs waiting for the OMX component to reach the Executing state. 0:00:00.136477641 929 0x10cb860 INFO omx gstomx.c:902:gst_omx_component_set_state:<omxh264enc-omxh264enc0> Setting video_encode state from Idle to Executing 0:00:00.137169622 929 0x10cb860 DEBUG omx gstomx.c:960:gst_omx_component_get_state:<omxh264enc-omxh264enc0> Getting state of video_encode 0:00:00.137202904 929 0x10cb860 DEBUG omx gstomx.c:460:gst_omx_component_wait_message:<omxh264enc-omxh264enc0> video_encode waiting for signal
+ Trace 238523
Thread 8 (Thread 0x733a1470 (LWP 936))
This used to work at some point as these encoder settings were used to test bug #698049 I tried reverting the omxvideoenc code to 5ba55b6c9aad49858304a38e0ab475c1ecafd646 (the commit fixing bug #698049) but hit the same problem. So this may be a change/bug in the OMX implementation.
-- GitLab Migration Automatic Message -- This bug has been migrated to freedesktop.org's GitLab instance and has been closed from further activity. You can subscribe and participate further through the new bug through this link to our GitLab instance: https://gitlab.freedesktop.org/gstreamer/gst-omx/issues/21.