From: "Александр Водянников via ffmpeg-devel" <ffmpeg-devel@ffmpeg.org>
To: "FFmpeg development discussions and patches" <ffmpeg-devel@ffmpeg.org>
Cc: "Александр Водянников" <aleksoid1978@mail.ru>
Subject: Re: [FFmpeg-devel] [PATCH 1/2] Add support d3d11va Intel Hevc Rext decoder.
Date: Mon, 26 Feb 2024 02:35:17 +0300
Message-ID: <1708904117.742258314@f554.i.mail.ru> (raw)
In-Reply-To: <a087150b-3d13-410d-ac2a-d9b054e3ec45@jkqxz.net>
I apologize for the previous letter, I forgot to translate)
Dear developers. I simply wrote a patch, tested its operation on Intel with Hevc Rext support by decoding on all possible HEVC formats - 420 12bit, 422 8/10/12bit, 444 8/10/12bit.
There is no particular desire to describe why exactly this or that way.
But it is now in full working order, and the correct AV_PIX_FMT_ + DXGI_FORMAT_ is registered in it,
and copying from the GPU works correctly.
You can compile and test it yourself and make sure that everything works correctly.
Right here:
(sps->intra_smoothing_disabled_flag << 5) | (sps->high_precision_offsets_enabled_flag << 5)
apparently yes, a typo, must be
sps->high_precision_offsets_enabled_flag << 6
--
Александр Водянников.
_______________________________________________
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:[~2024-02-25 23:35 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-02-25 2:22 Водянников А.В. via ffmpeg-devel
2024-02-25 10:36 ` Mark Thompson
2024-02-25 15:46 ` Hendrik Leppkes
2024-02-25 21:55 ` Александр Водянников via ffmpeg-devel
2024-02-25 23:35 ` Александр Водянников 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=1708904117.742258314@f554.i.mail.ru \
--to=ffmpeg-devel@ffmpeg.org \
--cc=aleksoid1978@mail.ru \
/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