Git Inbox Mirror of the ffmpeg-devel mailing list - see https://ffmpeg.org/mailman/listinfo/ffmpeg-devel
 help / color / mirror / Atom feed
From: Devlist Archive <devlist@rlb.org>
To: FFmpeg development discussions and patches <ffmpeg-devel@ffmpeg.org>
Subject: Re: [FFmpeg-devel] Captions SCC
Date: Fri, 7 Feb 2025 08:05:08 -0800
Message-ID: <CANJxsBkYuVh8exMSQ9_Yo40=ApHD4PoeOmxy8nof+ABFv-W5vA@mail.gmail.com> (raw)
In-Reply-To: <CAAhd_PXq_RF8rttN9DuccHuYeZQbDyoSOph0G2isLVeEbdY3eg@mail.gmail.com>

My intent with starting this thread was to recruit at least one developer
to help make sure a solution is found.  It kind of got sent off topic to
the user space by some of the replies.  My current understanding is that
the tools used in the ffmpeg commands I was using are actually extracting
subtitles from the video rather than preserving all the captions data like
I thought they were intended to do.  I will take the discussion on the bug
like stuff over to TRAC, but I am still looking for a developer that thinks
they have the skills to implement functions that will preserve display
information in addition to the text.  Correct me if I'm wrong, but my
understanding is that those other lists are for help with user space
commands and bug issues (which is what this thread became) and not
development and trying to communicate with developers about specific
projects and patches.

So to pivot this thread back to its intended purpose, is there anyone in
addition to Soft Works that has an interest in captions filtering topics
and would like to be involved in discussing the specifics of a solution for
608/708 filtering, extraction, and embedding off list so that the required
code can be generated and submitted?

Zach

On Fri, Feb 7, 2025 at 7:39 AM Marth64 <marth64@proxyid.net> wrote:

> Hi folks
>
> Zach (Devlist Archive):
> Thanks for sharing your experience and I hope a resolution comes out
> of it. I encourage you to write this email instead to the ffmpeg-user
> list (or possibly TRAC, our bug trucker), which is better suited for
> discussing issues like yours.
> Let us pivot this conversation there.
>
> Jack Lau:
> I know you mean well and are trying to help. LLM are useful tools, I
> would however recommend giving a heads up that the content was being
> generated so it does not spook people.
> Regarding your own patch, you may send a "Ping" note on your email if
> within a reasonable amount of time nobody has reviewed it (sometimes
> it takes several days, so 5-7 days is a reasonable time to ping).
>
> That said, I think this is thread off topic for the development list's
> core purpose.
> I suggest the above steps forward to get this through the right channels.
>
> Thank you!
> _______________________________________________
> 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-07 16:05 UTC|newest]

Thread overview: 36+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-02-06 10:19 Devlist Archive
2025-02-06 12:57 ` Jack Lau
2025-02-07  5:12   ` Devlist Archive
2025-02-07  7:48     ` Soft Works
2025-02-07  7:58       ` Jack Lau
2025-02-07  8:16         ` Soft Works
2025-02-07  8:26           ` Jack Lau
2025-02-07  9:11             ` Soft Works
2025-02-07  9:44               ` Jack Lau
2025-02-07 15:38                 ` Marth64
2025-02-07 16:05                   ` Devlist Archive [this message]
2025-02-07 16:18                     ` Marth64
2025-02-07 16:37                       ` Marth64
2025-02-07 16:42                         ` Devlist Archive
2025-02-07 18:05                           ` Devin Heitmueller
2025-02-07 18:32                             ` Devlist Archive
2025-02-07 19:03                               ` Devin Heitmueller
2025-02-07 19:31                                 ` Devlist Archive
2025-02-07 19:44                                   ` Soft Works
2025-02-07 19:51                                     ` Devlist Archive
2025-02-07 19:55                                       ` Devin Heitmueller
2025-02-07 19:56                                         ` Devin Heitmueller
2025-02-07 19:56                                       ` Soft Works
2025-02-07 20:20                                         ` Devlist Archive
2025-02-07 19:52                                   ` Devin Heitmueller
2025-02-07 19:54                                     ` Devlist Archive
2025-02-07 17:37                 ` Rémi Denis-Courmont
2025-02-07 17:31           ` Rémi Denis-Courmont
2025-02-07 17:47             ` Soft Works
2025-02-07 18:36       ` Tom Vaughan
2025-02-07 18:54         ` Soft Works
2025-02-07 20:09           ` Tom Vaughan
2025-02-07 20:49             ` Devlist Archive
2025-02-07 20:58               ` Soft Works
2025-02-07 21:05                 ` Devlist Archive
2025-02-07 21:08                 ` Devin Heitmueller

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='CANJxsBkYuVh8exMSQ9_Yo40=ApHD4PoeOmxy8nof+ABFv-W5vA@mail.gmail.com' \
    --to=devlist@rlb.org \
    --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