Git Inbox Mirror of the ffmpeg-devel mailing list - see https://ffmpeg.org/mailman/listinfo/ffmpeg-devel
 help / color / mirror / Atom feed
From: Niklas Haas <ffmpeg@haasn.xyz>
To: FFmpeg development discussions and patches <ffmpeg-devel@ffmpeg.org>
Subject: Re: [FFmpeg-devel] [PATCH] fftools/ffmpeg_filter: add -print_filter_graph option
Date: Mon, 17 Feb 2025 14:50:34 +0100
Message-ID: <20250217145034.GB92368@haasn.xyz> (raw)
In-Reply-To: <DM8P223MB036551A34683E264AC0FA0ADBAFB2@DM8P223MB0365.NAMP223.PROD.OUTLOOK.COM>

On Mon, 17 Feb 2025 13:40:49 +0000 Soft Works <softworkz-at-hotmail.com@ffmpeg.org> wrote:
> Well, then the question would be when or whether this future will become a reality?
>
> Or maybe the solution rather lies in the past?
>
> IIRC, I had already submitted a patchset with a complete solution:
>
> - It includes absolutely all relevant information
>   - filter string from the command line
>   - filter name and description
>   - parsed options
>   - formats, hw context
>   - all input and output pads/connections
>     including all format information
>
> - It prints using the same method like FFprobe, so it can print as
>   - default
>   - xml
>   - json
>   - csv
>
> - Here's an example JSON output:
>
> https://gist.github.com/softworkz/2a9e8699b288f5d40fa381c2a496e165

That seems amazing and exactly what I need.

>
>
> I can resubmit it, it's the most comprehensive implementation in this regard.

Yes, please resubmit it. I will review it.

>
> 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".
_______________________________________________
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-02-17 13:50 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-02-17 12:17 Niklas Haas
2025-02-17 12:42 ` Nicolas George
2025-02-17 13:40   ` Soft Works
2025-02-17 13:50     ` Niklas Haas [this message]
2025-02-17 13:53   ` Niklas Haas
2025-02-17 15:35     ` Nicolas George

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=20250217145034.GB92368@haasn.xyz \
    --to=ffmpeg@haasn.xyz \
    --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