From: Leo Izen <leo.izen@gmail.com>
To: FFmpeg Development <ffmpeg-devel@ffmpeg.org>
Subject: Re: [FFmpeg-devel] [PATCH v8 0/2] libjxl Colorspace Fixes
Date: Wed, 15 Jun 2022 10:31:04 -0400
Message-ID: <cb6100d2-1c2d-3ad4-7988-3cec6ce49fbb@gmail.com> (raw)
In-Reply-To: <acd40170-8430-0711-150c-3060d2270bee@gmail.com>
On 6/9/22 07:31, Leo Izen wrote:
> On 6/1/22 22:14, Leo Izen wrote:
>> Changes in v8:
>> - Use avutil/csp for both encoding and decoding
>> - Handle the non-XYB case with an attached ICC Profile on decoding
>> - clean up some code and segment it out to static functions
>>
>> Leo Izen (2):
>> avcodec/libjxldec: properly tag output colorspace
>> avcodec/libjxlenc: properly read input colorspace
>>
>> libavcodec/libjxldec.c | 142 +++++++++++++++++++++++++++++++++++---
>> libavcodec/libjxlenc.c | 153 +++++++++++++++++++++++++++++++++--------
>> 2 files changed, 256 insertions(+), 39 deletions(-)
>>
>
> I believe this should make it into 5.1 as it fixes a known bug and
> improves existing behavior.
>
> - Leo Izen (thebombzen)
Bumping again for review.
- 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".
next prev parent reply other threads:[~2022-06-15 14:31 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-06-02 2:14 Leo Izen
2022-06-02 2:14 ` [FFmpeg-devel] [PATCH v8 1/2] avcodec/libjxldec: properly tag output colorspace Leo Izen
2022-06-23 14:02 ` Anton Khirnov
2022-06-24 10:14 ` Niklas Haas
2022-06-02 2:14 ` [FFmpeg-devel] [PATCH v8 2/2] avcodec/libjxlenc: properly read input colorspace Leo Izen
2022-06-23 14:16 ` Anton Khirnov
2022-06-23 15:33 ` Leo Izen
2022-06-23 21:46 ` Niklas Haas
2022-06-09 11:31 ` [FFmpeg-devel] [PATCH v8 0/2] libjxl Colorspace Fixes Leo Izen
2022-06-15 14:31 ` Leo Izen [this message]
2022-06-22 16:28 ` Leo Izen
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=cb6100d2-1c2d-3ad4-7988-3cec6ce49fbb@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