NOTE: This article is 3 years or older so its information may no longer be relevant. Read on at your own discretion! Comments for this article have automatically been locked, refer to the FAQ
for more details.
I was using my Odroid XU4 based media server
to transcode some videos using ffmpeg
when I came across some strange errors appearing on the console. When I would run ffmpeg
as a single command, it would work, however running it in a loop presented errors (or rather strange behaviour).
This is the kind of output I was seeing...
Instead of processing the video file, ffmpeg
would stop and wait for user input. The message 'error parsing debug value'
would also be displayed prior to input being asked.
Turns out this happens because by default ffmpeg
is in interactive mode. This means that the output it was producing was being used as input and eventually certain input characters caused ffmpeg
to stop and ask for user input.
There are two ways to stop this from happening:
- Add '< /dev/null' to the end of the ffmpeg command so it reads input from the null device instead of standard input
- Add '-nostdin' to the ffmpeg command as per documentation to stop it reading input from standard input by default
I went for the first option, so my command to transcode all AVI files in a directory to H.264 with AAC MKV files looked like this:
Hope you found this post useful...
...so please read on! I love writing articles that provide beneficial information,
tips and examples to my readers. All information on my blog is provided free of
charge and I encourage you to share it as you wish. There is a small favour I ask in return however -
engage in comments below, provide feedback, and if you see mistakes let me know.
If you want to show additional support and help me pay for web hosting and
domain name registration,
donations, no matter how small, are always welcome!
Use of any information contained in this blog post/article is subject to this disclaimer
Other posts you may like...