From: Devlist Archive <devlist@rlb.org>
To: FFmpeg development discussions and patches <ffmpeg-devel@ffmpeg.org>
Subject: Re: [FFmpeg-devel] [RFC] Subtitle Filtering Ramp-Up
Date: Tue, 3 Jun 2025 09:51:15 -0700
Message-ID: <CANJxsBkOcvdBaCvE7ZbQBAyvdq3bK4qzPE584xXikPSf0eLWBw@mail.gmail.com> (raw)
In-Reply-To: <3a57e98a-df14-4ea3-bc53-696f0bff959b@gmail.com>
Please can we stop keeping score and give everyone a chance to actually get
some work done? I would love to see more objective discussions on this
topic. As others have mentioned, let's focus on why specific things are
needed so any objections can be understood and translated into code
modifications that can make a patchset that can actually be merged. Please
leave personal censure or flaming to other conversations. Maybe we can
pull up those past explanations and objections so they can be addressed
without having to rehash the past. Some of those conversations predate my
archive of the ML so may need to be restated for me to understand.
One subject that derailed a previous attempt I made at discussing
subtitles, captions and general ancillary data is explained here. The
terminology used on here is not always precise in acknoledging the
differences between data types such as captions data, subtitle frames,
timed text, teletext, etc. Filtering may also be desirable for non
subtitle ancillary information as referenced.
https://github.com/softworkz/SubtitleFilteringDemos/issues/5
I love the ambition of a filtering framework where subtitle types and
formats can be converted and manipulated, but let's make sure basic data
routing is also allowed by the new infrastructure.
On Tue, Jun 3, 2025 at 9:48 AM James Almer <jamrial@gmail.com> wrote:
> On 6/3/2025 1:40 PM, Nicolas George wrote:
> > James Almer (HE12025-06-03):
> >> The first sentence was unnecessary. No need to be this aggressive.
> >
> > “softworks” has been abusing many people in the last week but it is
> > Lynne that you decide to chide?
>
> I missed it if he was aggressive to someone else before. I just saw this
> email and replied accordingly.
> In any case, aggression to fight aggression goes nowhere.
>
> _______________________________________________
> 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".
next prev parent reply other threads:[~2025-06-03 16:51 UTC|newest]
Thread overview: 55+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-06-03 14:20 softworkz .
2025-06-03 16:00 ` Lynne
2025-06-03 16:02 ` James Almer
2025-06-03 16:40 ` Nicolas George
2025-06-03 16:48 ` James Almer
2025-06-03 16:51 ` Devlist Archive [this message]
2025-06-03 17:59 ` Nicolas George
2025-06-03 16:12 ` softworkz .
2025-06-03 16:12 ` Devin Heitmueller
2025-06-03 16:43 ` Nicolas George
2025-06-03 17:07 ` softworkz .
2025-06-03 17:15 ` Devlist Archive
2025-06-03 17:16 ` Devlist Archive
2025-06-03 17:19 ` softworkz .
2025-06-04 15:49 ` Rémi Denis-Courmont
2025-06-04 17:13 ` softworkz .
2025-06-04 17:25 ` Nicolas George
2025-06-04 17:31 ` softworkz .
2025-06-04 19:02 ` softworkz .
2025-06-03 17:17 ` softworkz .
2025-06-03 16:28 ` softworkz .
2025-06-03 18:02 ` Hendrik Leppkes
2025-06-03 18:34 ` Zach Swena
2025-06-04 0:01 ` Michael Niedermayer
2025-06-04 7:13 ` Nicolas George
2025-06-04 7:22 ` Diederick C. Niehorster
2025-06-04 7:25 ` Nicolas George
2025-06-04 17:24 ` softworkz .
2025-06-04 17:29 ` Nicolas George
2025-06-04 17:33 ` softworkz .
2025-06-04 17:35 ` Nicolas George
2025-06-04 17:40 ` softworkz .
2025-06-04 17:44 ` Nicolas George
2025-06-04 17:54 ` softworkz .
2025-06-04 17:57 ` Nicolas George
2025-06-04 18:11 ` softworkz .
2025-06-04 18:12 ` Nicolas George
2025-06-04 18:17 ` softworkz .
2025-06-04 20:42 ` Michael Niedermayer
2025-06-05 0:17 ` softworkz .
2025-06-06 14:32 ` Nicolas George
2025-06-06 14:50 ` Devin Heitmueller
2025-06-08 13:10 ` Nicolas George
2025-06-06 16:54 ` softworkz .
2025-06-07 16:19 ` softworkz .
2025-06-07 17:25 ` Kieran Kunhya via ffmpeg-devel
2025-06-07 17:45 ` softworkz .
2025-06-03 19:13 ` softworkz .
2025-06-04 7:34 ` Nicolas George
2025-06-04 1:16 ` softworkz .
2025-06-04 7:36 ` Nicolas George
2025-06-03 19:23 ` softworkz .
2025-06-04 7:33 ` Nicolas George
2025-06-04 18:35 ` softworkz .
2025-06-05 0:44 ` 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=CANJxsBkOcvdBaCvE7ZbQBAyvdq3bK4qzPE584xXikPSf0eLWBw@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