Go to the documentation of this file.
19 #ifndef AVCODEC_H2645_SEI_H
20 #define AVCODEC_H2645_SEI_H
175 unsigned bit_depth_luma,
unsigned bit_depth_chroma,
AVFilmGrainAFGS1Params aom_film_grain
SEIFpaType arrangement_type
uint16_t max_pic_average_light_level
uint16_t display_primaries[3][2]
This structure describes decoded (raw) audio or video data.
int preferred_transfer_characteristics
@ FF_H2645_SEI_MESSAGE_HANDLED
H2645SEIA53Caption a53_caption
HEVCSEIDynamicHDRVivid dynamic_hdr_vivid
uint8_t intensity_interval_upper_bound[3][256]
int ff_h2645_sei_message_decode(H2645SEI *h, enum SEIType type, enum AVCodecID codec_id, GetBitContext *gb, GetByteContext *gbyte, void *logctx)
Decode a single SEI message.
it s the only field you need to keep assuming you have a context There is some magic you don t need to care about around this just let it vf type
H2645SEIAmbientViewingEnvironment ambient_viewing_environment
uint8_t intensity_interval_lower_bound[3][256]
int current_frame_is_frame0_flag
int arrangement_cancel_flag
is previous arrangement canceled, -1 if never received (currently H.264 only)
int anticlockwise_rotation
void ff_h2645_sei_reset(H2645SEI *s)
uint16_t max_content_light_level
int comp_model_present_flag[3]
uint16_t num_intensity_intervals[3]
static int FUNC() sei(CodedBitstreamContext *ctx, RWContext *rw, H264RawSEI *current)
H2645SEIDisplayOrientation display_orientation
AVCodecID
Identify the syntax and semantics of the bitstream.
uint8_t num_model_values[3]
H2645SEIFramePacking frame_packing
uint8_t ptrdiff_t const uint8_t ptrdiff_t int intptr_t intptr_t int int16_t * dst
int arrangement_repetition_period
H2645SEIMasteringDisplay mastering_display
@ FF_H2645_SEI_MESSAGE_UNHANDLED
int transfer_characteristics
H2645SEIContentLight content_light
int ff_h2645_sei_to_context(AVCodecContext *avctx, H2645SEI *sei)
int separate_colour_description_present_flag
these buffered frames must be flushed immediately if a new input produces new the filter must not call request_frame to get more It must just process the frame or queue it The task of requesting more frames is left to the filter s request_frame method or the application If a filter has several the filter must be ready for frames arriving randomly on any input any filter with several inputs will most likely require some kind of queuing mechanism It is perfectly acceptable to have a limited queue and to drop frames when the inputs are too unbalanced request_frame For filters that do not use the this method is called when a frame is wanted on an output For a it should directly call filter_frame on the corresponding output For a if there are queued frames already one of these frames should be pushed If the filter should request a frame on one of its repeatedly until at least one frame has been pushed Return or at least make progress towards producing a frame
int content_interpretation_type
SEIFpaType
frame_packing_arrangement types.
H2645SEIUnregistered unregistered
main external API structure.
int ff_h2645_sei_ctx_replace(H2645SEI *dst, const H2645SEI *src)
uint32_t ambient_illuminance
int quincunx_sampling_flag
A reference to a data buffer.
HEVCSEIDynamicHDRPlus dynamic_hdr_plus
int ff_h2645_sei_to_frame(AVFrame *frame, H2645SEI *sei, enum AVCodecID codec_id, AVCodecContext *avctx, const H2645VUI *vui, unsigned bit_depth_luma, unsigned bit_depth_chroma, int seed)
int16_t comp_model_value[3][256][6]
H2645SEIAlternativeTransfer alternative_transfer
H2645SEIFilmGrainCharacteristics * film_grain_characteristics
uint8_t active_format_description