Closed isrealityreallyreal closed 2 years ago
It's also worth noting that when I use ffmpeg outside of Aegisub, the -crf
option works fine.
So... the issue went away when I went to Trim Settings and changed the encoder from x264 to ffmpeg. I could have sworn I had already done that when first prompted but maybe it didn't save the setting properly.
Previously, Aegisub had crashed when I clicked the Encoder button (in Trim Settings), so I had already hard coded the path to the ffmpeg executable in aegisub-motion.json
prior to attempting any trim. Considering that the Encoder was actually set to x264 but with the path to ffmpeg, I understand why something went wrong, but it still baffles me how this could produce the error message I got.
Since this is no longer affecting me, I'll go ahead and close the issue.
[Disclaimer: I see that there are several open issues related to trim right now. At first glance my issue appears unrelated to any of those, though I may be mistaken.]
When I try to trim a line using ffmpeg it fails with the following output:
I looked up the
unrecognized option '-crf'
part, which led me to this answer suggesting that the problem derives from ffmpeg not being compiled with the--enable-gpl
and--enable-libx264
options, but as you can see in the above output, it does include those options, so I'm not sure what's going on here.I am using the typesetting tools fork of Aegisub, commit
9266-master-f21d8a360
if the title bar is to be believed. I installed Aegisub-Motion through Dependency Control. Looks like it's at version 1.0.9.Any help is appreciated.