Git Inbox Mirror of the ffmpeg-devel mailing list - see https://ffmpeg.org/mailman/listinfo/ffmpeg-devel
 help / color / mirror / Atom feed
From: Bodecs Bela <bodecsb@vivanet.hu>
To: ffmpeg-devel@ffmpeg.org
Subject: Re: [FFmpeg-devel] [PATCH v1] ffmpeg: add optional JSON output of inputs, outputs, mapping, and progress
Date: Sun, 31 Jul 2022 15:15:23 +0200
Message-ID: <bdcee8a2-cf11-6fd6-87fd-9acd58e551d5@vivanet.hu> (raw)
In-Reply-To: <165901736482.10012.12784827214024177578@lain.khirnov.net>


2022.07.28. 16:09 keltezéssel, Anton Khirnov írta:
> Sorry, I do not like your patch. The problem is that this essentialy
> codifies ffmpeg's internal structure and makes into a kind of a public
> interface, which makes it harder for us to change it.
>
> Given that I'm currently in the middle of a big reshuffle of ffmpeg's
> internals, this patch would conflict with my work.
> And even after I'm done, we should think very carefully about exactly
> which parts of ffmpeg behaviour (if any at all) we want to guarantee.

Hi Anton,

I agree with you and we may split this whole thing into two separate 
decision:

- should we make something in ffmpeg to be able monitored by automation 
(e.g. a "monitoring api" - for long running ffmpeg processes)

- if the answer is yes, then we need to discuss about how we should do it.

My answer is yes for the first question but I haven't got the knowledge 
to make a good proposal for the second question,

but maybe anybody else can.

best,

Bela


_______________________________________________
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:[~2022-07-31 13:15 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-06-09 12:47 Ingo Oppermann
2022-07-25 17:47 ` Ingo Oppermann
2022-07-28 14:09   ` Anton Khirnov
2022-07-31 13:15     ` Bodecs Bela [this message]

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=bdcee8a2-cf11-6fd6-87fd-9acd58e551d5@vivanet.hu \
    --to=bodecsb@vivanet.hu \
    --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