Git Inbox Mirror of the ffmpeg-devel mailing list - see https://ffmpeg.org/mailman/listinfo/ffmpeg-devel
 help / color / mirror / Atom feed
From: Niklas Haas <ffmpeg@haasn.xyz>
To: ffmpeg-devel@ffmpeg.org
Subject: [FFmpeg-devel] [RFC] [PATCH 0/7] Towards YUVJ removal, v2
Date: Wed, 11 Oct 2023 16:55:34 +0200
Message-ID: <20231011150848.117897-1-ffmpeg@haasn.xyz> (raw)

A follow-up to my previous post (almost a year ago) about YUVJ removal.
This patchset does not add full filter colorspace negotiation - rather,
we add metadata only to AVCodec, with a warning being printed if
incorrect frames are sent. fftools/ffmpeg_filter.c gained an explicit
auto-conversion case, which is enough to pass FATE, and not regress
current use cases where automatic YUVJ<->YUVJ conversion is happening.

The major caveats here are:

1. Handling in fftools is great, but not ideal for API users who want
   the filter graph API to handle all auto-conversions. This would
   require also adding support for color ranges etc. to the filter
   format negotiation API, which would be a major undertaking, much
   larger than this series in scope. It would also build on top of the
   basis established out by this series, since the capabilities
   advertise by the AVCodec would naturally plug in to the downstream
   end of the filter graph.

2. For symmetry, I added *all* of the colorspace metadata fields, rather
   than just color range. I don't expand their use in this series, but
   it's quite low-hanging fruit at this point to add a list of supported
   primaries etc. to whatever codecs need it (for example, VP8 can only
   do BT.601 primaries, HEVC can only do certain chroma locations,
   etc.).

   While this is more future-proof, libswscale can't handle these
   conversions at the moment. So we insert zscale instead, if available.
   (And otherwise, we would just continue to generate an error)

Probably not in the final form that will be merged, but I wanted to
gather feedback on this approach.

_______________________________________________
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".

             reply	other threads:[~2023-10-11 15:09 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-10-11 14:55 Niklas Haas [this message]
2023-10-11 14:55 ` [FFmpeg-devel] [PATCH 1/7] avcodec: add extended AVCodec color metadata Niklas Haas
2023-10-11 14:55 ` [FFmpeg-devel] [PATCH 2/7] lavc/options: properly init AVCodecContext.colorspace Niklas Haas
2023-10-11 15:44   ` Andreas Rheinhardt
2023-10-11 14:55 ` [FFmpeg-devel] [PATCH 3/7] fftools/ffmpeg_filter: auto-insert csp conversion filter Niklas Haas
2023-10-11 14:55 ` [FFmpeg-devel] [PATCH 4/7] fftools/ffmpeg_filter: auto-insert zscale filter Niklas Haas
2023-10-11 16:55   ` Michael Niedermayer
2023-10-11 17:34     ` Niklas Haas
2023-10-11 14:55 ` [FFmpeg-devel] [PATCH 5/7] avcodec/encode: enforce AVCodec capabilities at encode time Niklas Haas
2023-10-11 14:55 ` [FFmpeg-devel] [PATCH 6/7] lavc: set color_ranges for YUVJ-only codecs Niklas Haas
2023-10-11 14:55 ` [FFmpeg-devel] [PATCH 7/7] lavfi/lavu/lavc: remove YUVJ pixel formats 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=20231011150848.117897-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