From: James Almer <jamrial@gmail.com> To: FFmpeg development discussions and patches <ffmpeg-devel@ffmpeg.org> Subject: Re: [FFmpeg-devel] [PATCH] ffmpeg: Carry streamid as metadata key 'id' Date: Tue, 16 Apr 2024 09:52:59 -0300 Message-ID: <CAOZuJMjbT9tXFFP2TY+3G+AXp7rSHzHtkUOkUSM+R69MFjOryg@mail.gmail.com> (raw) In-Reply-To: <171327111150.22242.6810934335632875664@lain.khirnov.net> On Tue, Apr 16, 2024 at 9:38 AM Anton Khirnov <anton@khirnov.net> wrote: > Quoting Tomas Härdin (2024-04-12 11:40:47) > > This idea could be extended to other fields not presently considered to > > be metadata, that would be handy to treat as such. > > > > I use the key "id" because ffprobe outputs id= for streamid. Another > > option could be to collect these types of metadata that go into > > AVStream fields under a namespace like FFMPEG: or AVSTREAM: or > > something, then delete all of them using AV_DICT_IGNORE_SUFFIX near the > > end of of_open() since they're for internal ffmpeg use. > > > > The FATE change is just because av_dict() changes the order of things > > when elements are deleted. > > > > /Tomas > > > > From 7799f1b2eb8ab02e58118565f3e889fbe0d568a7 Mon Sep 17 00:00:00 2001 > > From: =?UTF-8?q?Tomas=20H=C3=A4rdin?= <git@haerdin.se> > > Date: Fri, 12 Apr 2024 10:34:12 +0200 > > Subject: [PATCH] ffmpeg: Carry streamid as metadata key 'id' > > > > This allows using -map_metadata and -metadata to copy/set streamids > (PIDs). > > I dislike this patch, metadata is the wrong place for such information. > Can it be propagated within the InputStream? > > -- > Anton Khirnov > _______________________________________________ > 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". > _______________________________________________ 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:[~2024-04-16 12:53 UTC|newest] Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top 2024-04-12 9:40 Tomas Härdin 2024-04-12 23:25 ` Michael Niedermayer 2024-04-15 8:35 ` Tomas Härdin 2024-04-16 0:30 ` Michael Niedermayer 2024-04-16 0:33 ` James Almer 2024-04-16 14:00 ` Tomas Härdin 2024-04-16 12:38 ` Anton Khirnov 2024-04-16 12:52 ` James Almer [this message] 2024-04-16 14:12 ` Tomas Härdin 2024-07-01 14:51 ` Anton Khirnov 2024-07-01 14:58 ` Tomas Härdin
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=CAOZuJMjbT9tXFFP2TY+3G+AXp7rSHzHtkUOkUSM+R69MFjOryg@mail.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