You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Hey, this is really just here to notify you that I finally got around to implementing support for passing custom ffmpeg options. It doesn't use hardcoded file extensions anymore either, so it works with any codec/container combination that ffmpeg supports, not just what I use. And by passing in custom options, you can now select a codec and configure it to your liking.
The default is still H.264 with CRF 26 and the veryslow preset, but if you want to do something else, it's now as simple as
I also upload an x86-64 binary for every release now, since I'm aware that many people who might want to try this don't necessarily know about Rust or are willing to install Cargo.
The text was updated successfully, but these errors were encountered:
sorry i haven't gotten back sooner, but i've been busy with some other things as of late, hopefully i'll get some time later this week to test this out, and let you know how it goes.
I think supporting native ffmpeg options and switches is an awesome idea for people who want to use for distributed encoding. 🚀
Pinging @ipatch.
Hey, this is really just here to notify you that I finally got around to implementing support for passing custom
ffmpeg
options. It doesn't use hardcoded file extensions anymore either, so it works with any codec/container combination thatffmpeg
supports, not just what I use. And by passing in custom options, you can now select a codec and configure it to your liking.The default is still H.264 with CRF 26 and the
veryslow
preset, but if you want to do something else, it's now as simple as$ shepherd -c c1,c2 input.mkv output.mp4 -- -c:v libx264 -crf 40
I also upload an x86-64 binary for every release now, since I'm aware that many people who might want to try this don't necessarily know about Rust or are willing to install Cargo.
The text was updated successfully, but these errors were encountered: