On 23/04/2025 15:12, Dawid Kozinski wrote: > - Added constants definitions for APV parser > - Provided parsing following APV RFC > - APV parser registration > > Signed-off-by: Dawid Kozinski <d.kozin...@samsung.com> > --- > configure | 2 + > libavcodec/Makefile | 2 + > libavcodec/apv.h | 93 ++++++++ > libavcodec/apv_parse.c | 32 +++ > libavcodec/apv_parse.h | 81 +++++++ > libavcodec/apv_parser.c | 141 +++++++++++ > libavcodec/apv_ps.c | 503 ++++++++++++++++++++++++++++++++++++++++ > libavcodec/apv_ps.h | 188 +++++++++++++++ > libavcodec/parsers.c | 1 + > 9 files changed, 1043 insertions(+) > create mode 100644 libavcodec/apv.h > create mode 100644 libavcodec/apv_parse.c > create mode 100644 libavcodec/apv_parse.h > create mode 100644 libavcodec/apv_parser.c > create mode 100644 libavcodec/apv_ps.c > create mode 100644 libavcodec/apv_ps.h
Hi, Can you explain what the use-case for this parser is? Access units are always encapsulated with a known size, so I'm not understanding what this is used for. Thanks, - Mark _______________________________________________ ffmpeg-devel mailing list ffmpeg-devel@ffmpeg.org https://ffmpeg.org/mailman/listinfo/ffmpeg-devel To unsubscribe, visit link above, or email ffmpeg-devel-requ...@ffmpeg.org with subject "unsubscribe".
