From: "softworkz ." <softworkz-at-hotmail.com@ffmpeg.org>
To: FFmpeg development discussions and patches <ffmpeg-devel@ffmpeg.org>
Subject: [FFmpeg-devel] Subtitle Filtering: The $1,000 Bounty Challenge
Date: Tue, 3 Jun 2025 21:56:07 +0000
Message-ID: <DM8P223MB03653D0F70C9C4C041BB68FBBA6DA@DM8P223MB0365.NAMP223.PROD.OUTLOOK.COM> (raw)
Hello everybody,
as I am so tired about people who are claiming that the two additional fields (subtitle-start & -duration) would not be required and I would not have made plausible why those would be needed and it would be doable with the pts and duration fields of AVFrame alone, that I'm setting up the following challenge:
I will pay $1,000 (one-thousand US dollar)
to the first person who is able to show me a patched implementation of my Subtitle Filtering Patchset from 2022 (https://github.com/softworkz/FFmpeg/tree/submit_subfiltering) which fulfills the following criteria:
- The subtitle_timing struct from AVFrame is removed and
the information is not stored anywhere else
- All existing functionality is working like it did before
Fineprint
What's crucial is not the absence of those fields.
The point is that it must work without the extra INFORMATION.
This means that any kind of creative way for storing the
extra information is not valid. It must work without,
even at a logical level.
Please do not start working on it yet!!
Contact me first, then I will work out a detailed rule set which clarifies individual conditions
(e.g. specifying which functionality needs to be working and how this is tested, etc.)
But there's no bad surprise when contacting me or something.
This is a serious challenge. I have always said that it is not possible to achieve the same functionality without those extra timing fields.
And I was told that I'm wrong. By several people:
- Lynne
- Anton Khirnov
- Hendrik Leppkes
- and some others
So folks: Here's your chance. According to your attitudes and statements, those 1k USD should be an easy win for you.
Participate and prove your claims - earn that bounty!
(qualified are only persons who have reviewed my patchset and understand the topic)
(the challenges expires on 2025-06-12)
Best regards
softworkz
_______________________________________________
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-06-03 21:56 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=DM8P223MB03653D0F70C9C4C041BB68FBBA6DA@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