On 10/20/2012 12:25 PM, Peter B. wrote:
> On 10/20/2012 12:15 AM, Peter B. wrote:
>> On 10/19/2012 08:30 PM, Luca Barbato wrote:
>>
>>> slicecrc should be supported.
>> The version I've compiled now does.
>> Before it was complaining that the commandline argument "slicecrc" is
>> unknown.
>>
> Sor
On 10/20/2012 12:15 AM, Peter B. wrote:
> On 10/19/2012 08:30 PM, Luca Barbato wrote:
>
>> slicecrc should be supported.
> The version I've compiled now does.
> Before it was complaining that the commandline argument "slicecrc" is
> unknown.
>
Sorry! Mistake in my testscript. It was still using ff
On 10/19/2012 08:30 PM, Luca Barbato wrote:
> On 10/19/2012 04:43 PM, Peter B. wrote:
>> I've compiled your github libav version including ffv1.3 and it seems
>> that "slicecrc" is not yet implemented, correct?
>>
>> If you could quickly tell me which features/colorspaces should be
>> working in yo
On 10/19/2012 04:43 PM, Peter B. wrote:
> I've compiled your github libav version including ffv1.3 and it seems
> that "slicecrc" is not yet implemented, correct?
>
> If you could quickly tell me which features/colorspaces should be
> working in your implementation, I could run my testsuite and re
I've compiled your github libav version including ffv1.3 and it seems
that "slicecrc" is not yet implemented, correct?
If you could quickly tell me which features/colorspaces should be
working in your implementation, I could run my testsuite and report
any findings.
Thanks,
Pb
__
On 10/19/2012 12:16 PM, Luca Barbato wrote:
> As Kostya asked here the proper split between decoder and encoder.
>
> I tested it encoding and decoding properly.
Comments addressed here https://github.com/lu-zero/libav/tree/ffv1 to
not burden the ml with large patches.
lu
_
As Kostya asked here the proper split between decoder and encoder.
I tested it encoding and decoding properly.
___
libav-devel mailing list
libav-devel@libav.org
https://lists.libav.org/mailman/listinfo/libav-devel
On 10/14/2012 09:20 PM, Luca Barbato wrote:
>
> Could you please provide me a small sample of it?
>
You can generate it, using "red_kayak" from xiph/derf's collection:
http://media.xiph.org/video/derf/y4m/red_kayak_1080p.y4m
Using the current git of ffmpeg, create the FFv1.3 video as follows:
//-
On 10/14/2012 08:39 PM, Peter B. wrote:
> On 10/12/2012 12:24 AM, Luca Barbato wrote:
>> On 10/05/2012 05:31 PM, Peter B. wrote:
>>> On 10/01/2012 05:30 PM, Luca Barbato wrote:
I'm rebasing old patches supporting some pixel formats and possibly
I'll have a look at ffv1 to see what really
On 10/12/2012 12:24 AM, Luca Barbato wrote:
> On 10/05/2012 05:31 PM, Peter B. wrote:
>> On 10/01/2012 05:30 PM, Luca Barbato wrote:
>>> I'm rebasing old patches supporting some pixel formats and possibly
>>> I'll have a look at ffv1 to see what really changed.
>> In order to avoid misunderstanding
On 10/12/2012 03:14 PM, Peter B. wrote:
> On 10/12/2012 12:24 AM, Luca Barbato wrote:
>> On 10/05/2012 05:31 PM, Peter B. wrote:
>>> On 10/01/2012 05:30 PM, Luca Barbato wrote:
I'm rebasing old patches supporting some pixel formats and possibly
I'll have a look at ffv1 to see what really
On 10/12/2012 12:24 AM, Luca Barbato wrote:
> On 10/05/2012 05:31 PM, Peter B. wrote:
>> On 10/01/2012 05:30 PM, Luca Barbato wrote:
>>> I'm rebasing old patches supporting some pixel formats and possibly
>>> I'll have a look at ffv1 to see what really changed.
>> In order to avoid misunderstanding
On 10/05/2012 05:31 PM, Peter B. wrote:
> On 10/01/2012 05:30 PM, Luca Barbato wrote:
>> I'm rebasing old patches supporting some pixel formats and possibly
>> I'll have a look at ffv1 to see what really changed.
> In order to avoid misunderstandings, I wanted to ask if you are trying
> to merge th
On 10/05/2012 05:31 PM, Peter B. wrote:
> On 10/01/2012 05:30 PM, Luca Barbato wrote:
>> I'm rebasing old patches supporting some pixel formats and possibly
>> I'll have a look at ffv1 to see what really changed.
> In order to avoid misunderstandings, I wanted to ask if you are trying
> to merge th
On 10/01/2012 05:30 PM, Luca Barbato wrote:
> I'm rebasing old patches supporting some pixel formats and possibly
> I'll have a look at ffv1 to see what really changed.
In order to avoid misunderstandings, I wanted to ask if you are trying
to merge the new FFv1.3 code into libav, or just the colors
On 10/01/2012 06:22 PM, Peter B. wrote:
> Honestly, I'm not 100% sure about that, because that was coordinated
> directly between someone from the filmarchive and Georg Lippitsch who
> implemented the changes. He also modified DPX code as far as I know.
> I only saw 12 and 14 bits - no 13 so far...
Quoting Luca Barbato :
Those are more interesting to me, I prefer adding colorspaces only if
the need arises.
Understood :)
The main question regarding rgb with more than 10 and less than 16 is
where it is used.
This was added due to a request from the national film-archive for
converting
On 10/01/2012 05:57 PM, Peter B. wrote:
> That would be great! Thank you very much!
No problem, I hope to get the first ones working so you can copy over if
the need arises.
> With FFv1.3 it's not only about additional colorspaces, but the main
> features of the new version include multithreading
Quoting Luca Barbato :
On 10/01/2012 03:55 PM, Peter B. wrote:
I've removed unused pix_fmts from my patch (0-padded RGB, for example)
and added entries in pixdesc.c. It compiles correctly, so I assume
there's no syntax error at least.
Thanks, you are missing few bits in swscale, though.
Yes
On 10/01/2012 03:55 PM, Peter B. wrote:
> I've removed unused pix_fmts from my patch (0-padded RGB, for example)
> and added entries in pixdesc.c. It compiles correctly, so I assume
> there's no syntax error at least.
Thanks, you are missing few bits in swscale, though.
> I also took the liberty
On Mon, Oct 01, 2012 at 03:55:31PM +0200, Peter B. wrote:
>
> Which would be the preferred way for patches in the future on this list?
git send-email
Diego
___
libav-devel mailing list
libav-devel@libav.org
https://lists.libav.org/mailman/listinfo/liba
Quoting Luca Barbato :
On 10/01/2012 12:07 AM, Ronald S. Bultje wrote:
Hi,
On Sun, Sep 30, 2012 at 1:00 PM, Peter B. wrote:
+PIX_FMT_0RGB=0x123+4, ///< packed RGB 8:8:8, 32bpp, 0RGB0RGB...
+PIX_FMT_RGB0, ///< packed RGB 8:8:8, 32bpp, RGB0RGB0...
+PIX_FMT_0BGR, ///<
On 10/01/2012 12:07 AM, Ronald S. Bultje wrote:
> Hi,
>
> On Sun, Sep 30, 2012 at 1:00 PM, Peter B. wrote:
>> +PIX_FMT_0RGB=0x123+4, ///< packed RGB 8:8:8, 32bpp, 0RGB0RGB...
>> +PIX_FMT_RGB0, ///< packed RGB 8:8:8, 32bpp, RGB0RGB0...
>> +PIX_FMT_0BGR, ///< packed BGR 8
Hi,
On Sun, Sep 30, 2012 at 1:00 PM, Peter B. wrote:
> +PIX_FMT_0RGB=0x123+4, ///< packed RGB 8:8:8, 32bpp, 0RGB0RGB...
> +PIX_FMT_RGB0, ///< packed RGB 8:8:8, 32bpp, RGB0RGB0...
> +PIX_FMT_0BGR, ///< packed BGR 8:8:8, 32bpp, 0BGR0BGR...
> +PIX_FMT_BGR0, ///< p
I forgot to supply my patches which add the newly supported colorspace
definitions:
--- a/libavutil/pixfmt.h
+++ b/libavutil/pixfmt.h
@@ -157,6 +157,31 @@
PIX_FMT_GBRP10LE, ///< planar GBR 4:4:4 30bpp, little endian
PIX_FMT_GBRP16BE, ///< planar GBR 4:4:4 48bpp, big endian
PIX_FMT
On 09/30/2012 09:16 PM, Luca Barbato wrote:
>
> pkt_timebase reference could be dropped, not sure what got changed in
> the rangecoder let's have a look.
What does "pkt_timebase" do, and which counterpart would exist in libav?
Is there a struct-documentation anywhere, btw?
Thanks!
Pb
On 9/30/12 8:59 PM, Peter B. wrote:
Hello,
I'm working at the Austrian Mediathek (national audio/video archive) and
together with other archives we are using FFv1 as our archival video codec.
There have been major updates to FFv1, and its version 3 (FFv1.3) is
nearing its release.
I've tried t
Hello,
I'm working at the Austrian Mediathek (national audio/video archive) and
together with other archives we are using FFv1 as our archival video codec.
There have been major updates to FFv1, and its version 3 (FFv1.3) is
nearing its release.
I've tried to merge the code from ffmpeg to the cu
28 matches
Mail list logo
