Git Inbox Mirror of the ffmpeg-devel mailing list - see https://ffmpeg.org/mailman/listinfo/ffmpeg-devel
 help / color / mirror / Atom feed
From: "softworkz ." <softworkz-at-hotmail.com@ffmpeg.org>
To: FFmpeg development discussions and patches <ffmpeg-devel@ffmpeg.org>
Cc: Nicolas Gaullier <nicolas.gaullier@cji.paris>
Subject: Re: [FFmpeg-devel] [PATCH 1/2] fftools/textformat: fix print 64 bit integers
Date: Sun, 22 Jun 2025 22:14:12 +0000
Message-ID: <DM8P223MB036550C71FAD5EE13EBEF360BA7EA@DM8P223MB0365.NAMP223.PROD.OUTLOOK.COM> (raw)
In-Reply-To: <A02CF37B-08A5-49CF-B6CF-7D2F94206FB0@gmail.com>



> -----Original Message-----
> From: ffmpeg-devel <ffmpeg-devel-bounces@ffmpeg.org> On Behalf Of Marvin
> Scholz
> Sent: Freitag, 20. Juni 2025 13:30
> To: FFmpeg development discussions and patches <ffmpeg-devel@ffmpeg.org>
> Cc: Nicolas Gaullier <nicolas.gaullier@cji.paris>
> Subject: Re: [FFmpeg-devel] [PATCH 1/2] fftools/textformat: fix print 64
> bit integers
> 
> 
> 
> On 20 Jun 2025, at 13:07, Nicolas Gaullier wrote:
> 
> > Regression in ffprobe since textformat introduction
> > in d7a3f68feae0b1c3718f9d2671c6d41c60a40680.
> >
> > Fixes #11638
> >
> > Signed-off-by: Nicolas Gaullier <nicolas.gaullier@cji.paris>
> > ---
> >  fftools/textformat/avtextformat.c | 2 +-
> >  fftools/textformat/avtextformat.h | 2 +-
> >  2 files changed, 2 insertions(+), 2 deletions(-)
> >
> > diff --git a/fftools/textformat/avtextformat.c
> b/fftools/textformat/avtextformat.c
> > index 14779e6f0c..14bad9022b 100644
> > --- a/fftools/textformat/avtextformat.c
> > +++ b/fftools/textformat/avtextformat.c
> > @@ -437,7 +437,7 @@ static char *value_string(const
> AVTextFormatContext *tctx, char *buf, int buf_si
> >  }
> >
> >
> > -void avtext_print_unit_int(AVTextFormatContext *tctx, const char
> *key, int value, const char *unit)
> > +void avtext_print_unit_int(AVTextFormatContext *tctx, const char
> *key, int64_t value, const char *unit)
> >  {
> >      char val_str[128];
> >      struct unit_value uv;
> > diff --git a/fftools/textformat/avtextformat.h
> b/fftools/textformat/avtextformat.h
> > index cf23d93871..8316829af5 100644
> > --- a/fftools/textformat/avtextformat.h
> > +++ b/fftools/textformat/avtextformat.h
> > @@ -169,7 +169,7 @@ void avtext_print_integer(AVTextFormatContext
> *tctx, const char *key, int64_t va
> >
> >  int avtext_print_string(AVTextFormatContext *tctx, const char *key,
> const char *val, int flags);
> >
> > -void avtext_print_unit_int(AVTextFormatContext *tctx, const char
> *key, int value, const char *unit);
> > +void avtext_print_unit_int(AVTextFormatContext *tctx, const char
> *key, int64_t value, const char *unit);
> >
> >  void avtext_print_rational(AVTextFormatContext *tctx, const char
> *key, AVRational q, char sep);
> >
> > --
> > 2.47.2
> >
> 
> Looks good.
> 
> Would it be possible to add a test for this to make sure we catch such
> a regression next time?
> 
> (I can also give it a try if you don't want to)

Hi Marvin and Nicolas,

tests are always good. In this case though, I'm wondering whether it
might be better to cleanup and straighten the APIs and implementations
first. 

(look at the value_string() function to see what I mean).

Best regards,
sw




_______________________________________________
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".

  parent reply	other threads:[~2025-06-22 22:14 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-06-20 11:07 Nicolas Gaullier
2025-06-20 11:07 ` [FFmpeg-devel] [PATCH 2/2] fftools/textformat: renamings in print_unit_int for consistency (cosmetic) Nicolas Gaullier
2025-06-22 22:10   ` softworkz .
2025-06-20 11:29 ` [FFmpeg-devel] [PATCH 1/2] fftools/textformat: fix print 64 bit integers Marvin Scholz
2025-06-20 17:18   ` [FFmpeg-devel] [EXTERNE] " Nicolas Gaullier
2025-06-22 22:14   ` softworkz . [this message]
2025-06-22 22:04 ` [FFmpeg-devel] " softworkz .

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=DM8P223MB036550C71FAD5EE13EBEF360BA7EA@DM8P223MB0365.NAMP223.PROD.OUTLOOK.COM \
    --to=softworkz-at-hotmail.com@ffmpeg.org \
    --cc=ffmpeg-devel@ffmpeg.org \
    --cc=nicolas.gaullier@cji.paris \
    /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