From: Romain Beauxis <romain.beauxis@gmail.com> To: FFmpeg development discussions and patches <ffmpeg-devel@ffmpeg.org> Subject: Re: [FFmpeg-devel] [PATCH v5 1/6] libavcodec: Add generic metadata injection using AV_PKT_DATA_METADATA_UPDATE Date: Mon, 17 Feb 2025 13:18:41 -0600 Message-ID: <CABWZ6OT7+xPjVZuXW2b2nveaDRTQ_fvASQ1oqVY0EQH+Jskd3A@mail.gmail.com> (raw) In-Reply-To: <ad48f422-77ea-4732-803e-ead145789d87@lynne.ee> Le lun. 17 févr. 2025 à 13:10, Lynne <dev@lynne.ee> a écrit : > > On 17/02/2025 17:19, Romain Beauxis wrote: > > libavcodec/decode.c: intercept `AV_PKT_DATA_METADATA_UPDATE` packet extra data, > > attach them to the next decoded frame. > > > > The metadata needs to be cached because there is no guarantee that each packet > > will generate a decoded frame immediately. > > > > `AV_PKT_DATA_METADATA_UPDATE` does not seem used in `libavcodec` at the moment > > so regression risks seem low. > > > > This generic mechanism could be reused to support more in-band metadata update > > in the future. > > Much cleaner than before, thanks. Thanks for the guidance! > Which packets will not generate a decoded frame immediately? When it > comes to audio, all of them should output something immediately. > The code is correct, metadata updates could occur on B-frames in video. > Just wondering. I was working from memory about ogg/flac but got it wrong: flac frames map to ogg packets BUT they can span page boundaries: > * Native FLAC audio frames appear as subsequent packets in the stream. Each packet corresponds to one FLAC audio frame. The first byte of each packet serves as the packet type. >. Since audio packets are native FLAC frames, this first byte will be always 0xFF according to the native FLAC format specification. > * The last page is marked 'end of stream' in the page flags. > * FLAC packets may span page boundaries. Source: https://xiph.org/flac/ogg_mapping.html This is a bit confusing, though. At any rate, however, in the current implementation, flac ogg packet headers are still exported by the demuxer and later ignored by the decoder. These packets would not generate an audio frame. I'm happy to work on further improvement on this as discussed. Then we could consider un-caching the metadata. -- Romain _______________________________________________ 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-02-17 19:19 UTC|newest] Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top 2025-02-17 16:19 [FFmpeg-devel] [PATCH v5 0/6] Properly decode ogg metadata in ogg/flac and ogg/opus chained bitstreams Romain Beauxis 2025-02-17 16:19 ` [FFmpeg-devel] [PATCH v5 1/6] libavcodec: Add generic metadata injection using AV_PKT_DATA_METADATA_UPDATE Romain Beauxis 2025-02-17 19:10 ` Lynne 2025-02-17 19:18 ` Romain Beauxis [this message] 2025-02-18 23:28 ` Lynne 2025-02-19 4:11 ` Romain Beauxis 2025-02-19 4:36 ` Romain Beauxis 2025-02-17 16:19 ` [FFmpeg-devel] [PATCH v5 2/6] tests: Add stream dump test API util Romain Beauxis 2025-02-17 16:19 ` [FFmpeg-devel] [PATCH v5 3/6] Parse ogg/flac comments in new ogg packets Romain Beauxis 2025-02-17 16:19 ` [FFmpeg-devel] [PATCH v5 4/6] tests: Add chained ogg/flac stream dump test Romain Beauxis 2025-02-17 16:19 ` [FFmpeg-devel] [PATCH v5 5/6] Parse comments from secondary chained ogg/opus streams Romain Beauxis 2025-02-17 16:19 ` [FFmpeg-devel] [PATCH v5 6/6] tests: Add chained ogg/opus stream dump test Romain Beauxis 2025-02-17 16:30 ` [FFmpeg-devel] [PATCH v5 0/6] Properly decode ogg metadata in ogg/flac and ogg/opus chained bitstreams Romain Beauxis
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=CABWZ6OT7+xPjVZuXW2b2nveaDRTQ_fvASQ1oqVY0EQH+Jskd3A@mail.gmail.com \ --to=romain.beauxis@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