> The specific code I'm referring to is at the end of colorspace.h where it
> looks like they're trying to encode RGB to BT.601.
>
> #define RGB_TO_Y(r1, g1, b1, shift)
> #define RGB_TO_U(r1, g1, b1, shift)
> #define RGB_TO_V(r1, g1, b1, shift)
A quick search over the ffmpeg codebase tells me th
rs
encode(255,128,0,601); //use 601 or 709 as last argument
}
-Original Message-
From: Michael Niedermayer
To: FFmpeg development discussions and patches
Sent: Wed, Jun 3, 2015 11:52 am
Subject: Re: [FFmpeg-devel] colorspace.h
On Tue, Jun 02, 2015 at 02:28:59AM -0400, Chris wrote:
>
ors
encode(255,128,0,709); //use 601 or 709 as last argument
}
==
-Original Message-
From: Michael Niedermayer
To: FFmpeg development discussions and patches
Sent: Wed, Jun 3, 2015 11:52 am
Subject: Re: [FFmpeg-devel] colorspace.h
On Tue, Jun 02, 2015 at 02:28:59AM -0400, Chris
gram will be written with both 601 and 709. It will be expandable to
other color spaces.
-Original Message-
From: Michael Niedermayer
To: FFmpeg development discussions and patches
Sent: Wed, Jun 3, 2015 11:52 am
Subject: Re: [FFmpeg-devel] colorspace.h
On Tue, Jun 02, 2015 at 02:28:59AM
m: Michael Niedermayer
To: FFmpeg development discussions and patches
Sent: Wed, Jun 3, 2015 11:52 am
Subject: Re: [FFmpeg-devel] colorspace.h
On Tue, Jun 02, 2015 at 02:28:59AM -0400, Chris wrote:
> Hello -
>
> I have
found what I believe to be some questionable code in colorspace.h.
On Tue, Jun 02, 2015 at 02:28:59AM -0400, Chris wrote:
> Hello -
>
> I have found what I believe to be some questionable code in colorspace.h. I
> have modified the code to what I believe is correct but am unable to compile
> ffmpeg myself on Windows to test my modifications, despite spending ma
Hello -
I have found what I believe to be some questionable code in colorspace.h. I
have modified the code to what I believe is correct but am unable to compile
ffmpeg myself on Windows to test my modifications, despite spending many hours
trying to do so and reading several how-to's.
We can d
