Re: [libav-devel] [PATCH] movenc: check for the error in the AVIOContext and write

2016-03-19 Thread Vittorio Giovara
On Thu, Aug 27, 2015 at 7:20 AM, Luca Barbato wrote: > On 27/08/15 13:10, Martin Storsjö wrote: >> On Thu, 27 Aug 2015, Alexandra Hájková wrote: >> >>> the error message if there is some error. MOV has its header >>> at the end of the file so the output will be corrupted if

[libav-devel] [PATCH] movenc: check for the error in the AVIOContext and write

2015-08-27 Thread Alexandra Hájková
the error message if there is some error. MOV has its header at the end of the file so the output will be corrupted if writing to the output will fail before header is written. Bug-Id: 881 --- libavformat/movenc.c | 5 + 1 file changed, 5 insertions(+) diff --git a/libavformat/movenc.c

Re: [libav-devel] [PATCH] movenc: check for the error in the AVIOContext and write

2015-08-27 Thread Luca Barbato
On 27/08/15 12:09, Alexandra Hájková wrote: the error message if there is some error. MOV has its header at the end of the file so the output will be corrupted if writing to the output will fail before header is written. Bug-Id: 881 --- libavformat/movenc.c | 5 + 1 file changed, 5

Re: [libav-devel] [PATCH] movenc: check for the error in the AVIOContext and write

2015-08-27 Thread Martin Storsjö
On Thu, 27 Aug 2015, Alexandra Hájková wrote: the error message if there is some error. MOV has its header at the end of the file so the output will be corrupted if writing to the output will fail before header is written. This isn't true for all mov modes, only the non-fragmented ones.

Re: [libav-devel] [PATCH] movenc: check for the error in the AVIOContext and write

2015-08-27 Thread Luca Barbato
On 27/08/15 13:10, Martin Storsjö wrote: On Thu, 27 Aug 2015, Alexandra Hájková wrote: the error message if there is some error. MOV has its header at the end of the file so the output will be corrupted if writing to the output will fail before header is written. This isn't true for all