Le duodi 2 floréal, an CCXXIV, Jan Sebechlebsky a écrit : > I am not sure, I've understood this. If you meant the error of slave muxer, > it should be already printed (since it is handled by slave muxer itself).
Normally, components of FFmpeg print error messages only if the error code is enough to accurately encode the error. For example, a network protocol would print a protocol-specific explanation if the server rejects a chunk of data, because EINVAL or INVALIDDATA is not accurate enough to know what went wrong, but the file muxer, in case of disk full, will just return ENOSPC, because ENOSPC is accurate enough. You can observe that with: ffmpeg -lavfi testsrc -c rawvideo -f tee '[f=rawvideo]/dev/full' It outputs as only error message: av_interleaved_write_frame(): No space left on device And you can observe that ffmpeg.c is responsible for this. Regards, -- Nicolas George
signature.asc
Description: Digital signature
_______________________________________________ ffmpeg-devel mailing list ffmpeg-devel@ffmpeg.org http://ffmpeg.org/mailman/listinfo/ffmpeg-devel
