From: "softworkz ." <softworkz-at-hotmail.com@ffmpeg.org>
To: FFmpeg development discussions and patches <ffmpeg-devel@ffmpeg.org>
Subject: Re: [FFmpeg-devel] [PATCH] fftools/ffmpeg: move elapsed time counter to the end of the status line
Date: Fri, 9 May 2025 19:06:24 +0000
Message-ID: <DM8P223MB03658D88381A0FEA8A7AE946BA8AA@DM8P223MB0365.NAMP223.PROD.OUTLOOK.COM> (raw)
In-Reply-To: <b5f6e29c-0b22-2e90-4800-504da685ab66@passwd.hu>
> -----Original Message-----
> From: ffmpeg-devel <ffmpeg-devel-bounces@ffmpeg.org> On Behalf Of Marton
> Balint
> Sent: Freitag, 9. Mai 2025 20:56
> To: FFmpeg development discussions and patches <ffmpeg-devel@ffmpeg.org>
> Subject: Re: [FFmpeg-devel] [PATCH] fftools/ffmpeg: move elapsed time counter
> to the end of the status line
>
>
>
> On Fri, 9 May 2025, softworkz . wrote:
>
> >
> >
> >> -----Original Message-----
> >> From: ffmpeg-devel <ffmpeg-devel-bounces@ffmpeg.org> On Behalf Of Marton
> >> Balint
> >> Sent: Freitag, 9. Mai 2025 14:06
> >> To: ffmpeg-devel@ffmpeg.org
> >> Cc: Marton Balint <cus@passwd.hu>
> >> Subject: [FFmpeg-devel] [PATCH] fftools/ffmpeg: move elapsed time counter
> to
> >> the end of the status line
> >>
> >> Elapsed time is much less important than the actual progress, and I am
> >> guessing
> >> several ffmpeg CLI frontends use the existing status line for showing
> >> progress,
> >> so putting a new field in the beginning is less optimal anyway.
> >
> > I agree that it might not be the most important part of the stats,
> > yet, from experience, it is quite often useful.
> >
> > How about adding it to the end, then?
>
> This patch does exactly that.
>
> Regards,
> Marton
Oh, apologies. I stopped reading after the - prefixed lines 😊
Thank you,
sw
Also: LGTM
_______________________________________________
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:[~2025-05-09 19:06 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-05-09 12:06 Marton Balint
2025-05-09 16:24 ` James Almer
2025-05-09 18:22 ` softworkz .
2025-05-09 18:13 ` softworkz .
2025-05-09 18:56 ` Marton Balint
2025-05-09 19:06 ` softworkz . [this message]
2025-05-11 16:57 ` Marton Balint
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=DM8P223MB03658D88381A0FEA8A7AE946BA8AA@DM8P223MB0365.NAMP223.PROD.OUTLOOK.COM \
--to=softworkz-at-hotmail.com@ffmpeg.org \
--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