When encoding, the parameters are not taken in account. For exemple, 2-pass is not checked but x264 encodes in 2-pass, the same with Quality : whatever I choose ultrafast or veryslow, it takes the same encode framerate... I don't know for the other params as I don't have a way to check.
Hello,
Regarding the 2-pass checkbox - thank you, we found the issue, will fix in the next beta.
Regarding the presets - the speed can be noticed on the second pass mainly (for 2-pass encoding).
Hello!
You mean this UI? No, in this UI you can't. It is a replacement for command line recommended for Blu-ray encoding by x264bluray.com (not available anymore).
I found that the x264 binary is 32bits, why don't use 64bits one ? I replaced it by myself and got almost x2 performance.
But It stayed very slow (between 12-19fps), so I tested an encode by hand with command line and got 70fps !
Why x264 encoding is very slow with Encoders UI, but not executed standalone ?
You can use any binaries. Our archive is what some of our clients use.
Regarding the speed from UI against command line. UI creates cmd-file in the temp folder and runs it. You can compare your command line with it.
The only thing that I see - Encoder UI is not intended for using 1080p with x265.
BROKEN PIPE:
I've been attempting to end an encode at a certain point ( 240 frames for testing purposes).
I've successfully encoded the whole file using x265 but keep on getting Broken pipe errors whenever I limit the amount of frames to encode.
I did try 241,244,480 etc to see if it needed a certain amount of frames to be able to close on and I did try encoding it direct via the CMD, all with the same result.
I suppose you need to specify start/stop frames for ffmpeg, not x265
so you need to use -ss/-to/-t - check https://ffmpeg.org/ffmpeg.html for details
and you need to add it at the beginning of the "Other x265 ..." parameters
