From: Niklas Haas <ffmpeg@haasn.xyz>
To: ffmpeg-devel@ffmpeg.org
Subject: [FFmpeg-devel] [PATCH v4 0/7] ICC profile support in avcodec
Date: Thu, 28 Jul 2022 16:49:55 +0200
Message-ID: <20220728145002.102600-1-ffmpeg@haasn.xyz> (raw)
This tidies up the previous patchset slightly and adds the necessary
user-facing bits to make it actually usable, plus tests.
Will merge this soon since there was no additional feedback on v3.
Changes in v4:
- add the "icc_profiles" option to "flags2", and document it
- fix the corresponding check in avcodec/decode.c
- add FATE test for the new functionality
Changes in v3:
- switch from `int icc_profiles` to a new AV_CODEC_FLAG2 to avoid ABI
break
- rebased onto master and fixed merge conflicts
Changes in v2:
- remove unnecessary import
- fixed assignment-instead-of-equality
- fixed #ifdef -> #if
_______________________________________________
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 reply other threads:[~2022-07-28 14:50 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-07-28 14:49 Niklas Haas [this message]
2022-07-28 14:49 ` [FFmpeg-devel] [PATCH v4 1/7] fflcms2: move to libavcodec Niklas Haas
2022-07-28 14:49 ` [FFmpeg-devel] [PATCH v4 2/7] avcodec/codec_internal: add cap for ICC profile support Niklas Haas
2022-07-28 14:49 ` [FFmpeg-devel] [PATCH v4 3/7] avcodec: add API for automatic handling of icc profiles Niklas Haas
2022-07-28 14:49 ` [FFmpeg-devel] [PATCH v4 4/7] avcodec: add common fflcms2 boilerplate Niklas Haas
2022-07-28 14:50 ` [FFmpeg-devel] [PATCH v4 5/7] avcodec/decode: parse ICC profiles Niklas Haas
2022-07-28 14:50 ` [FFmpeg-devel] [PATCH v4 6/7] avcodec/encode:: generate " Niklas Haas
2022-07-28 14:50 ` [FFmpeg-devel] [PATCH v4 7/7] fate/png: add test for ICC profile parsing Niklas Haas
2022-07-30 9:59 ` [FFmpeg-devel] [PATCH v4 0/7] ICC profile support in avcodec Niklas Haas
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=20220728145002.102600-1-ffmpeg@haasn.xyz \
--to=ffmpeg@haasn.xyz \
--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