From: "Ronald S. Bultje" <rsbultje@gmail.com>
To: FFmpeg development discussions and patches <ffmpeg-devel@ffmpeg.org>
Subject: Re: [FFmpeg-devel] [PATCH] avutil/csp: create public API for colorspace structs
Date: Sun, 15 May 2022 12:49:51 -0400
Message-ID: <CAEEMt2mSAMkPTn8b7q+bE6Tcv_-kA-=hHuOsbbaPo6e_v6=Vqg@mail.gmail.com> (raw)
In-Reply-To: <20220513212245.GN396728@pb2>
Hi,
On Fri, May 13, 2022 at 5:22 PM Michael Niedermayer <michael@niedermayer.cc>
wrote:
> On Fri, May 13, 2022 at 11:42:08AM -0400, Leo Izen wrote:
> > This commit moves some of the functionality from avfilter/colorspace
> > into avutil/csp and exposes it as a public API so it can be used by
> > libavcodec and/or libavformat.
> [...]
> > diff --git a/libavutil/csp.h b/libavutil/csp.h
> > new file mode 100644
> > index 0000000000..1bcde7ddd3
> > --- /dev/null
> > +++ b/libavutil/csp.h
> > @@ -0,0 +1,49 @@
> > +/*
> > + * Copyright (c) 2016 Ronald S. Bultje <rsbultje@gmail.com>
> > + * This file is part of FFmpeg.
> > + *
> > + * FFmpeg is free software; you can redistribute it and/or
> > + * modify it under the terms of the GNU Lesser General Public
> > + * License as published by the Free Software Foundation; either
> > + * version 2.1 of the License, or (at your option) any later version.
> > + *
> > + * FFmpeg is distributed in the hope that it will be useful,
> > + * but WITHOUT ANY WARRANTY; without even the implied warranty of
> > + * MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the GNU
> > + * Lesser General Public License for more details.
> > + *
> > + * You should have received a copy of the GNU Lesser General Public
> > + * License along with FFmpeg; if not, write to the Free Software
> > + * Foundation, Inc., 51 Franklin Street, Fifth Floor, Boston, MA
> 02110-1301 USA
> > + */
> > +
> > +#ifndef AVUTIL_CSP_H
> > +#define AVUTIL_CSP_H
> > +
> > +#include "libavutil/frame.h"
> > +#include "libavutil/pixfmt.h"
> > +
> > +struct LumaCoefficients {
> > + double cr, cg, cb;
> > +};
> > +
> > +struct PrimaryCoefficients {
> > + double xr, yr, xg, yg, xb, yb;
> > +};
> > +
> > +struct WhitepointCoefficients {
> > + double xw, yw;
> > +};
>
> I think we should avoid floating point so as to ensure reproduceable
> results and simplify regerssion testing
>
To explain: when I designed this stuff, I chose to keep them in float so
that we can use the literal values from the specs, which are themselves in
floating point. That would not be possible anymore, and would therefore
make it slightly harder to read for a casual observer.
(Otherwise no opinion, I'm typically used to fixed-point rather than
floating-point myself also.)
Ronald
_______________________________________________
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-05-15 16:50 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-05-13 15:42 Leo Izen
2022-05-13 19:14 ` Ronald S. Bultje
2022-05-13 19:18 ` James Almer
2022-05-14 2:43 ` Leo Izen
2022-05-13 21:22 ` Michael Niedermayer
2022-05-14 2:41 ` Leo Izen
2022-05-14 12:15 ` Niklas Haas
2022-05-15 16:49 ` Ronald S. Bultje [this message]
2022-05-15 18:10 ` Niklas Haas
2022-05-15 18:55 ` Michael Niedermayer
2022-05-15 19:19 ` Michael Niedermayer
2022-05-15 16:32 ` Andreas Rheinhardt
2022-05-16 14:45 ` Leo Izen
2022-05-18 12:21 ` Niklas Haas
2022-05-18 12:29 ` 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='CAEEMt2mSAMkPTn8b7q+bE6Tcv_-kA-=hHuOsbbaPo6e_v6=Vqg@mail.gmail.com' \
--to=rsbultje@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