From: Nuo Mi <nuomi2021@gmail.com>
To: FFmpeg development discussions and patches <ffmpeg-devel@ffmpeg.org>
Subject: [FFmpeg-devel] Let us review and collebrate on vvc native decoder.
Date: Sat, 14 Jan 2023 21:13:58 +0800
Message-ID: <CAFXK13cG-==g4WEzJr6TfZgdpV93D6uW4H30aaB+PqgGF=EzkA@mail.gmail.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 718 bytes --]
Hi Experts:
I am happy to send out the first draft of vvc decoder.
It's not ready for upstream yet, but it's a good base ground for review and
future improvement.
It has the following features:
* C only
+ Fast. On a 4 cores laptop, it can get 30~35+ fps for 10bits 1080P.
+ Support traditional features I, P B frames, 8/10 bits, chroma 400,420,
422, and 444,
+ Support VVC new tools like MIP, CCLM, AFFINE, GPM, DMVR, PROF, BDOF,
LMCS, ALF
- Not support RPR, PCM, IBC, PALETTE, and other minor features yet.
Please help review the attached patch and provide your valuable comment.
I also created a GitHub repo https://github.com/ffvvc/FFmpeg to
collaborate. Any improvement or issue report is welcomed.
Thank you.
[-- Attachment #2: 0001-avcodec-add-vvc-decoder.patch --]
[-- Type: application/octet-stream, Size: 1258332 bytes --]
[-- Attachment #3: 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 reply other threads:[~2023-01-26 12:16 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-01-14 13:13 Nuo Mi [this message]
2023-01-14 13:32 ` Nuo Mi
2023-01-14 13:53 ` Paul B Mahol
2023-01-14 14:12 ` Nuo Mi
2023-01-14 14:28 ` Ronald S. Bultje
2023-01-14 15:15 ` Nuo Mi
2023-01-14 15:52 ` Ronald S. Bultje
2023-01-15 9:08 ` Nuo Mi
2023-02-01 14:02 ` Nuo Mi
2023-01-26 12:23 ` Thilo Borgmann
2023-01-26 13:35 ` Nuo Mi
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='CAFXK13cG-==g4WEzJr6TfZgdpV93D6uW4H30aaB+PqgGF=EzkA@mail.gmail.com' \
--to=nuomi2021@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