From: Leo Izen <leo.izen@gmail.com>
To: ffmpeg-devel@ffmpeg.org
Cc: Leo Izen <leo.izen@gmail.com>
Subject: [FFmpeg-devel] [PATCH v7 0/1] avutil/csp: create public API for colorspace structs
Date: Sat, 28 May 2022 09:30:35 -0400
Message-ID: <20220528133036.33914-1-leo.izen@gmail.com> (raw)
Changes in v7:
- remove #define AVUTIL_CSP_DENOM, a.r.b. Andreas R and Ronald B
Changes in v6:
- Reordered avutil/csp.h functions to be in alphabetical order, as requested
by Lynne on IRC (which also matches the order they occur in csp.c)
- Clarified that RGB->YUV matrix works for similar ones too e.g. YCoCg
Changes in v5:
- Unmark as [WIP], ready for review and merging
- rename public functions to namespace them via av_csp_,
as requested by Anton K
- documented public API using Doxygen comments
- remove abs() from denominator in abs_sub_q, assuming denom is positive,
as requested by Andreas R
Leo Izen (1):
avutil/csp: create public API for colorspace structs
libavfilter/colorspace.c | 143 ++++++++----------------------------
libavfilter/colorspace.h | 31 +-------
libavfilter/fflcms2.c | 33 +++++----
libavfilter/fflcms2.h | 4 +-
libavfilter/vf_colorspace.c | 37 +++++-----
libavfilter/vf_iccdetect.c | 5 +-
libavfilter/vf_tonemap.c | 17 +----
libavutil/Makefile | 2 +
libavutil/csp.c | 128 ++++++++++++++++++++++++++++++++
libavutil/csp.h | 106 ++++++++++++++++++++++++++
libavutil/version.h | 2 +-
11 files changed, 317 insertions(+), 191 deletions(-)
create mode 100644 libavutil/csp.c
create mode 100644 libavutil/csp.h
--
2.36.1
_______________________________________________
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-05-28 13:30 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-05-28 13:30 Leo Izen [this message]
2022-05-28 13:30 ` [FFmpeg-devel] [PATCH v7 1/1] " Leo Izen
2022-05-31 14:26 ` Ronald S. Bultje
2022-06-01 18:31 ` Ronald S. Bultje
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=20220528133036.33914-1-leo.izen@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