From: Wu Jianhua <toqsxw@outlook.com>
To: FFmpeg development discussions and patches <ffmpeg-devel@ffmpeg.org>
Subject: [FFmpeg-devel] [PATCH v2] avcodec: add D3D12VA hardware accelerated H264, HEVC, VP9, and AV1 decoding
Date: Fri, 23 Dec 2022 18:01:01 +0000
Message-ID: <OSZP286MB217328A12BC439F5BB31897DCAE99@OSZP286MB2173.JPNP286.PROD.OUTLOOK.COM> (raw)
In-Reply-To: <OSZP286MB217380EBFB2351E3B8B54E25CAE99@OSZP286MB2173.JPNP286.PROD.OUTLOOK.COM>
[-- Attachment #1: Type: text/plain, Size: 115 bytes --]
[PATCH v2] avcodec: add D3D12VA hardware accelerated H264, HEVC, VP9, and AV1 decoding
Patches attached.
[-- Attachment #2: 0004-avcodec-add-D3D12VA-hardware-accelerated-VP9-decodin.patch --]
[-- Type: application/octet-stream, Size: 15188 bytes --]
[-- Attachment #3: 0005-avcodec-add-D3D12VA-hardware-accelerated-AV1-decodin.patch --]
[-- Type: application/octet-stream, Size: 24714 bytes --]
[-- Attachment #4: 0006-Changelog-add-D3D12VA-hardware-accelerated-H264-HEVC.patch --]
[-- Type: application/octet-stream, Size: 1215 bytes --]
[-- Attachment #5: 0001-libavutil-add-hwcontext_d3d12va-and-AV_PIX_FMT_D3D12.patch --]
[-- Type: application/octet-stream, Size: 40484 bytes --]
[-- Attachment #6: 0002-avcodec-add-D3D12VA-hardware-accelerated-H264-decodi.patch --]
[-- Type: application/octet-stream, Size: 45738 bytes --]
[-- Attachment #7: 0003-avcodec-add-D3D12VA-hardware-accelerated-HEVC-decodi.patch --]
[-- Type: application/octet-stream, Size: 22298 bytes --]
[-- Attachment #8: 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 parent reply other threads:[~2022-12-23 18:01 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <OSZP286MB217380EBFB2351E3B8B54E25CAE99@OSZP286MB2173.JPNP286.PROD.OUTLOOK.COM>
2022-12-23 18:01 ` Wu Jianhua [this message]
2023-02-28 14:50 ` Wu, Tong1
2023-04-11 15:36 ` Wu Jianhua
2023-03-01 15:55 ` Hendrik Leppkes
2023-04-11 16:41 ` Wu Jianhua
2023-04-11 17:28 ` Hendrik Leppkes
2023-04-11 19:03 ` Wu Jianhua
2023-03-01 15:52 Anton Khirnov
2023-04-11 17:03 ` Wu Jianhua
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=OSZP286MB217328A12BC439F5BB31897DCAE99@OSZP286MB2173.JPNP286.PROD.OUTLOOK.COM \
--to=toqsxw@outlook.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