Git Inbox Mirror of the ffmpeg-devel mailing list - see https://ffmpeg.org/mailman/listinfo/ffmpeg-devel
 help / color / mirror / Atom feed
From: Vittorio Palmisano <vpalmisano@gmail.com>
To: FFmpeg development discussions and patches <ffmpeg-devel@ffmpeg.org>
Subject: Re: [FFmpeg-devel] [PATCH] Whisper audio filter
Date: Tue, 15 Jul 2025 09:44:48 +0200
Message-ID: <CADv15W_jJCZS3kLL72WLhHZXdNXXor-AHNUDShkhbrH+25aPkQ@mail.gmail.com> (raw)
In-Reply-To: <20250714214713.GO29660@pb2>

> > +@item gpu_device
> > +The GPU device to use.
> > +Default value: @code{"0"}
>
> is this always a number ?
> if so the documenattion could say that

Yes, it is the device index.

> > +@item destination
> > +If set, the transcription output will be sent to the specified file or URL
> > +(use one of the FFmpeg AVIO protocols); otherwise, the output will be logged as
> > +info messages.
> > +The output will also be set in the "lavfi.whisper.text" frame metadata.
>
> teh documenattion should elaborate on what happens if the destination already
> exists

Ok

> > + if (!av_strcasecmp(wctx->format, "srt")) {
> > + buf =
> > + av_asprintf
> > + ("%d\n%02ld:%02ld:%02ld.%03ld --> %02ld:%02ld:%02ld.%03ld\n%s\n\n",
> > + wctx->index, start_t / 3600000,
> > + (start_t / 60000) % 60, (start_t / 1000) % 60,
> > + start_t % 1000, end_t / 3600000, (end_t / 60000) % 60,
> > + (end_t / 1000) % 60, end_t % 1000, text_cleaned);
> > + } else if (!av_strcasecmp(wctx->format, "json")) {
> > + buf = av_asprintf("{\"start\":%ld,\"end\":%ld,\"text\":\"%s\"}\n",
> > start_t, end_t, text_cleaned);
> > + } else
> > + buf = av_strdup(text_cleaned);
>
> Do you think it would make sense to use avcodec_encode_subtitle() ?
> It would avoid hardcoding these "writers" and could use any we support

avcodec_encode_subtitle should be used to generate a subtitle track, right?
I'm checking how it is used.

> also please make sure to attach the next attach in a way that doesnt corrupt it.
> (i used the forgejo pr to test and read most of this but i think my reply
>  is not very readable as i replied to the mail)

Ok I will use git send-email.
Feel free to comment on
https://code.ffmpeg.org/FFmpeg/FFmpeg/pulls/17/files too.
Thanks
_______________________________________________
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-07-15  7:45 UTC|newest]

Thread overview: 24+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-07-09  7:23 Vittorio Palmisano
2025-07-09 13:36 ` Marvin Scholz
2025-07-09 15:24 ` Zhao Zhili
2025-07-10  8:43   ` Vittorio Palmisano
2025-07-10  9:47     ` Zhao Zhili
2025-07-10 12:41   ` Michael Niedermayer
2025-07-09 23:37 ` Michael Niedermayer
2025-07-10  8:34   ` Vittorio Palmisano
2025-07-10 10:05     ` Marvin Scholz
2025-07-10 10:20       ` Vittorio Palmisano
2025-07-10 10:25         ` Vittorio Palmisano
2025-07-10 12:20           ` Michael Niedermayer
2025-07-11  8:41             ` Vittorio Palmisano
2025-07-11  9:07               ` Vittorio Palmisano
2025-07-11 19:05                 ` Marvin Scholz
2025-07-12  0:03               ` Michael Niedermayer
2025-07-13 11:16                 ` Vittorio Palmisano
2025-07-14 10:34                   ` Vittorio Palmisano
2025-07-14 21:47                     ` Michael Niedermayer
2025-07-15  7:44                       ` Vittorio Palmisano [this message]
2025-07-10 11:31     ` Michael Niedermayer
2025-07-10 12:07       ` Nicolas George
2025-07-10 12:10         ` Nicolas George
2025-07-09 23:41 ` Michael Niedermayer

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=CADv15W_jJCZS3kLL72WLhHZXdNXXor-AHNUDShkhbrH+25aPkQ@mail.gmail.com \
    --to=vpalmisano@gmail.com \
    --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