Hi Michal, On 13.03.2015 11:54, Michal Suchanek wrote: > I think that by default errors should lead to non-zero return value even > if output can be produced. Such output can also contain errors and > cannot be considered valid unless checked by the user. However, if this > is weird upstream design decision Debian is not the place to change that.
I don't think it's so weird, because if ffmpeg created a file it should have no errors in the sense that a player can play it just fine. > Unfortunately, the option to report errors does not seem to be > documented. After some grepping of the man page I get no relevant > results. At least it's mentioned in the long help output: $ ffmpeg --help long 2>&1 | grep xerror -xerror error exit on error > Also it does not change the fact that encoding broken source may result > in success. > > $ ffmpeg -xerror -v warning -i > /scratch/dwhelper/Mill_CPU_for_Humans_-_Part_2.mp4 -f null /dev/null ; echo $? > [null @ 0x264f8c0] Encoder did not produce proper pts, making some up. > [h264 @ 0x26096e0] AVC: nal size 5421 > Last message repeated 1 times > [h264 @ 0x26096e0] no frame! > 0 This option works here, i.e. it changes the return code to 1, if decoding a part of the input file failed. It seems your file is not broken enough... Can you share it, so that I can have a look at why '-xerror' doesn't make a difference? Best regards, Andreas -- To UNSUBSCRIBE, email to [email protected] with a subject of "unsubscribe". Trouble? Contact [email protected]
