Timeline for Problem with ffmpeg in bash loop
Current License: CC BY-SA 3.0
8 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Nov 20, 2020 at 18:39 | comment | added | mivk |
An alternative to redirecting stdin with < /dev/null is the -nostdin option like in ffmpeg -nostdin -i "$f" ...
|
|
| Jul 23, 2019 at 2:46 | comment | added | simon | This was a tough one to debug -- thanks for saving me a headache today! | |
| Nov 10, 2015 at 13:39 | comment | added | chepner | No, the problem is with scripts that make naive assumptions about what characters can appear in a file name. | |
| Nov 10, 2015 at 13:22 | comment | added | forthrin | Filenames containing newline characters; then I'd say the problem would lie elsewhere :) | |
| Nov 9, 2015 at 11:58 | comment | added | chepner | It will; just be aware that file names containing newline characters break that approach. | |
| Nov 9, 2015 at 7:50 | comment | added | forthrin |
Will the prior approach work if using find . -type f (where for won't)?
|
|
| Nov 9, 2015 at 7:29 | vote | accept | forthrin | ||
| Nov 9, 2015 at 1:59 | history | answered | chepner | CC BY-SA 3.0 |