From: "softworkz ." <softworkz-at-hotmail.com@ffmpeg.org>
To: FFmpeg development discussions and patches <ffmpeg-devel@ffmpeg.org>
Subject: Re: [FFmpeg-devel] [RFC] Subtitle Filtering Ramp-Up
Date: Wed, 4 Jun 2025 18:11:49 +0000
Message-ID: <DM8P223MB03658B13114F571D04ED0F82BA6CA@DM8P223MB0365.NAMP223.PROD.OUTLOOK.COM> (raw)
In-Reply-To: <aECI9ICQcav2xxaK@phare.normalesup.org>
> -----Original Message-----
> From: ffmpeg-devel <ffmpeg-devel-bounces@ffmpeg.org> On Behalf Of Nicolas
> George
> Sent: Mittwoch, 4. Juni 2025 19:57
> To: FFmpeg development discussions and patches <ffmpeg-devel@ffmpeg.org>
> Subject: Re: [FFmpeg-devel] [RFC] Subtitle Filtering Ramp-Up
>
> softworkz . (HE12025-06-04):
> > Those kinds of texts don't get us anywhere.
>
> I confirm. If you want to get somewhere, get to work.
>
> > Please provide specific example which demonstrate your claims.
>
> Do the work yourself.
If you want to make any claims it is up to you to provide a specific
example scenario which doesn't work.
So far, you have just written some text that sound like there would
be any substance, but this alone is not sufficient to make an objection
It is up to you to provide specific examples for those claims and if
you are unable to do so, there is no other conclusion than that
your claims are not valid.
Also, I have been asking 3 times about your claim that I would have
refused to implement important utility filters and you weren't able
to name those filters.
This should make it very clear to everybody that this claims isn't
worth a penny.
I'm not saying that there aren't any scenarios which it cannot handle,
but it all has to start by naming them, understanding them, and
evaluating their importance.
This is also relevant for any other readers who follow this discussion.
It must be clear and understandable for everybody what is working and
what might not be working and how relevant those cases are which are
not working and how easily or not they can be made working.
You are the objector.
You are making claims.
Provide specific examples to illustrate your claims.
Otherwise, your claims can only be considered invalid.
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-04 18:12 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
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 . [this message]
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=DM8P223MB03658B13114F571D04ED0F82BA6CA@DM8P223MB0365.NAMP223.PROD.OUTLOOK.COM \
--to=softworkz-at-hotmail.com@ffmpeg.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