hi_mpi_venc_request_idr
Applicability
Product |
Supported |
|---|---|
☓ |
|
☓ |
|
√ |
|
√ |
|
☓ |
Description
Requests for an instantaneous decoding refresh (IDR) frame.
Prototype
hi_s32 hi_mpi_venc_request_idr (hi_venc_chn chn, hi_bool instant)
Parameters
Parameter |
Input/Output |
Description |
|---|---|---|
chn |
Input |
Encoding channel ID. |
instant |
Input |
Whether to instantly encode an IDR frame. |
Returns
- 0: success
- Other values: failure. For details, see VENC/JPEGE Return Codes.
Restrictions
- Ensure that a channel has been created. Otherwise, a failure is returned.
- After an IDR frame request is received, if instant is set to 0, an IDR frame is encoded in the next frame as controlled by the frame rate controller; if instant is set to 1, an IDR frame is encoded instantly.
- IDR frame requesting is applicable to H.264 and H.265 encoding.
- Typically, the destination frame rate is the same as the source frame rate. Therefore, the frame rate controller has no impact on this API. Regardless of the setting of instant (either 0 or 1), an IDR frame is encoded on every call to this API. Note that frequent calls to this API cause fluctuations in the frame rate and bit rate of the stream.
- When the GOP mode is OT_VENC_GOP_MODE_SMART_P or B-frame mode, the request for the IDR frame takes effect after a delay.
Currently, the
Atlas inference products do not support OT_VENC_GOP_MODE_SMART_P or B-frame mode.Currently, the
Atlas 200I/500 A2 inference products does not support B-frame mode.