[FFmpeg-devel] FFV1 Specification

[David Rice]

On Apr 8, 2012, at 8:21 AM, Peter B. wrote:

>>> 2) Can you decode the next frame. Since FFV1 does not specify the
>>> container, that is not a property of FFV1. If you store it in e.g.
>>> NUT the answer is "better than with any MPEG-format", if you would store
>>> it in mov/mp4 the answer would be "about the same as for e.g. Intra-only H.264"
>>> I'd say.
>> yes but dont forget ffv1 can reuse range coder contexts over frames
>> so one has to set the gop size to 1 if this kind of next frame recovery
>> is important to them
>> 
> Interesting to hear that.
> These are exactly the "small details" which I'd love to find when
> reading docs about FFv1 :)
> I thought that when using an intra-frame-only codec, all frames are
> self-contained and there'd be no GOPs. Am I getting something wrong here?

I first learned that ffv1 reuses coder context from this ticket: https://avcodec.org/trac/ffmpeg/ticket/351#comment:6.
>From my tests using ffv1 with -g 1 only adds a minimal to the file size; however it sounds like using -g 1 produces a much more resilient file. Is this the case?
Perhaps the spec could include recommendations for use cases such as producing a file with optimal file size or optimal error resilience.
Dave Rice