4 ms·
IMO better to fork/exec ffmpeg to avoid memory leaks and security issues. The fork/exec takes a few microseconds and works well (you can even pipe it data). Of
by innagadadavida 9y ago
IMO better to fork/exec ffmpeg to avoid memory leaks and security issues. The fork/exec takes a few microseconds and works well (you can even pipe it data). Of course, if the command line options doesn’t do what you want, that’s a different issue.
- blt 9y agoHow to deal with efficiency issues from the huge amount of data being piped? Shared memory area and send pointers over the pipe?
- Something1234 9y agoIs this really a problem with pipes. I found that I can easily push 8-9 GIB/s over a standard pipe on my 4 year old desktop yes | pv > /dev/null