Timeline for Strange errors when using ffmpeg in a loop
Current License: CC BY-SA 3.0
11 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Sep 9, 2021 at 4:56 | answer | added | Arani | timeline score: -1 | |
| Jun 28, 2021 at 12:10 | answer | added | Pamphile | timeline score: 18 | |
| Mar 21, 2020 at 22:57 | comment | added | MikeV | The linuxquestions link is broken -- here's the updated link | |
| Apr 14, 2012 at 7:08 | vote | accept | Mark Williams | ||
| Apr 14, 2012 at 2:47 | answer | added | jw013 | timeline score: 94 | |
| Apr 13, 2012 at 9:12 | answer | added | Mark Williams | timeline score: 25 | |
| Apr 12, 2012 at 18:37 | comment | added | Mark Williams | I've found the solution. The bash script seems to product input (Namely the 'c' key) which interferes with the ffmpeg process. Piping "< /dev/null" into ffmpeg like so: ffmpeg -i "./$f" -vcodec libx264 -vprofile high -preset slow -b:v 500k -maxrate 500k -bufsize 1000k -threads 0 -acodec libfaac -ab 128k "./mp4s/$MP4FILENAME" < /dev/null Fixes the issue. via [linuxquestions.org/questions/programming-9/… [1]: linuxquestions.org/questions/programming-9/… | |
| Apr 12, 2012 at 16:35 | comment | added | Warren Young | Say bash -x myscript to get a line-by-line trace of the script's execution, with all the variables expanded. Oh, and incidentally, you've reinvented the basename wheel on the FILENAME= line. :) | |
| Apr 12, 2012 at 14:34 | comment | added | Peter.O | As a side issue: mp4filename=$(basename "$f" mp4) might be useful (see man basename and man dirname for more info) | |
| Apr 12, 2012 at 14:15 | comment | added | Faheem Mitha | I'm not much of a scripter, but an obvious suggestion - have your script print out the lines it is executing. They may not be what you think they are. | |
| Apr 12, 2012 at 13:18 | history | asked | Mark Williams | CC BY-SA 3.0 |