From: Anton Khirnov <anton@khirnov.net> To: FFmpeg development discussions and patches <ffmpeg-devel@ffmpeg.org> Subject: Re: [FFmpeg-devel] [PATCH 04/11] avcodec/packet: add some documentation for AVPacketSideData Date: Wed, 04 Oct 2023 16:46:39 +0200 Message-ID: <169643079949.6638.10107251396186814606@lain.khirnov.net> (raw) In-Reply-To: <20231004122849.56604-5-jamrial@gmail.com> Quoting James Almer (2023-10-04 14:28:42) > Explaining what or who may use it, and in what scenarios. > > Signed-off-by: James Almer <jamrial@gmail.com> > --- > libavcodec/packet.h | 19 +++++++++++++++++++ > 1 file changed, 19 insertions(+) > > diff --git a/libavcodec/packet.h b/libavcodec/packet.h > index 96fc0084d6..85b3eeb728 100644 > --- a/libavcodec/packet.h > +++ b/libavcodec/packet.h > @@ -312,6 +312,25 @@ enum AVPacketSideDataType { > > #define AV_PKT_DATA_QUALITY_FACTOR AV_PKT_DATA_QUALITY_STATS //DEPRECATED > > +/** > + * This structure stores information for decoding, presenting, or otherwise ^ I didn't mean for you to drop the 'auxiliary' that used to be here - it (or some other equivalent wording) should be here to make it clear that side data applies in additon/on top of the main coded bitstream. > + * processing the coded stream. It is typically exported by demuxers and > + * encoders and can be fed to decoders and muxers in a per packet basis, or as ^ / \ either > + * global side data (applying to the entire coded stream) as follows: The following bullet points apply only to the global side data, so you should start a new sentence that makes that explicit. > + * - During demuxing, it will be exported through global side data in > + * @ref AVStream.codecpar.side_data "AVStream's codec parameters", which can > + * then be passed as input to decoders through the > + * @ref AVCodecContext.coded_side_data "decoder context's side data", for > + * initialization. > + * - For muxing, it can be fed through global side data in > + * @ref AVStream.codecpar.side_data "AVStream's codec parameters", typically > + * the output of encoders through the @ref AVCodecContext.coded_side_data > + * "encoder context's side data", for initialization. > + * > + * Different modules may accept or export different types of side data > + * depending on media type and codec. Refer to @ref AVPacketSideDataType for a > + * list of defined types and where they may be found or used. > + */ -- Anton Khirnov _______________________________________________ ffmpeg-devel mailing list ffmpeg-devel@ffmpeg.org https://ffmpeg.org/mailman/listinfo/ffmpeg-devel To unsubscribe, visit link above, or email ffmpeg-devel-request@ffmpeg.org with subject "unsubscribe".
next prev parent reply other threads:[~2023-10-04 14:46 UTC|newest] Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top 2023-10-04 12:28 [FFmpeg-devel] [PATCH 00/11 v6] AVCodecContext and AVCodecParameters side data James Almer 2023-10-04 12:28 ` [FFmpeg-devel] [PATCH 01/11] avcodec/packet: add generic side data helpers James Almer 2023-10-04 12:28 ` [FFmpeg-devel] [PATCH 02/11] avcodec/codec_par: add side data to AVCodecParameters James Almer 2023-10-04 12:28 ` [FFmpeg-devel] [PATCH 03/11] avformat/avformat: use the side data from AVStream.codecpar James Almer 2023-10-06 3:04 ` Andreas Rheinhardt 2023-10-06 11:34 ` James Almer 2023-10-04 12:28 ` [FFmpeg-devel] [PATCH 04/11] avcodec/packet: add some documentation for AVPacketSideData James Almer 2023-10-04 14:46 ` Anton Khirnov [this message] 2023-10-04 12:28 ` [FFmpeg-devel] [PATCH 05/11] fftools/ffmpeg: stop using AVStream.side_data James Almer 2023-10-04 12:28 ` [FFmpeg-devel] [PATCH 06/11] fftools/ffplay: " James Almer 2023-10-04 12:28 ` [FFmpeg-devel] [PATCH 07/11] fftools/ffprobe: " James Almer 2023-10-04 12:28 ` [FFmpeg-devel] [PATCH 08/11] avcodec/hevcdec: check for DOVI configuration record in AVCodecContext side data James Almer 2023-10-04 12:28 ` [FFmpeg-devel] [PATCH 09/11] avcodec/decode: propagate global side data to frames James Almer 2023-10-04 12:28 ` [FFmpeg-devel] [PATCH 10/11] fftools/ffmpeg: stop injecting stream side data in packets James Almer 2023-10-04 12:28 ` [FFmpeg-devel] [PATCH 11/11] fftools/ffplay: " James Almer 2023-10-04 14:47 ` [FFmpeg-devel] [PATCH 00/11 v6] AVCodecContext and AVCodecParameters side data Anton Khirnov -- strict thread matches above, loose matches on Subject: below -- 2023-09-27 13:12 [FFmpeg-devel] [PATCH 00/11 v5] " James Almer 2023-09-27 13:12 ` [FFmpeg-devel] [PATCH 04/11] avcodec/packet: add some documentation for AVPacketSideData James Almer 2023-10-03 11:02 ` Anton Khirnov
Reply instructions: You may reply publicly to this message via plain-text email using any one of the following methods: * Save the following mbox file, import it into your mail client, and reply-to-all from there: mbox Avoid top-posting and favor interleaved quoting: https://en.wikipedia.org/wiki/Posting_style#Interleaved_style * Reply using the --to, --cc, and --in-reply-to switches of git-send-email(1): git send-email \ --in-reply-to=169643079949.6638.10107251396186814606@lain.khirnov.net \ --to=anton@khirnov.net \ --cc=ffmpeg-devel@ffmpeg.org \ /path/to/YOUR_REPLY https://kernel.org/pub/software/scm/git/docs/git-send-email.html * If your mail client supports setting the In-Reply-To header via mailto: links, try the mailto: link
Git Inbox Mirror of the ffmpeg-devel mailing list - see https://ffmpeg.org/mailman/listinfo/ffmpeg-devel This inbox may be cloned and mirrored by anyone: git clone --mirror https://master.gitmailbox.com/ffmpegdev/0 ffmpegdev/git/0.git # If you have public-inbox 1.1+ installed, you may # initialize and index your mirror using the following commands: public-inbox-init -V2 ffmpegdev ffmpegdev/ https://master.gitmailbox.com/ffmpegdev \ ffmpegdev@gitmailbox.com public-inbox-index ffmpegdev Example config snippet for mirrors. AGPL code for this site: git clone https://public-inbox.org/public-inbox.git