From: James Zern <jzern-at-google.com@ffmpeg.org> To: FFmpeg development discussions and patches <ffmpeg-devel@ffmpeg.org> Subject: Re: [FFmpeg-devel] [PATCH v1 2/2] lavc/libvpxenc: support creating full range output Date: Sat, 17 Jun 2023 17:03:17 -0700 Message-ID: <CABWgkXLnES9sDyp1NsZTkbj+vs8pEjdMUpSmrXz5qzyNdOKrfg@mail.gmail.com> (raw) In-Reply-To: <20230617081108.10051-2-thilo.borgmann@mail.de> On Sat, Jun 17, 2023 at 1:11 AM Thilo Borgmann <thilo.borgmann@mail.de> wrote: > > suggested-by: ffmpeg@meta.com > --- > libavcodec/libvpxenc.c | 12 ++++++++++++ > 1 file changed, 12 insertions(+) > Looks like there's some discussion on the parent patch about the correctness of adding this. This wrapper does set the color range to full with AVCOL_RANGE_JPEG. > diff --git a/libavcodec/libvpxenc.c b/libavcodec/libvpxenc.c > index 8833df2d68..6e8a0d07c3 100644 > --- a/libavcodec/libvpxenc.c > +++ b/libavcodec/libvpxenc.c > @@ -799,21 +799,25 @@ static int set_pix_fmt(AVCodecContext *avctx, vpx_codec_caps_t codec_caps, > enccfg->g_bit_depth = enccfg->g_input_bit_depth = desc->comp[0].depth; > switch (avctx->pix_fmt) { > case AV_PIX_FMT_YUV420P: > + case AV_PIX_FMT_YUVJ420P: > case AV_PIX_FMT_YUVA420P: > enccfg->g_profile = 0; > *img_fmt = VPX_IMG_FMT_I420; > return 0; > case AV_PIX_FMT_YUV422P: > + case AV_PIX_FMT_YUVJ422P: > enccfg->g_profile = 1; > *img_fmt = VPX_IMG_FMT_I422; > return 0; > case AV_PIX_FMT_YUV440P: > + case AV_PIX_FMT_YUVJ440P: > enccfg->g_profile = 1; > *img_fmt = VPX_IMG_FMT_I440; > return 0; > case AV_PIX_FMT_GBRP: > ctx->vpx_cs = VPX_CS_SRGB; > case AV_PIX_FMT_YUV444P: > + case AV_PIX_FMT_YUVJ444P: > enccfg->g_profile = 1; > *img_fmt = VPX_IMG_FMT_I444; > return 0; > @@ -2054,20 +2058,28 @@ static av_cold int vp9_init(AVCodecContext *avctx) > > static const enum AVPixelFormat vp9_pix_fmts_highcol[] = { > AV_PIX_FMT_YUV420P, > + AV_PIX_FMT_YUVJ420P, > AV_PIX_FMT_YUVA420P, > AV_PIX_FMT_YUV422P, > + AV_PIX_FMT_YUVJ422P, > AV_PIX_FMT_YUV440P, > + AV_PIX_FMT_YUVJ440P, > AV_PIX_FMT_YUV444P, > + AV_PIX_FMT_YUVJ444P, > AV_PIX_FMT_GBRP, > AV_PIX_FMT_NONE > }; > > static const enum AVPixelFormat vp9_pix_fmts_highbd[] = { > AV_PIX_FMT_YUV420P, > + AV_PIX_FMT_YUVJ420P, > AV_PIX_FMT_YUVA420P, > AV_PIX_FMT_YUV422P, > + AV_PIX_FMT_YUVJ422P, > AV_PIX_FMT_YUV440P, > + AV_PIX_FMT_YUVJ440P, > AV_PIX_FMT_YUV444P, > + AV_PIX_FMT_YUVJ444P, > AV_PIX_FMT_YUV420P10, > AV_PIX_FMT_YUV422P10, > AV_PIX_FMT_YUV440P10, > -- > 2.37.1 (Apple Git-137.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". _______________________________________________ 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:[~2023-06-18 0:03 UTC|newest] Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top 2023-06-17 8:11 [FFmpeg-devel] [PATCH v1 1/2] lavc/vp9: set yuvj pixel format for full range decode Thilo Borgmann 2023-06-17 8:11 ` [FFmpeg-devel] [PATCH v1 2/2] lavc/libvpxenc: support creating full range output Thilo Borgmann 2023-06-18 0:03 ` James Zern [this message] 2023-06-18 7:31 ` Thilo Borgmann 2023-06-17 11:40 ` [FFmpeg-devel] [PATCH v1 1/2] lavc/vp9: set yuvj pixel format for full range decode Paul B Mahol 2023-06-17 11:46 ` Thilo Borgmann 2023-06-17 11:53 ` Paul B Mahol 2023-06-17 12:00 ` Thilo Borgmann 2023-06-17 14:02 ` Leo Izen 2023-06-17 14:26 ` Thilo Borgmann 2023-06-17 14:48 ` Leo Izen 2023-06-18 21:21 ` Leo Izen 2023-06-19 8:14 ` Thilo Borgmann 2023-06-19 15:35 ` Leo Izen
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=CABWgkXLnES9sDyp1NsZTkbj+vs8pEjdMUpSmrXz5qzyNdOKrfg@mail.gmail.com \ --to=jzern-at-google.com@ffmpeg.org \ --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