Process separation for 10-bit?

[asarian]

I was thinking about doing a 10-bit encode. :)

Thing is, I'm used to calling x264 like this (from a batch file):

"c:\x264\avs2yuv.exe" "f:\jobs\%1.avs" -o - | "c:\x264\x264.exe" - --demuxer y4m ....

If I recall correctly, that was a trick by Lord_Mulder, from a while back already, so as to maximize available memory to the x264 process (thru the process separation). But it will likely ruin the 10-bit color-space.

So, can this be done for 10-bit too?

[sneaker_ger]

You can continue using that if you want to.

In case you are doing high-bitdepth work within AviSynth you need to pipe raw:
"c:\x264\avs2yuv.exe" -raw "f:\jobs\%1.avs" -o - | "c:\x264\x264.exe" - --demuxer raw --input-res 1920x1080 --input-depth 16 ...

(--input-depth 10 may or may not be better suited depending on what you are doing)

But working in high-bitdepth is not required to profit from 10 bit x264 encoding, you can continue to use your old command-line in that case.

[asarian]

You can continue using that if you want to.

In case you are doing high-bitdepth work within AviSynth you need to pipe raw:
"c:\x264\avs2yuv.exe" -raw "f:\jobs\%1.avs" -o - | "c:\x264\x264.exe" - --demuxer raw --input-res 1920x1080 --input-depth 16 ...

(--input-depth 10 may or may not be better suited depending on what you are doing)

But working in high-bitdepth is not required to profit from 10 bit x264 encoding, you can continue to use your old command-line in that case.


Thx! That is a lot easier than I thought it would be! :)