On Fri, 9 Dec 2022, Niklas Haas wrote:
So, as was discussed at the last meeting, we should move towards
removing YUVJ.
Libswscale still does have cases where it doesn't work correctly, for some
conversions, unless differences in range is signalled with the YUVJ pixel
formats (this, despite t
Niklas Haas (12022-12-13):
> So, the biggest roadblock I see with regards to making color range etc.
> part of filter negotiation is that, currently, color range (and
> colorspace and so on) are part of AVFrame, which can (in theory and
> possibly also in practice) change suddenly mid-stream.
That
On Fri, 09 Dec 2022 17:50:11 +0100 Michael Niedermayer
wrote:
> On Fri, Dec 09, 2022 at 12:49:41PM +0100, Niklas Haas wrote:
> > So, as was discussed at the last meeting, we should move towards
> > removing YUVJ. I want to gather feedback on what appears to be to the
> > major hurdle, and possibl
On Fri, Dec 09, 2022 at 12:49:41PM +0100, Niklas Haas wrote:
> So, as was discussed at the last meeting, we should move towards
> removing YUVJ. I want to gather feedback on what appears to be to the
> major hurdle, and possible ways to solve it.
>
> The basic major issue is how to handle the case
On Fri, Dec 9, 2022 at 1:45 PM Niklas Haas wrote:
> Oh, you are right. So that presents an alternative to 4 - rather than an
> encoder flag, we can tie the auto-conversion in fftools to be tied to
> the strict_std_compliance check.
>
> I will try implementing this approach, it may be the best com
On Fri, Dec 9, 2022 at 12:49 PM Niklas Haas wrote:
>
> So, as was discussed at the last meeting, we should move towards
> removing YUVJ. I want to gather feedback on what appears to be to the
> major hurdle, and possible ways to solve it.
>
> The basic major issue is how to handle the case of comb
On 12/9/22, Niklas Haas wrote:
> On Fri, 09 Dec 2022 13:10:02 +0100 Andreas Rheinhardt
> wrote:
>> This is incorrect: Here are the pixel formats advertised by the mjpeg
>> encoder:
>>
>> .p.pix_fmts = (const enum AVPixelFormat[]) {
>> AV_PIX_FMT_YUVJ420P, AV_PIX_FMT_YUVJ422P, AV_P
On Fri, 09 Dec 2022 13:10:02 +0100 Andreas Rheinhardt
wrote:
> This is incorrect: Here are the pixel formats advertised by the mjpeg
> encoder:
>
> .p.pix_fmts = (const enum AVPixelFormat[]) {
> AV_PIX_FMT_YUVJ420P, AV_PIX_FMT_YUVJ422P, AV_PIX_FMT_YUVJ444P,
> AV_PIX_FMT_Y
3. :)
On Fri, 9 Dec 2022, at 12:49, Niklas Haas wrote:
> So, as was discussed at the last meeting, we should move towards
> removing YUVJ. I want to gather feedback on what appears to be to the
> major hurdle, and possible ways to solve it.
>
> The basic major issue is how to handle the case of co
So, as was discussed at the last meeting, we should move towards
removing YUVJ. I want to gather feedback on what appears to be to the
major hurdle, and possible ways to solve it.
The basic major issue is how to handle the case of combining limited
range input with an encoder for a format that onl
10 matches
Mail list logo
