AntiJw
4th December 2008, 22:01
Hey,
I used this extreme setting for encoding 3DCG/2D:
x264.r1046.exe --crf 21 --level 4.1 --ref 4 --mixed-refs --no-fast-pskip --bframes 15 --b-adapt 2 --b-pyramid --weightb --direct auto --deblock -3:-3 --subme 9 --trellis 2 --psy-rd 0.8:0.2 --partitions all --8x8dct --me tesa --merange 32 --aq-strength 0.5 --vbv-maxrate 50000 --vbv-bufsize 50000 --no-dct-decimate --progress --no-psnr --no-ssim --output "video.1080p.mkv" "video.1080p.avs"
The Task-manager "Processes"-info said that x264 took ~500MB RAM (I got 1GB RAM total, and WinXP Pro), but I saw that ~2GB virtual-memory was also used by x264. Why doesn't task-manager include the virtual-memory usage in "Processes"-info?
I used this extreme setting for encoding 3DCG/2D:
x264.r1046.exe --crf 21 --level 4.1 --ref 4 --mixed-refs --no-fast-pskip --bframes 15 --b-adapt 2 --b-pyramid --weightb --direct auto --deblock -3:-3 --subme 9 --trellis 2 --psy-rd 0.8:0.2 --partitions all --8x8dct --me tesa --merange 32 --aq-strength 0.5 --vbv-maxrate 50000 --vbv-bufsize 50000 --no-dct-decimate --progress --no-psnr --no-ssim --output "video.1080p.mkv" "video.1080p.avs"
The Task-manager "Processes"-info said that x264 took ~500MB RAM (I got 1GB RAM total, and WinXP Pro), but I saw that ~2GB virtual-memory was also used by x264. Why doesn't task-manager include the virtual-memory usage in "Processes"-info?