From: James Almer <jamrial@gmail.com> To: ffmpeg-devel@ffmpeg.org Subject: Re: [FFmpeg-devel] [PATCH 1/2] avcodec/decode: make ff_frame_new_side_data_from_buf behave like the function it's a wrapper for Date: Fri, 7 Feb 2025 13:22:33 -0300 Message-ID: <9eff1b60-938a-4085-bc10-73cacf0031a5@gmail.com> (raw) In-Reply-To: <AS8P250MB0744F0C8B1B461D68A8A1FA78FF12@AS8P250MB0744.EURP250.PROD.OUTLOOK.COM> [-- Attachment #1.1.1: Type: text/plain, Size: 1219 bytes --] On 2/7/2025 9:17 AM, Andreas Rheinhardt wrote: > James Almer: >> It's less confusing to have ff_frame_new_side_data_from_buf() be a drop in >> replacement for av_frame_side_data_add(), and the addition of the missing flags >> field will make it more versatile, as will be seen in the following commit. >> >> Signed-off-by: James Almer <jamrial@gmail.com> >> --- >> libavcodec/av1dec.c | 6 ++++-- >> libavcodec/decode.c | 13 +++++-------- >> libavcodec/decode.h | 11 +++++++---- >> libavcodec/h2645_sei.c | 12 ++++++++---- >> libavcodec/hevc/hevcdec.c | 7 +++++-- >> libavcodec/hevc/refs.c | 6 ++++-- >> libavcodec/libdav1d.c | 6 ++++-- >> libavcodec/libjxldec.c | 6 ++++-- >> libavcodec/mpeg12dec.c | 6 ++++-- >> 9 files changed, 45 insertions(+), 28 deletions(-) [...] > > This adds these cleanup av_buffer_unref() everywhere. That is not an > improvement. It makes the function have the same semantics as av_frame_side_data_add(), including the addition of the flags argument, so it can be a direct drop in replacement in lavc. This does result in a potential extra cleaning step for callers, but it's hardly a problem. [-- Attachment #1.2: OpenPGP digital signature --] [-- Type: application/pgp-signature, Size: 495 bytes --] [-- Attachment #2: Type: text/plain, Size: 251 bytes --] _______________________________________________ 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".
prev parent reply other threads:[~2025-02-07 16:22 UTC|newest] Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top 2025-02-04 21:12 James Almer 2025-02-04 21:12 ` [FFmpeg-devel] [PATCH 2/2] avcodec/hevc/hevcdec: simplify creating a new reference to HDR10 side data James Almer 2025-02-07 12:17 ` [FFmpeg-devel] [PATCH 1/2] avcodec/decode: make ff_frame_new_side_data_from_buf behave like the function it's a wrapper for Andreas Rheinhardt 2025-02-07 16:22 ` James Almer [this message]
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=9eff1b60-938a-4085-bc10-73cacf0031a5@gmail.com \ --to=jamrial@gmail.com \ --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