Quote:
Originally Posted by diimaan
I just copied this from the clipboard!
Code:
D:\x264_x64.2010-04-25\pipebuf.exe D:\x264_x64.2010-04-25\avs2yuv.exe D:\sample\m1.avs - : \
D:\x264_x64.2010-04-25\x264_x64.exe --preset slower --crf 21.0 --level 30 --sar 1:1 --output NUL \
--frames 1035 --demuxer y4m --stdin y4m - : 4
so the 4 in the above mentioned code means 4 MB?
|
Yup.
Quote:
Originally Posted by diimaan
and in the place of NUL if i mention a mkv or h264 and run from the pipebuf cli will it encode?
|
The "NUL" device will simply discard everything you write on it. Writing the output to the NUL device makes sense for the
first pass of a 2-Pass encode.
Of course for the
second pass of a 2-Pass encoder or for a 1-Pass CRF encode you would specify a "real" file there...
Quote:
Originally Posted by diimaan
but it stops on 8 MByte!
I can see ppl running the benchmark till 128MByte! but how?
|
The buffer sizes to test are hard-coded. In older versions more (and bigger) buffer sizes were tested.
That was before it turned out that such very large buffers don't help
But of course you can still test arbitrary buffer sizes by calling pipebuf.exe/x264.exe manually from the console.