From: James Almer <jamrial@gmail.com>
To: ffmpeg-devel@ffmpeg.org
Subject: Re: [FFmpeg-devel] [PATCH v4 3/3] avcodec/hevc: Add alpha layer support
Date: Thu, 6 Feb 2025 11:32:13 -0300
Message-ID: <a8b78807-f82a-4835-b64d-04273f2a1804@gmail.com> (raw)
In-Reply-To: <tencent_FA5B20354F81AC347F3EBB56AD9D0CE0D409@qq.com>
[-- Attachment #1.1.1: Type: text/plain, Size: 1033 bytes --]
On 2/6/2025 11:06 AM, Zhao Zhili wrote:
>
>
>> On Feb 6, 2025, at 21:26, James Almer <jamrial@gmail.com> wrote:
>>
>> On 2/6/2025 12:50 AM, Zhao Zhili wrote:
>>> From: Zhao Zhili <zhilizhao@tencent.com>
>>> Signed-off-by: Zhao Zhili <zhilizhao@tencent.com>
>>> ---
>>> libavcodec/hevc/hevcdec.c | 72 ++++++++++++++++++++++++++++++++++++++-
>>> libavcodec/hevc/hevcdec.h | 2 ++
>>> libavcodec/hevc/refs.c | 11 +++++-
>>> 3 files changed, 83 insertions(+), 2 deletions(-)
>>
>> Can you please share the sample from the other day without requiring to request for access to your google drive?
>
> Sorry I have modified the permission but forgot to reply.
>
> https://drive.google.com/file/d/1SK6gnMNlWODeTySpetNAKgNeqt69DQDz/view?usp=sharing
Thanks. That sample however doesn't really showcase the alpha layer
doing anything. Can't you generate a sample with videotoolbox out of
some apng, webp or similar source with alpha where the transparency is
noticeable? The FATE suite has a couple.
[-- Attachment #1.2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 495 bytes --]
[-- Attachment #2: 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 prev parent reply other threads:[~2025-02-06 14:32 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-02-06 3:50 Zhao Zhili
2025-02-06 13:26 ` James Almer
2025-02-06 14:06 ` Zhao Zhili
2025-02-06 14:32 ` James Almer [this message]
2025-02-06 14:36 ` James Almer
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=a8b78807-f82a-4835-b64d-04273f2a1804@gmail.com \
--to=jamrial@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