From: ff--- via ffmpeg-devel <ffmpeg-devel@ffmpeg.org>
To: FFmpeg development discussions and patches <ffmpeg-devel@ffmpeg.org>
Cc: Noah Johannessen <njohannessen@tamu.edu>, ff@hawaiiantel.net
Subject: [FFmpeg-devel] Re: Quick question from a CS student at TAMU
Date: Sat, 24 Jan 2026 08:43:25 -0800
Message-ID: <e43f49cdd91ee6b6a5a472954acc76c7@hawaiiantel.net> (raw)
In-Reply-To: <CAAKa-rzxw_2o61=e66MPS-5U=zUQ5qJFK-wAA82j_wfv9KfAjQ@mail.gmail.com>
On 2026-01-22 13:30, Noah Johannessen via ffmpeg-devel wrote:
> Howdy!
>
> I hope you don’t mind the cold outreach. I’m a CS student at Texas A&M
> who’s been following some of the work coming out of the GSoC ecosystem,
> and
> your involvement caught my eye.
>
> I’m exploring a small, student-led project this spring. As part of
> that,
> I’ve been reaching out to a few folks whose judgment I respect to get a
> sense for what kinds of problems are actually useful to work on.
>
> In particular, I was curious whether you’d ever be open to students
> taking
> on a well scoped project aligned with your work. Even a quick gut check
> on
> whether that’s something you ever consider would be super helpful.
Hi,
yes, the ffmpeg project welcomes all. anyone and everyone who wants to
dip their toes into the vast world of video technology, we're happy to
have the help.
although most people working on our project are volunteers. you may
find that we arent very organized or have a ton of free time to help
people find things to work on.
what kind of project are you thinking about? audio and video filtering?
maybe reverse engineering some old codecs so that ffmpeg can decode it?
for these codecs, the first version of the codec is supported, but
version 2 of the codec is not supported yet:
https://wiki.multimedia.cx/index.php/Motion_Pixels
or
https://wiki.multimedia.cx/index.php/Viv2
there are plenty of things to work on. finding something interesting
is the hard part!
-compn
compn@ffmpeg.org
_______________________________________________
ffmpeg-devel mailing list -- ffmpeg-devel@ffmpeg.org
To unsubscribe send an email to ffmpeg-devel-leave@ffmpeg.org
prev parent reply other threads:[~2026-01-24 16:44 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <e860881014.9a9@mailsuite.com>
2026-01-22 21:30 ` [FFmpeg-devel] " Noah Johannessen via ffmpeg-devel
2026-01-24 16:42 ` [FFmpeg-devel] " Kieran Kunhya via ffmpeg-devel
2026-01-24 16:43 ` ff--- via ffmpeg-devel [this message]
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=e43f49cdd91ee6b6a5a472954acc76c7@hawaiiantel.net \
--to=ffmpeg-devel@ffmpeg.org \
--cc=ff@hawaiiantel.net \
--cc=njohannessen@tamu.edu \
/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