From: "softworkz ." <softworkz-at-hotmail.com@ffmpeg.org>
To: FFmpeg development discussions and patches <ffmpeg-devel@ffmpeg.org>
Subject: Re: [FFmpeg-devel] [PATCH v2] ffmpeg: Don't print graphs if there are no outputs yet
Date: Sun, 18 May 2025 14:57:01 +0000
Message-ID: <DM8P223MB03652E3E135B77B5DBBF0759BA9DA@DM8P223MB0365.NAMP223.PROD.OUTLOOK.COM> (raw)
In-Reply-To: <40001c07-a1ac-4075-8c8c-da684461c82e@jkqxz.net>
> -----Original Message-----
> From: ffmpeg-devel <ffmpeg-devel-bounces@ffmpeg.org> On Behalf Of Mark
> Thompson
> Sent: Sonntag, 18. Mai 2025 16:22
> To: ffmpeg-devel@ffmpeg.org
> Subject: Re: [FFmpeg-devel] [PATCH v2] ffmpeg: Don't print graphs if there are
> no outputs yet
>
> On 17/05/2025 21:04, softworkz . wrote:
> >> -----Original Message-----
> >> From: ffmpeg-devel <ffmpeg-devel-bounces@ffmpeg.org> On Behalf Of Mark
> >> Thompson
> >> Sent: Samstag, 17. Mai 2025 22:02
> >> To: ffmpeg-devel@ffmpeg.org
> >> Subject: [FFmpeg-devel] [PATCH v2] ffmpeg: Don't print graphs if there are
> no
> >> outputs yet
> >>
> >> Avoids writing an empty json blob in setup error cases.
> >> ---
> >> On 17/05/2025 20:08, softworkz . wrote:
> >>> If you could resubmit without the nb_filtergraphs check that would be
> fine!
> >>
> >> Sure, here.
> >>
> >> Thanks,
> >>
> >> - Mark
> >>
> >> fftools/ffmpeg.c | 2 +-
> >> 1 file changed, 1 insertion(+), 1 deletion(-)
> >>
> >> diff --git a/fftools/ffmpeg.c b/fftools/ffmpeg.c
> >> index 964770df23..bd6f22e421 100644
> >> --- a/fftools/ffmpeg.c
> >> +++ b/fftools/ffmpeg.c
> >> @@ -309,7 +309,7 @@ const AVIOInterruptCB int_cb = { decode_interrupt_cb,
> NULL
> >> };
> >>
> >> static void ffmpeg_cleanup(int ret)
> >> {
> >> - if (print_graphs || print_graphs_file)
> >> + if ((print_graphs || print_graphs_file) && nb_output_files > 0)
> >> print_filtergraphs(filtergraphs, nb_filtergraphs, input_files,
> >> nb_input_files, output_files, nb_output_files);
> >>
> >> if (do_benchmark) {
> >> --
> >
> > Excellent, thanks a lot for reviewing the feature!
> >
> > LGTM
> Set applied.
>
> Suggest doing any non-performance-critical development (like this) with asan
> enabled in future; it doesn't slow things down very much and makes it easier
> to catch and fix leaks as you go along.
It's a good idea - I didn't have it on the record anymore after the pause.
In the past, it had often caused trouble with MSVC (/fsanitize=address), so
we had it only in a Linux CI - which this work didn't go through 😊
I'll check it out, maybe MS have made some progress with it.
Thanks for the suggestion and the patches,
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".
next prev parent reply other threads:[~2025-05-18 14:57 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-05-17 20:02 Mark Thompson
2025-05-17 20:04 ` softworkz .
2025-05-18 14:21 ` Mark Thompson
2025-05-18 14:57 ` softworkz . [this message]
2025-05-19 20:08 ` Mark Thompson
2025-05-19 21:13 ` softworkz .
2025-05-20 2:14 ` 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=DM8P223MB03652E3E135B77B5DBBF0759BA9DA@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