L4T 32.1, V4L vs OpenMAX video encoding

Autonomous Machines Jetson & Embedded Systems Jetson TX2
1

Hi,

as far as I understood with L4T release 32.1 NVIDIA has deprecated OpenMAX API for video encoding. V4L API seems to be the main supported option now. But there’s a missing feature compared to OpenMAX - V4L lacks support for 10 bit H.265 encoding. Are there any plans to add it?

Also I wonder what does new V4L2_CID_MPEG_VIDEOENC_ENABLE_ALLIFRAME_ENCODE option do? Does it make every frame an I-frame?

2

Hi,
On r32.1, please use omxh265enc for 10 bit encoding.

Deprecation may take one or two releases. We will have it in nvv4l2h265enc before we completely deprecate omxh265enc.

3

Yes. Please check the option ‘–alliframes’ in 01_video_encode sample.

4

Hi,

thank you for your answers. Could you also explain what does V4L2_CID_MPEG_VIDEOENC_EXTEDED_COLORFORMAT do? I understand it defines whether YUV input is full-range (0-255) or limited (16-235), but specifically what effect does this option have? Does it just set the corresponding flag in VUI? Or does it affect encoding algorithm somehow?

Also, is it possible to control other options in VUI, like color space with transfer function (e.g. set it to BT.709)? Is such functionality planned, if not?

5

Hi,

This is true if you set V4L2_CID_MPEG_VIDEOENC_EXTEDED_COLORFORMAT