Would definitely want to try something along those lines. failed to set option SRTOPASSPHRASE on socket: Operation not. ass format: (haha fun extension name) ffmpeg-i. Otherwise, you can the libass library (make sure your FFmpeg install has the library in the configuration -enable-libass). You can pass in an array of ffmpeg filter strings or objects with keys that make it a little bit more intuitive. The configured passphrase cannot be recovered (write-only). The original fluent-ffmpeg project has a decent way of handling complex filters. For anything beyond that, using this approach would become a nightmare!įor more nuanced arguments, we'll have to find a better way of setting them. Anyway, running npm install on a linux installation and uploading the code to Lambda did the trick. Then I use the following command to extract images from my video file.
Would be interested in the reasons, though. Right now each argument is wrapped in its own field in a struct and this approach is best when there is only a one-to-one mapping from argument to value. My development machine runs Windows 7, and that's apparently what caused the issue. However, it's easy to simplify something that is already simple, but like you've encountered with more sophisticated arguments, it becomes chaotic to try to abstract and simplify something quite complex. I would say the benefit of this approach is that we can simplify setting ffmpeg args by exposing a fluent API that allows the user to intuitively set them. Thanks for the comment, this is something we will have to consider greatly as this project moves forward.
0 kommentar(er)
