2020-05-19, 02:13 AM
Been fiddling with this again and ended up finding out that the problem with x264 was that it was trying to use 32-bit AviSynth (some of the plugins I tried were 32-bit only) with 64-bit x264. Turns out that's easily fixed by avs4x264mod! So, I've just run this...
... with this:
Results look like they might be better than via the prores intermediate and obviously means I don't have a big ol' prores master sitting on my storage. The .h264 output from this is only a few GB.
Code:
FFmpegSource2("inputfile.mkv")
SetFilterMTMode("QTGMC", 2)
AssumeFPS("ntsc_video")
AssumeTFF()
Crop(10, 40, -6, -44)
QTGMC(Preset="Slower", Edithreads=6)
BicubicResize(1280,720)
Prefetch(threads=14)
... with this:
Code:
avs4x264mod --pass 1 --bitrate 20000 --bluray-compat --level 4.1 --preset veryslow --tune film --keyint 60 --sar 1:1 --slices 4 --vbv-bufsize 30000 --vbv-maxrate 40000 --b-pyramid none --weightp 0 --colorprim smpte170m --transfer smpte170m --colormatrix smpte170m --merange 24 --stats ".stats" --output NUL script.avs
avs4x264mod --pass 2 --bitrate 20000 --bluray-compat --level 4.1 --preset veryslow --tune film --keyint 60 --sar 1:1 --slices 4 --vbv-bufsize 30000 --vbv-maxrate 40000 --b-pyramid none --weightp 0 --colorprim smpte170m --transfer smpte170m --colormatrix smpte170m --merange 24 --stats ".stats" --output output.h264 script.avs
PAUSE
Results look like they might be better than via the prores intermediate and obviously means I don't have a big ol' prores master sitting on my storage. The .h264 output from this is only a few GB.