use check=False, but the point is that a workaround would not be necessary if ffmpeg behaved as expected, i.e. Of course there are ways around this, e.g.
For example, using Python's n(., check=True), the nonzero exit code causes a CalledProcessError. However, when running the commands programmatically, it may cause trouble. For information on the various options, see section 5.2 of the ffmpeg Documentation. To use these options, specify the ffmpeg command and the option, for example, ffmpeg -devices. The following FFmpeg options are used to display information. When running the commands manually, from the command line, the exit code does not make much difference, as long as the requested information is displayed. A full list of the options is available in the ffmpeg Documentation. Questionĭoes the exit code 1 constitute normal behavior for ffmpeg, or am I doing something wrong? Relevance ffmpeg -f dshow -i video="M圜amera" "myfile.mp4", then stop using q, the exit code is 0, as expected. If I stream camera input to disk, using e.g. ffmpeg -list_devices true -f dshow -i dummyįfmpeg -list_options true -f dshow -i video="M圜amera"Īs far as I know, exit code 1 on Windows implies "Incorrect function", so I consider this behavior to be unexpected. If I run any of the following commands from the examples in the documentation, using ffmpeg 4.2.2 on Windows 10, the requested information is successfully displayed in the console, but the process exits with exit code 1, instead of the expected 0 (success).
0 kommentar(er)
