From: Andreas Rheinhardt <andreas.rheinhardt@outlook.com>
To: ffmpeg-devel@ffmpeg.org
Subject: Re: [FFmpeg-devel] [PATCH] avformat/concat: fix missing metadata
Date: Sun, 3 Jul 2022 15:47:01 +0200
Message-ID: <DB6PR0101MB22146DC61E3D1712EDBBA73E8FBF9@DB6PR0101MB2214.eurprd01.prod.exchangelabs.com> (raw)
In-Reply-To: <YsGcuQqQI5qYUUYm@phare.normalesup.org>
Nicolas George:
> Steven Hartland (12022-07-02):
>> I'm using concat to join multiple files from a GoPro camera including the
>> three metadata streams, with the early return it fails as the metadata
>> stream information is missing so map fails.
>
>> I believe the reason for the failure is that this early return prevents the
>> metadata from being preserved.
>
> You are trying to trick concat into merging files with different streams
> and match streams between them. It is not how concat is designed to
> work, it might work in your particular test case but will not work in
> more complex cases and will break other use cases.
>
> For example, with your change, if you concatenate a file with metadata
> "start_time=12:00" and another with "start_time=12:01", it will generate
> a file with both metadata entries instead of just the first one as would
> be desirable.
>
Actually, the newer entry will overwrite the older entry; if you want
multiple keys with the same value, you have to use the AV_DICT_MULTIKEY
flag.
- Andreas
_______________________________________________
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:[~2022-07-03 13:47 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-06-12 19:48 Steven Hartland
2022-06-19 20:18 ` Marton Balint
2022-07-02 10:44 ` Steven Hartland
2022-07-02 10:47 ` Steven Hartland
2022-07-03 13:42 ` Nicolas George
2022-07-03 13:47 ` Andreas Rheinhardt [this message]
2022-07-03 13:49 ` Nicolas George
2022-07-04 22:33 ` Steven Hartland
2022-07-14 21:46 ` Steven Hartland
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=DB6PR0101MB22146DC61E3D1712EDBBA73E8FBF9@DB6PR0101MB2214.eurprd01.prod.exchangelabs.com \
--to=andreas.rheinhardt@outlook.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