omxvideoenc: Failed to force a keyframe: Unsupported index (0x8000101a)

[Graham Leggett]

On 15 Aug 2015, at 1:56 PM, Graham Leggett <minfrin at sharp.fm> wrote:

> Using the patch below to improve the error message, I am now getting the following:
> 
> 0:03:01.909221579 10369  0x1a526f0 ERROR            omxvideoenc gstomxvideoenc.c:1553:gst_omx_video_enc_handle_frame:<omxh264enc-omxh264enc0> Failed to force a keyframe at index 200: Unsupported index (0x8000101a)
> 
> Does anyone know what units an “index” is measured in? Is it a frame number, seconds, something else?
> 
> Is “200” a reasonable index?
> 
> Patching further to print an error if the attempt to force a keyframe ever succeeds shows that this call never succeeds. Is this API documented anywhere?

It gets weirder.

Trying to change the code to query the OMX_IndexConfigVideoIntraVOPRefresh value before setting it, I get the exact same "Unsupported index” error on the get that I do on the set:

      GST_DEBUG_OBJECT (self, "Forcing a keyframe");
      err =
          gst_omx_component_get_config (self->enc,
          OMX_IndexConfigVideoIntraVOPRefresh, &config);
      if (err != OMX_ErrorNone) {
        GST_ERROR_OBJECT (self, "Failed to force a keyframe at index %d (Could not get config): %s (0x%08x)",
            (int)port->index, gst_omx_error_to_string (err), err);
      }

0:00:21.667666054 11184   0x2f02f0 ERROR            omxvideoenc gstomxvideoenc.c:1553:gst_omx_video_enc_handle_frame:<omxh264enc-omxh264enc0> Failed to force a keyframe at index 200 (Could not get config): Unsupported index (0x8000101a)

Does the gst_omx_component_get_config() have some kind of requirement on the initialisation of the config structure? Why would the get_config fail, this seems really weird?

Regards,
Graham
—