osophy.junkie
9th June 2008, 05:23
Hi,
I get the visual errors seen in attached photo during random scene changes...
until approved: http://lamedomain.net/badI.jpg
I use the following command line args:
--crf 16 --level 3 --ref 10 --mixed-refs --no-fast-pskip --bframes 10 --b-pyramid --b-rdo --bime --weightb --direct auto --filter -1,1 --subme 6 --trellis 1 --partitions p8x8,b8x8,i4x4,i8x8 --8x8dct --ipratio 1.3 --pbratio 1.2 --vbv-bufsize 1500 --vbv-maxrate 2300 --qcomp 0.4 --scenecut 30 --threads auto --thread-input --sar 1:1 --progress --output final.mkv final.avs
1. The machine is a vmware image running on a c2d. I've tried running it with both single and dual processors mode.
2. I have tried running x264 with --threads 1 and --threads 2 with the same results.
3. Changing x264 version has no effect.
4. Changing scenecut to 50 had no effect.
Suggestions?
I get the visual errors seen in attached photo during random scene changes...
until approved: http://lamedomain.net/badI.jpg
I use the following command line args:
--crf 16 --level 3 --ref 10 --mixed-refs --no-fast-pskip --bframes 10 --b-pyramid --b-rdo --bime --weightb --direct auto --filter -1,1 --subme 6 --trellis 1 --partitions p8x8,b8x8,i4x4,i8x8 --8x8dct --ipratio 1.3 --pbratio 1.2 --vbv-bufsize 1500 --vbv-maxrate 2300 --qcomp 0.4 --scenecut 30 --threads auto --thread-input --sar 1:1 --progress --output final.mkv final.avs
1. The machine is a vmware image running on a c2d. I've tried running it with both single and dual processors mode.
2. I have tried running x264 with --threads 1 and --threads 2 with the same results.
3. Changing x264 version has no effect.
4. Changing scenecut to 50 had no effect.
Suggestions?