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

[Sebastian Dröge]

On Sa, 2015-08-15 at 18:51 +0200, Graham Leggett wrote:
> On 15 Aug 2015, at 6:28 PM, Sebastian Dröge <
> sebastian at centricular.com> wrote:
> 
> > That's the index of the port as defined by the RPi openmax 
> > component.
> > It's how the port is identified.
> 
> What is the “port”?

See the OpenMAX IL spec.

> > Yes, it's documented in the OpenMAX IL specification.
> > https://www.khronos.org/registry/omxil/specs/OpenMAX_IL_1_1_2_Speci
> > fica
> > tion.pdf
> 
> According to the docs the nPortIndex value is read only, so the 
> existing code that tried to write directly to nPortIndex seems to be 
> incorrect.

The port being read-only means that we can't change the port number.
But we have to set a port number in various structs, so that OpenMAX IL
knows for which struct we are requesting or setting a value.

> What is confusing me through is that I’m getting 
> OMX_ErrorUnsupportedIndex from OMX_GetConfig() - given we’re getting 
> the index the only parameter of relevance is 
> “OMX_IndexConfigVideoIntraVOPRefresh”, and yet this is supposedly 
> supported?

It might just not be supported by the RPi OpenMAX IL implementation. No
OpenMAX IL implementations implements all the things that are mentioned
in the spec, and none of them even implements everything they implement
in a way that is conforming with the spec.


That said, this might also be a bug on our side. We currently set this
config on the port with index 200. Maybe it is only supported to be set
on the other port, 201 (IIRC).


-- 
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/20150816/65de4176/attachment.sig>