From: Anton Khirnov <anton@khirnov.net> To: FFmpeg development discussions and patches <ffmpeg-devel@ffmpeg.org> Subject: Re: [FFmpeg-devel] [PATCH] lavc/bsf: add a showinfo filter Date: Tue, 30 Jan 2024 13:51:55 +0100 Message-ID: <170661911550.1197.2611997212025820879@lain.khirnov.net> (raw) In-Reply-To: <f98e5249-cc83-4c77-a490-88e2b0e92ffd@gmail.com> Quoting James Almer (2024-01-30 13:39:19) > > + av_log(ctx, AV_LOG_INFO, > > + "n:%7"PRIu64" " > > + "size:%7d " > > + "pts:%s pt:%s " > > + "dts:%s dt:%s " > > + "ds:%"PRId64" d:%s " > > Why the trailing space? Copypasted from above mainly. But also it doesn't hurt and adding more entries won't require modifying this line. > > > + "\n", > > + priv->nb_packets, pkt->size, > > + av_ts2str(pkt->pts), av_ts2timestr(pkt->pts, &ctx->time_base_in), > > + av_ts2str(pkt->dts), av_ts2timestr(pkt->dts, &ctx->time_base_in), > > + pkt->duration, av_ts2timestr(pkt->duration, &ctx->time_base_in)); > > No av_ts2str for duration? Yes, duration cannot be AV_NOPTS_VALUE. > Also, missing side data. It's useful to know if a bitstream in the > chain/list added or removed any. > Maybe all the printing from lavf/dump.c can be shared somehow? Or just > duplicated. Exactly, side data makes this more complicated. I'd rather get the basic filter in, and then people can it as they see fit. Another thing I'm deliberately not printing yet is some sort of codec parameters summary. Patches welcome. -- 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".
next prev parent reply other threads:[~2024-01-30 12:51 UTC|newest] Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top 2024-01-29 18:42 Anton Khirnov 2024-01-30 7:17 ` Andreas Rheinhardt 2024-01-30 9:11 ` Anton Khirnov 2024-01-30 12:39 ` James Almer 2024-01-30 12:51 ` Anton Khirnov [this message] 2024-02-12 22:35 ` Alexander Strasser via ffmpeg-devel
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=170661911550.1197.2611997212025820879@lain.khirnov.net \ --to=anton@khirnov.net \ --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