From: Paul B Mahol <onemda@gmail.com>
To: FFmpeg development discussions and patches <ffmpeg-devel@ffmpeg.org>
Subject: Re: [FFmpeg-devel] [PATCH v1 1/2] lavc/vp9: set yuvj pixel format for full range decode
Date: Sat, 17 Jun 2023 13:53:43 +0200
Message-ID: <CAPYw7P4ygc4bPG8VVCA=aoKAGyKfwXzGeY1bntGbZLK94s1eNg@mail.gmail.com> (raw)
In-Reply-To: <3dd7a821-51b9-5131-1211-083f43729970@mail.de>
On Sat, Jun 17, 2023 at 1:47 PM Thilo Borgmann <thilo.borgmann@mail.de>
wrote:
> Am 17.06.23 um 13:40 schrieb Paul B Mahol:
> > NAK, there is color_range that should not be ignored.
>
> In patch 1/2 color_range is used in the condition for the switch.
>
> if (avctx->color_range == AVCOL_RANGE_JPEG) {
>
> Or I don't understand. What shall be done with color_range?
>
Actually used, and all YUVJ uses finally removed from codebase.
>
>
> > Fix finally scale filter.
>
> Hmm? Where what who?
>
Perhaps just frame->color_range needs to be set?
>
> -Thilo
>
> _______________________________________________
> 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-17 11:54 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-06-17 8:11 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
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 [this message]
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='CAPYw7P4ygc4bPG8VVCA=aoKAGyKfwXzGeY1bntGbZLK94s1eNg@mail.gmail.com' \
--to=onemda@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