omxvideoenc: Failed to force a keyframe: Unsupported index (0x8000101a)
Sebastian Dröge
sebastian at centricular.com
Sat Aug 15 09:28:56 PDT 2015
On Sa, 2015-08-15 at 13:56 +0200, Graham Leggett wrote:
> On 15 Aug 2015, at 1:04 PM, Sebastian Dröge <
> sebastian at centricular.com> wrote:
>
> > It means that the RPi OpenMAX implementation does not support
> > forcing a
> > keyframe to be generated with that API, or we use that API wrong.
>
> 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?
That's the index of the port as defined by the RPi openmax component.
It's how the port is identified.
> 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?
Yes, it's documented in the OpenMAX IL specification.
https://www.khronos.org/registry/omxil/specs/OpenMAX_IL_1_1_2_Specifica
tion.pdf
--
Sebastian Dröge, Centricular Ltd · http://www.centricular.com
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 949 bytes
Desc: This is a digitally signed message part
URL: <http://lists.freedesktop.org/archives/gstreamer-devel/attachments/20150815/219a7ea4/attachment.sig>
More information about the gstreamer-devel
mailing list