On Thu, Feb 01, 2018 at 01:51:17PM +0100, Jerome Martinez wrote:
> On 05/01/2018 11:18, Jerome Martinez wrote:
> >1 year without RGB48 related patches, tested by a couple of users, tested
> >with a FFV1 conformance checker, I suggest that FFV1 RGB48 support in
> >FFmpeg does not mandate anymore the
On 05/01/2018 11:18, Jerome Martinez wrote:
1 year without RGB48 related patches, tested by a couple of users,
tested with a FFV1 conformance checker, I suggest that FFV1 RGB48
support in FFmpeg does not mandate anymore the user to add " -strict
experimental" on the command line during encoding
On Fri, Jan 05, 2018 at 10:26:42PM +0100, Jerome Martinez wrote:
> On 05/01/2018 16:14, Tobias Rapp wrote:
> >On 05.01.2018 11:18, Jerome Martinez wrote:
> >>0001-FFV1-make-RGB48-support-as-non-experimental.patch
> >>
> >>From cd1bfe68a1a809700f25e593ac21ca3876d265ad Mon Sep 17 00:00:00 2001
> >>Fr
On 06/01/2018 23:21, Michael Niedermayer wrote:
On Sat, Jan 06, 2018 at 04:54:18PM +0100, Jerome Martinez wrote:
On 06/01/2018 02:05, Michael Niedermayer wrote:
ffv1enc.c |4
1 file changed, 4 deletions(-)
acfc60c913b311b148f2eeef2d2d6ea9e37afcf7
0001-avcodec-ffv1enc-mark-RGB48-su
On Sat, Jan 06, 2018 at 05:01:42PM +0100, Reto Kromer wrote:
> Michael Niedermayer wrote:
>
> >>Resulting bitstream was tested with a conformance checker
> >>using the last draft of FFV1 specifications.
> >
> >But has the way this is stored been optimized ?
> >
> >Once its marked as non exerimenta
On Sat, Jan 06, 2018 at 04:54:18PM +0100, Jerome Martinez wrote:
> On 06/01/2018 02:05, Michael Niedermayer wrote:
> >
> >> ffv1enc.c |4
> >> 1 file changed, 4 deletions(-)
> >>acfc60c913b311b148f2eeef2d2d6ea9e37afcf7
> >>0001-avcodec-ffv1enc-mark-RGB48-support-as-non-experiment.patch
Michael Niedermayer wrote:
>>Resulting bitstream was tested with a conformance checker
>>using the last draft of FFV1 specifications.
>
>But has the way this is stored been optimized ?
>
>Once its marked as non exerimental all future decoders must
>support the exact way. It can no longer then be c
On 06/01/2018 02:05, Michael Niedermayer wrote:
ffv1enc.c |4
1 file changed, 4 deletions(-)
acfc60c913b311b148f2eeef2d2d6ea9e37afcf7
0001-avcodec-ffv1enc-mark-RGB48-support-as-non-experiment.patch
From 303f63fb7e6172fdb7de66da1f8a4006b79a535f Mon Sep 17 00:00:00 2001
From: =?UTF
On Fri, Jan 05, 2018 at 10:26:42PM +0100, Jerome Martinez wrote:
> On 05/01/2018 16:14, Tobias Rapp wrote:
> >On 05.01.2018 11:18, Jerome Martinez wrote:
> >>0001-FFV1-make-RGB48-support-as-non-experimental.patch
> >>
> >>From cd1bfe68a1a809700f25e593ac21ca3876d265ad Mon Sep 17 00:00:00 2001
> >>Fr
On 05/01/2018 16:14, Tobias Rapp wrote:
On 05.01.2018 11:18, Jerome Martinez wrote:
0001-FFV1-make-RGB48-support-as-non-experimental.patch
From cd1bfe68a1a809700f25e593ac21ca3876d265ad Mon Sep 17 00:00:00 2001
From: =?UTF-8?q?J=C3=A9r=C3=B4me=20Martinez?=
Date: Fri, 5 Jan 2018 11:09:01 +0100
S
On 05.01.2018 11:18, Jerome Martinez wrote:
0001-FFV1-make-RGB48-support-as-non-experimental.patch
From cd1bfe68a1a809700f25e593ac21ca3876d265ad Mon Sep 17 00:00:00 2001
From: =?UTF-8?q?J=C3=A9r=C3=B4me=20Martinez?=
Date: Fri, 5 Jan 2018 11:09:01 +0100
Subject: [PATCH] FFV1: make RGB48 support
1 year without RGB48 related patches, tested by a couple of users,
tested with a FFV1 conformance checker, I suggest that FFV1 RGB48
support in FFmpeg does not mandate anymore the user to add " -strict
experimental" on the command line during encoding.
From cd1bfe68a1a809700f25e593ac21ca3876d2
12 matches
Mail list logo