Git Inbox Mirror of the ffmpeg-devel mailing list - see https://ffmpeg.org/mailman/listinfo/ffmpeg-devel
 help / color / mirror / Atom feed
From: Mark Thompson <sw@jkqxz.net>
To: ffmpeg-devel@ffmpeg.org
Subject: Re: [FFmpeg-devel] [PATCH 1/3] ffmpeg: Don't print graphs if there are no graphs to print
Date: Sat, 17 May 2025 19:18:54 +0100
Message-ID: <c8badaa1-71df-4c07-8b32-d6590422ab97@jkqxz.net> (raw)
In-Reply-To: <DM8P223MB03655D641279718C96B1FEC4BA92A@DM8P223MB0365.NAMP223.PROD.OUTLOOK.COM>

On 17/05/2025 18:52, softworkz . wrote:
> 
> 
>> -----Original Message-----
>> From: ffmpeg-devel <ffmpeg-devel-bounces@ffmpeg.org> On Behalf Of Mark
>> Thompson
>> Sent: Samstag, 17. Mai 2025 13:14
>> To: ffmpeg-devel@ffmpeg.org
>> Subject: [FFmpeg-devel] [PATCH 1/3] ffmpeg: Don't print graphs if there are no
>> graphs to print
>>
>> Avoids writing an empty json blob in setup error cases.
>> ---
>>  fftools/ffmpeg.c | 3 ++-
>>  1 file changed, 2 insertions(+), 1 deletion(-)
>>
>> diff --git a/fftools/ffmpeg.c b/fftools/ffmpeg.c
>> index 964770df23..ad28cff78d 100644
>> --- a/fftools/ffmpeg.c
>> +++ b/fftools/ffmpeg.c
>> @@ -309,7 +309,8 @@ 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_filtergraphs > 0 || nb_output_files > 0))
>>          print_filtergraphs(filtergraphs, nb_filtergraphs, input_files,
>> nb_input_files, output_files, nb_output_files);
> 
> The feature is not just about filter graphs, that's why it's been renamed
> as "Execution Graph Printing". It also works when no filter graphs are
> in play at all. 
> Here's an example:
> 
> https://softworkz.github.io/ffmpeg_output_apis/1_nofilters_3_in_1_out.html
> 
> 
> As for the nb_output_files check, I'm not sure - is it 0 or 1 in case of
> -f null output?

1, including when you stream copy to null and there aren't any real graphs.  At least one output is mandatory for a valid command line, so it should always appear in non-error cases as far as I am aware.

The aim is to avoid to the nonsense json blob when an early error happens - example below.  It does still get printed on later errors (such as a muxer error), because the graph is created then and some operations will have happened at that point.

Thanks,

- Mark


$ ./ffmpeg_g -print_graphs -i nonexistent -f null -
...
[in#0 @ 0x513000000200] Error opening input: No such file or directory
Error opening input file nonexistent.
Error opening input files: No such file or directory
{
    "graphs": [

    ],
    "inputfiles": [
        {
            "index": "0",
            "inputstreams": [

            ]
        }
    ],
    "decoders": [

    ],
    "encoders": [

    ],
    "outputfiles": [

    ],
    "streamlinks": [

    ]
}

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

  reply	other threads:[~2025-05-17 18:19 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-05-17 11:14 Mark Thompson
2025-05-17 11:14 ` [FFmpeg-devel] [PATCH 2/3] fftools/graphprint: Fix leak of graphprint object Mark Thompson
2025-05-17 17:24   ` softworkz .
2025-05-17 11:14 ` [FFmpeg-devel] [PATCH 3/3] fftools/graphprint: Fix leak of graph section header string Mark Thompson
2025-05-17 17:55   ` softworkz .
2025-05-17 17:52 ` [FFmpeg-devel] [PATCH 1/3] ffmpeg: Don't print graphs if there are no graphs to print softworkz .
2025-05-17 18:18   ` Mark Thompson [this message]
2025-05-17 19:08     ` 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=c8badaa1-71df-4c07-8b32-d6590422ab97@jkqxz.net \
    --to=sw@jkqxz.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