Git Inbox Mirror of the ffmpeg-devel mailing list - see https://ffmpeg.org/mailman/listinfo/ffmpeg-devel
 help / color / mirror / Atom feed
From: Vittorio Giovara <vittorio.giovara@gmail.com>
To: FFmpeg development discussions and patches <ffmpeg-devel@ffmpeg.org>
Cc: Leo Izen <leo.izen@gmail.com>
Subject: Re: [FFmpeg-devel] [PATCH v4 1/1] avutil/csp: create public API for colorspace structs
Date: Tue, 24 May 2022 17:28:17 +0200
Message-ID: <CABLWnS_gT9szG0vM0TK_+wtqGne+fK7GeoSdrkiSxhqBPpH=eg@mail.gmail.com> (raw)
In-Reply-To: <20220523210139.19480-2-leo.izen@gmail.com>

On Mon, May 23, 2022 at 11:02 PM Leo Izen <leo.izen@gmail.com> 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. It also converts those structs from
> double values to AVRational to make regression testing easier and
> more consistent
>

which places did you have in mind to use this api in avcodec and avformat?
also wouldn't callers be interested in accessory functions like
ff_matrix_invert_3x3 if they are dealing with color spaces?
-- 
Vittorio
_______________________________________________
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".

  parent reply	other threads:[~2022-05-24 15:28 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-05-23 21:01 [FFmpeg-devel] [PATCH v4 0/1] [WIP] avutil/csp changes Leo Izen
2022-05-23 21:01 ` [FFmpeg-devel] [PATCH v4 1/1] avutil/csp: create public API for colorspace structs Leo Izen
2022-05-24 15:10   ` Anton Khirnov
2022-05-24 15:28   ` Vittorio Giovara [this message]
2022-05-24 15:47     ` Leo Izen
2022-05-24 13:45 ` [FFmpeg-devel] [PATCH v4 0/1] [WIP] avutil/csp changes Michael Niedermayer

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='CABLWnS_gT9szG0vM0TK_+wtqGne+fK7GeoSdrkiSxhqBPpH=eg@mail.gmail.com' \
    --to=vittorio.giovara@gmail.com \
    --cc=ffmpeg-devel@ffmpeg.org \
    --cc=leo.izen@gmail.com \
    /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