From: Michael Niedermayer <michael@niedermayer.cc> To: FFmpeg development discussions and patches <ffmpeg-devel@ffmpeg.org> Subject: Re: [FFmpeg-devel] [PATCH] ffmpeg: Carry streamid as metadata key 'id' Date: Sat, 13 Apr 2024 01:25:09 +0200 Message-ID: <20240412232509.GB6420@pb2> (raw) In-Reply-To: <71fccb5a1e28dfd23e3dd710c86c8a3a662bbd61.camel@haerdin.se> [-- Attachment #1.1: Type: text/plain, Size: 2530 bytes --] On Fri, Apr 12, 2024 at 11:40:47AM +0200, Tomas Härdin wrote: > 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 > fftools/ffmpeg_demux.c | 5 +++ > fftools/ffmpeg_mux_init.c | 56 ++++++++++++++++++++++++++---------- > tests/ref/fate/matroska-stereo_mode | 6 +-- > 3 files changed, 49 insertions(+), 18 deletions(-) > cd526b2292b6d7e3fb5739a04cf17fbe5f207f16 0001-ffmpeg-Carry-streamid-as-metadata-key-id.patch > 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). > --- > fftools/ffmpeg_demux.c | 5 +++ > fftools/ffmpeg_mux_init.c | 56 +++++++++++++++++++++-------- > tests/ref/fate/matroska-stereo_mode | 6 ++-- > 3 files changed, 49 insertions(+), 18 deletions(-) breaks: ./ffmpeg -i ~/videos/mm-short.mpg -vstats_file /tmp/vstats -bitexact -map 0:1 -map 0:1 -map 0:2 -threads 6 -vcodec libx264 -vcodec libx264 -pass 1 -b:v:0 300k -b:v:1 900k -passlogfile:v:1 /tmp/video2 -passlogfile:v:0 /tmp/video1 -t 1 -y -ab 128k /tmp/x.ts [mpegts @ 0x558d5e3b2140] Duplicate stream id 480 [out#0/mpegts @ 0x558d5e3b2000] Could not write header (incorrect codec parameters ?): Invalid argument [vf#0:0 @ 0x558d5e400400] Error sending frames to consumers: Invalid argument [vf#0:0 @ 0x558d5e400400] Task finished with error code: -22 (Invalid argument) [vf#0:0 @ 0x558d5e400400] Terminating thread with return code -22 (Invalid argument) [out#0/mpegts @ 0x558d5e3b2000] Nothing was written into output file, because at least one of its streams received no packets. [...] -- Michael GnuPG fingerprint: 9FF2128B147EF6730BADF133611EC787040B0FAB The misfortune of the wise is better than the prosperity of the fool. -- Epicurus [-- 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:[~2024-04-12 23:25 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 [this message] 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 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=20240412232509.GB6420@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