From: Leo Izen <leo.izen@gmail.com>
To: FFmpeg Development <ffmpeg-devel@ffmpeg.org>
Subject: Re: [FFmpeg-devel] [PATCH v2 0/3] Proper color support in PNG
Date: Wed, 25 Jan 2023 08:40:10 -0500
Message-ID: <b0c02561-d865-0de0-87ef-b45d4ef4e031@gmail.com> (raw)
In-Reply-To: <583976aa-fae0-d1fb-9a7e-ca4ea02f7d9d@gmail.com>
On 1/24/23 16:25, Leo Izen wrote:
> On 1/24/23 09:02, Leo Izen wrote:
>> On 1/17/23 13:50, Leo Izen wrote:
>>> This series of patches fixes our incorrect cHRM handling
>>> in PNGs and properly supports sRGB and cICP chunks in PNGs
>>> as well.
>>>
>>> Leo Izen (3):
>>> avcodec/png: use libavutil/csp.h for cHRM chunks
>>> avcodec/pngdec: support decoding sRGB chunks
>>> avcodec/png: support cICP chunks
>>>
>>> libavcodec/pngdec.c | 87 +++++++++++++++++++++++++++---------
>>> libavcodec/pngenc.c | 61 ++++++++++---------------
>>> tests/ref/fate/png-icc | 2 +-
>>> tests/ref/fate/png-side-data | 13 +-----
>>> 4 files changed, 92 insertions(+), 71 deletions(-)
>>>
>>
>> Bumping for review, thanks.
>>
>> -Leo Izen (thebombzen)
>
> Got a LGTM from haasn on IRC, will push soon-ish
>
> - Leo Izen (thebombzen)
Pushed.
- Leo Izen (thebombzen)
_______________________________________________
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:[~2023-01-25 13:40 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-01-17 18:50 Leo Izen
2023-01-17 18:50 ` [FFmpeg-devel] [PATCH v2 1/3] avcodec/png: use libavutil/csp.h for cHRM chunks Leo Izen
2023-01-17 18:50 ` [FFmpeg-devel] [PATCH v2 2/3] avcodec/pngdec: support decoding sRGB chunks Leo Izen
2023-01-17 18:50 ` [FFmpeg-devel] [PATCH v2 3/3] avcodec/png: support cICP chunks Leo Izen
2023-01-24 14:02 ` [FFmpeg-devel] [PATCH v2 0/3] Proper color support in PNG Leo Izen
2023-01-24 21:25 ` Leo Izen
2023-01-25 13:40 ` Leo Izen [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=b0c02561-d865-0de0-87ef-b45d4ef4e031@gmail.com \
--to=leo.izen@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