From: Paul B Mahol <onemda@gmail.com>
To: FFmpeg development discussions and patches <ffmpeg-devel@ffmpeg.org>
Subject: Re: [FFmpeg-devel] Too many project ideas in GSOC 2022 FFmpeg
Date: Thu, 3 Mar 2022 20:47:19 +0100
Message-ID: <CAPYw7P5iH65c7vyJEMMh87e71xs_qoCxPtsQUb=2Xpoi86PjzQ@mail.gmail.com> (raw)
In-Reply-To: <93cd3615-d7ae-92b3-b7ed-f33b64d6ece8@t-online.de>
On 3/1/22, Michael Koch <astroelectronic@t-online.de> wrote:
>> We have 0 project ideas on our gsoc 2022 page
>> well we have 2 now as i copied my two from last year
>> If you have an idea, please add it!
>
> Might it be possible to integrate LibRaw into FFmpeg?
> https://www.libraw.org/
>
> This could also solve the problem that import of DNG images doesn't work in
> FFmpeg.
Importing works fine, and mpv displays correct colors.
>
> Michael
>
> _______________________________________________
> 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".
prev parent reply other threads:[~2022-03-03 19:47 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-02-21 12:12 Michael Niedermayer
2022-02-21 16:59 ` Pierre-Anthony Lemieux
2022-02-21 18:24 ` Michael Niedermayer
2022-02-23 16:22 ` Michael Niedermayer
2022-02-23 17:07 ` Mark Gaiser
2022-03-01 7:46 ` Michael Koch
2022-03-01 8:09 ` Paul B Mahol
2022-03-01 17:49 ` Marvin Scholz
2022-03-02 11:46 ` Paul B Mahol
2022-03-01 15:17 ` Michael Niedermayer
2022-03-03 19:47 ` Paul B Mahol [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='CAPYw7P5iH65c7vyJEMMh87e71xs_qoCxPtsQUb=2Xpoi86PjzQ@mail.gmail.com' \
--to=onemda@gmail.com \
--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