ffmpeg and x265 allow you to do this too. frame-threads=1 will use 1 thread per frame addressing the issue OP mentioned, without big perf penalty, in contrary to
'pools' switch which sets the threads to be used for encoding.
* Fewer context switches among user space / kernel syscalls
* No need to copy _modified_ data into the swap. The behavior for read only data doesn't change
That's it, nothing miraculous about it. -bcdedit /c {xxxx-xxx-xxx-xxx} (= {..} is parsed as a code block)
-invoking executables with spaces in path