From: "softworkz ." <softworkz-at-hotmail.com@ffmpeg.org> To: Kieran Kunhya <kieran618@googlemail.com>, FFmpeg development discussions and patches <ffmpeg-devel@ffmpeg.org> Subject: Re: [FFmpeg-devel] [PATCH 3/3] tools/ffmpeg-sg: Include show-graph wrapper script in build output Date: Wed, 11 Jun 2025 22:04:52 +0000 Message-ID: <DM8P223MB0365A474102F1ACC615E3876BA75A@DM8P223MB0365.NAMP223.PROD.OUTLOOK.COM> (raw) In-Reply-To: <CABGuwEm72Ynf=anVta4rj0pOPThHeM0aweAbYVTBuvLsQSbJ4Q@mail.gmail.com> > -----Original Message----- > From: Kieran Kunhya <kieran618@googlemail.com> > Sent: Mittwoch, 11. Juni 2025 23:14 > To: FFmpeg development discussions and patches <ffmpeg- > devel@ffmpeg.org> > Subject: Re: [FFmpeg-devel] [PATCH 3/3] tools/ffmpeg-sg: Include > show-graph wrapper script in build output > > On Wed, Jun 11, 2025 at 9:58 PM softworkz . > <softworkz-at-hotmail.com@ffmpeg.org> wrote: > > > > > > > > > -----Original Message----- > > > From: ffmpeg-devel <ffmpeg-devel-bounces@ffmpeg.org> On Behalf Of > > > Marton Balint > > > Sent: Mittwoch, 11. Juni 2025 21:18 > > > To: FFmpeg development discussions and patches <ffmpeg- > > > devel@ffmpeg.org> > > > Subject: Re: [FFmpeg-devel] [PATCH 3/3] tools/ffmpeg-sg: Include > > > show-graph wrapper script in build output > > > > > > > > > > > > On Mon, 9 Jun 2025, softworkz wrote: > > > > > > > From: softworkz <softworkz@hotmail.com> > > > > > > > > Signed-off-by: softworkz <softworkz@hotmail.com> > > > > --- > > > > .gitignore | 1 + > > > > fftools/Makefile | 14 ++++++++++++-- > > > > 2 files changed, 13 insertions(+), 2 deletions(-) > > > > > > > > diff --git a/.gitignore b/.gitignore > > > > index 59c89da5e0..989c702b6c 100644 > > > > --- a/.gitignore > > > > +++ b/.gitignore > > > > @@ -32,6 +32,7 @@ > > > > /.config > > > > /.version > > > > /ffmpeg > > > > +/ffmpeg-sg > > > > Should we have a script to run ffplay after a user has encoded a file > as well? > > Kieran ----------------- The difference to this - as far as I'm seeing it - is that that the execution graph display is of a very different nature: It is (at least logically) not an output of FFmpeg like a produced media file. It rather provides insights into FFmpeg's own operations - to the operator and not to the client/consumer of the output. It could even be seen as a kind of (passive) UI - for monitoring and diagnosis, which is something very different from launching a generated video file. And regarding the latter - don't we have those output devices, where you just need to add a few letters to the command line to "launch" a video window that is showing the output? Best regards, 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-06-11 22:05 UTC|newest] Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top 2025-06-09 19:23 [FFmpeg-devel] [PATCH 0/3] tools/ffmpeg-sg: Add show-graph wrapper scripts (aka killer feature) ffmpegagent 2025-06-09 19:23 ` [FFmpeg-devel] [PATCH 1/3] tools/ffmpeg-sg: Add show-graph wrapper script for Linux softworkz 2025-06-09 19:23 ` [FFmpeg-devel] [PATCH 2/3] tools/ffmpeg-sg: Add show-graph wrapper script for Windows softworkz 2025-06-09 19:23 ` [FFmpeg-devel] [PATCH 3/3] tools/ffmpeg-sg: Include show-graph wrapper script in build output softworkz 2025-06-11 19:18 ` Marton Balint 2025-06-11 20:58 ` softworkz . 2025-06-11 21:14 ` Kieran Kunhya via ffmpeg-devel [not found] ` <CABGuwEm72Ynf=anVta4rj0pOPThHeM0aweAbYVTBuvLsQSbJ4Q@mail.gmail.com> 2025-06-11 21:39 ` softworkz . 2025-06-11 22:04 ` softworkz . [this message] 2025-06-12 7:40 ` Nicolas George 2025-06-12 18:42 ` softworkz . 2025-06-12 19:06 ` Nicolas George 2025-06-12 19:20 ` softworkz . 2025-06-09 22:49 ` [FFmpeg-devel] [PATCH 0/3] tools/ffmpeg-sg: Add show-graph wrapper scripts (aka killer feature) Kieran Kunhya via ffmpeg-devel 2025-06-11 14:42 ` Nicolas George [not found] ` <CABGuwEnDSAKEEP6e5yUzeXM_bp5EKV2bPHaL8+wM+Pbmm5KBPQ@mail.gmail.com> 2025-06-10 13:31 ` softworkz . 2025-06-10 15:28 ` 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=DM8P223MB0365A474102F1ACC615E3876BA75A@DM8P223MB0365.NAMP223.PROD.OUTLOOK.COM \ --to=softworkz-at-hotmail.com@ffmpeg.org \ --cc=ffmpeg-devel@ffmpeg.org \ --cc=kieran618@googlemail.com \ /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