-0800, jon morley wrote:
movenc.c |9 ++---
1 file changed, 6 insertions(+), 3 deletions(-)
6317011578bca8bf065f5bd4de2dfce803557e81
0001-libavformat-movenc.c-Correct-color-range-when-writin.patch
From 0097277471810ab1d9d737c64a57c2278a039153 Mon Sep 17 00:00:00 2001
From: Jon Morley
>From 0097277471810ab1d9d737c64a57c2278a039153 Mon Sep 17 00:00:00 2001
From: Jon Morley
Date: Tue, 27 Jan 2015 11:10:27 -0800
Subject: [PATCH] libavformat/movenc.c: Correct color range when writing DNxHD
atoms
The meaning of the color range values in the AVdn.ACLR atom was swapped.
This cha
e:
On Sat, Jan 24, 2015 at 07:40:38AM -0800, jon morley wrote:
Hi Clément,
Hi,
That is a good point! I am attaching an additional patch to remove those
cases even before entering the mod test loop.
Now the logic should look like this:
static int check_fps(int fps)
{
if (fps <=
ot find anywhere that
benefited from the explicit list the method currently used, but that
doesn't mean it isn't out there.
Thanks,
Jon
On 1/24/15 2:27 AM, Clément Bœsch wrote:
On Fri, Jan 23, 2015 at 08:48:37AM -0800, jon morley wrote:
Patch attached for consideration.
On 1/23/15
Patch attached for consideration.
On 1/23/15 8:03 AM, jon morley wrote:
Currently check_fps has the following logic:
static int check_fps(int fps)
{
int i;
static const int supported_fps[] = {24, 25, 30, 48, 50, 60};
for (i = 0; i < FF_ARRAY_ELEMS(supported_fps)
Currently check_fps has the following logic:
static int check_fps(int fps)
{
int i;
static const int supported_fps[] = {24, 25, 30, 48, 50, 60};
for (i = 0; i < FF_ARRAY_ELEMS(supported_fps); i++)
if (fps == supported_fps[i])
return 0;
return -1;
}
I am start
