From: Michael Niedermayer <michael@niedermayer.cc>
To: FFmpeg development discussions and patches <ffmpeg-devel@ffmpeg.org>
Subject: Re: [FFmpeg-devel] [PATCH v9 1/8] libavcodec/decode.c: intercept `AV_PKT_DATA_METADATA_UPDATE` packet extra data, attach them to the next decoded frame with the same PTS.
Date: Wed, 2 Apr 2025 19:43:03 +0200
Message-ID: <20250402174303.GH4991@pb2> (raw)
In-Reply-To: <20250324145059.16593-2-romain.beauxis@gmail.com>
[-- Attachment #1.1: Type: text/plain, Size: 1487 bytes --]
On Mon, Mar 24, 2025 at 09:50:52AM -0500, Romain Beauxis wrote:
> ---
> libavcodec/decode.c | 131 ++++++++++++++++++++++++++++++++++++++++++++
> 1 file changed, 131 insertions(+)
doesnt apply cleanly:
Applying: libavcodec/decode.c: intercept `AV_PKT_DATA_METADATA_UPDATE` packet extra data, attach them to the next decoded frame with the same PTS.
Using index info to reconstruct a base tree...
M libavcodec/decode.c
.git/rebase-apply/patch:74: tab in indent.
ret->data = pending->data;
warning: 1 line adds whitespace errors.
Falling back to patching base and 3-way merge...
Auto-merging libavcodec/decode.c
CONFLICT (content): Merge conflict in libavcodec/decode.c
error: Failed to merge in the changes.
Patch failed at 0001 libavcodec/decode.c: intercept `AV_PKT_DATA_METADATA_UPDATE` packet extra data, attach them to the next decoded frame with the same PTS.
hint: Use 'git am --show-current-patch=diff' to see the failed patch
hint: When you have resolved this problem, run "git am --continue".
hint: If you prefer to skip this patch, run "git am --skip" instead.
hint: To restore the original branch and stop patching, run "git am --abort".
hint: Disable this message with "git config set advice.mergeConflict false"
[...]
--
Michael GnuPG fingerprint: 9FF2128B147EF6730BADF133611EC787040B0FAB
No human being will ever know the Truth, for even if they happen to say it
by chance, they would not even known they had done so. -- Xenophanes
[-- 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-04-02 17:43 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-03-24 14:50 [FFmpeg-devel] [PATCH v9 0/8] Properly decode ogg metadata in ogg/{vorbis, flac, opus} chained bitstreams Romain Beauxis
2025-03-24 14:50 ` [FFmpeg-devel] [PATCH v9 1/8] libavcodec/decode.c: intercept `AV_PKT_DATA_METADATA_UPDATE` packet extra data, attach them to the next decoded frame with the same PTS Romain Beauxis
2025-04-02 17:43 ` Michael Niedermayer [this message]
2025-04-02 18:26 ` Romain Beauxis
2025-04-02 21:29 ` Michael Niedermayer
2025-04-02 22:08 ` Romain Beauxis
2025-04-04 20:11 ` Romain Beauxis
2025-03-24 14:50 ` [FFmpeg-devel] [PATCH v9 2/8] tests: Add stream dump test API util Romain Beauxis
2025-03-24 14:50 ` [FFmpeg-devel] [PATCH v9 3/8] tests: Add chained ogg/vorbis stream dump test Romain Beauxis
2025-03-24 14:50 ` [FFmpeg-devel] [PATCH v9 4/8] libavformat/oggdec.h, libavformat/oggparsevorbis.c: Factor out vorbis metadata update mechanism Romain Beauxis
2025-03-24 14:50 ` [FFmpeg-devel] [PATCH v9 5/8] libavformat/oggparseflac.c: Parse ogg/flac comments in new ogg packets, add them to ogg stream new_metadata Romain Beauxis
2025-03-24 14:50 ` [FFmpeg-devel] [PATCH v9 6/8] tests: Add chained ogg/flac stream dump test Romain Beauxis
2025-03-24 14:50 ` [FFmpeg-devel] [PATCH v9 7/8] libavformat/oggparseopus.c: Parse comments from secondary chained streams header packet Romain Beauxis
2025-03-24 14:50 ` [FFmpeg-devel] [PATCH v9 8/8] tests: Add chained ogg/opus stream dump test Romain Beauxis
2025-04-01 16:04 ` [FFmpeg-devel] [PATCH v9 0/8] Properly decode ogg metadata in ogg/{vorbis, flac, 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=20250402174303.GH4991@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