From: Michael Niedermayer <michael@niedermayer.cc> To: FFmpeg development discussions and patches <ffmpeg-devel@ffmpeg.org> Subject: Re: [FFmpeg-devel] [PATCH] Macroblocks modes extraction Date: Fri, 4 Jul 2025 13:05:00 +0200 Message-ID: <20250704110500.GT29660@pb2> (raw) In-Reply-To: <67c3bd5d-4570-48d3-9957-60f788adfcb2@regaud-chapuy.fr> [-- Attachment #1.1: Type: text/plain, Size: 1794 bytes --] Hi On Wed, Jul 02, 2025 at 12:57:46PM +0200, Timothee wrote: > Hello, > > I am working on a modification toextract per-macroblock prediction modes > (H.264 for now). The goal is to make this information available to > vf_codecview and print it in a log file (for now). > > This are what I have added: > > 1. > > A new H264MBInfostruct holding the prediction modes. If existing data structures proof inadequate then a newly introduced data structure should allow storing macroblock info for an arbitrary square lattice of macroblocks and arbitrary rectangular subdivision tree. Or said differently, new API should support H264, H265, H266 We cannot have a incompatible data structure for each standard in public API > > 2. > > An AVBufferRef *mb_info_refis added to the H264Picturestruct to > store this data for each picture. > > 3. > > This buffer is allocated with av_buffer_allocz()in > alloc_picture()and its reference is released with > av_buffer_unref()in ff_h264_unref_picture(). > > 4. > > A new function, ff_h264_collect_mb_info(), is called after > macroblock decoding to populate the buffer. > > 5. > > In output_frame(), a new side data (AV_FRAME_DATA_H264_MB_INFO) > buffer is allocated, and the contents of srcp->mb_info_ref->dataare > copied into it. > > 6. A new function to log the result in vf_codecview.c > > This implementation results in a segmentation fault. I guess it is a race > condition, but I am struggling to fix it. missing entry in sd_props[] also make sure "make fate" works thx [...] -- Michael GnuPG fingerprint: 9FF2128B147EF6730BADF133611EC787040B0FAB Why not whip the teacher when the pupil misbehaves? -- Diogenes of Sinope [-- Attachment #1.2: signature.asc --] [-- Type: application/pgp-signature, Size: 195 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".
next prev parent reply other threads:[~2025-07-04 11:05 UTC|newest] Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top 2025-07-02 10:57 Timothee 2025-07-04 11:05 ` Michael Niedermayer [this message] 2025-07-04 13:04 ` Timothée 2025-07-04 12:36 ` James Almer 2025-07-04 13:22 ` Timothée
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=20250704110500.GT29660@pb2 \ --to=michael@niedermayer.cc \ --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