From: Michael Niedermayer <michael@niedermayer.cc>
To: FFmpeg development discussions and patches <ffmpeg-devel@ffmpeg.org>
Subject: Re: [FFmpeg-devel] VP6 Encoder Proposal- Seeking Feedback and Suggestions
Date: Sat, 12 Apr 2025 02:37:47 +0200
Message-ID: <20250412003747.GG4991@pb2> (raw)
In-Reply-To: <CAHw49E3NONcvXgBNyWAKb+h9ZncLazwRUw6E6bZdEu90MUdLsw@mail.gmail.com>
[-- Attachment #1.1: Type: text/plain, Size: 1678 bytes --]
Hi
On Tue, Apr 08, 2025 at 07:05:16PM +0530, SUBHANGANI JHA wrote:
> Hello FFmpeg developers,
>
> I'm a 2025 Gsoc applicant and have submitted a proposal for implementing a
> basic VP6 Encoder in FFmpeg. I understand the importance of community
> engagement and am reaching out to introduce myself and seek any guidance,
> feedback,or suggestions you might have on the idea or the approach .
> While the proposal is already submitted, I'm highly interested in
> contributing regardless of the outcome and would love to get more involved
> with the FFmpeg development process .
> If there are small tasks or bugs I could help with, or if there is any
> documentation or suggestions for working with encoding pipeline in FFmpeg,
> I would really appreciate being pointed in the right direction.
>
>
> Looking forward to hearing from you and contributing.
Iam not sure someone else has already replied
but if you (or someone else) is looking for suggestions there are many
some ideas that come to my mind
as you mention encoder.
a current example would be the FFv1 encoder
there are for example 3 different ways to code LSBs. These are in
3 patches on this mailing list. These could be compared in terms of
speed and compression. Though likely each patch would only apply
cleanly to a git checkout from around that time.
If you are interrested in this, i can look at and provide exact
links to the patches
thx
[...]
--
Michael GnuPG fingerprint: 9FF2128B147EF6730BADF133611EC787040B0FAB
Those who would give up essential Liberty, to purchase a little
temporary Safety, deserve neither Liberty nor Safety -- Benjamin Franklin
[-- Attachment #1.2: signature.asc --]
[-- Type: application/pgp-signature, Size: 195 bytes --]
[-- Attachment #2: Type: text/plain, Size: 251 bytes --]
_______________________________________________
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-04-12 0:37 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-04-08 13:35 SUBHANGANI JHA
2025-04-12 0:37 ` Michael Niedermayer [this message]
2025-04-12 13:18 ` SUBHANGANI JHA
2025-04-16 14:00 ` 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=20250412003747.GG4991@pb2 \
--to=michael@niedermayer.cc \
--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