xyloy
30th April 2006, 16:21
source: DOSBox's (v0.65) .AVI capture movie (codec: Zipped Motion Block Video VFW v0.1) 640*480(640 is divisible by 16, 480 is divisible by 16 and 24, so AFAIK it's ok for x264's Width&Height limitations), 70 FPS.
AviSynth(v2.5.5) Script:
avisource("F:\tex197_000.avi")
ConvertToYV12()
x264 (http://x264.nl/)(rev516) cmd line:
E:\Program Files\x264\x264.exe --crf 22 --keyint 700 --min-keyint 70 --ref 5 --mixed-refs --no-fast-pskip --bframes 3 --b-pyramid --b-rdo --bime --weightb --direct auto --subme 7 --trellis 2 --analyse all --8x8dct --me umh --cqm "jvt" --progress --no-psnr --output "F:\Tex.mp4"
Here are 5 screenshots(.PNG format) where you can spot the bugs easily
http://img225.imageshack.us/img225/1747/snapshot200604301658427hk.png (http://imageshack.us)
http://img133.imageshack.us/img133/692/snapshot200604301659022nl.png (http://imageshack.us)
http://img135.imageshack.us/img135/4078/snapshot200604301659368bn.png (http://imageshack.us)
http://img222.imageshack.us/img222/5198/snapshot200604301659559ka.png (http://imageshack.us)
http://img222.imageshack.us/img222/3629/snapshot200604301700203cx.png (http://imageshack.us)
Before, I had the very same bugs with a nonmod16 source capture of 320*200(and that time, MeGUI warned me), so I used XviD v1.2 instead. I used also XviD v1.2 with this capture and I had no bugs(so I guess my problem isn't related to ConvertToYV12).
By the way, I'm curious about this story...
Is XviD's unlimitation in Width&Height conform to the MPEG-4 ASP specs ?
And is it H.264/AVC's specs that prevents x264 to have no limitations ?
Any help would be very much appreciated.
I can also upload the source .AVI file, and/or the resulting .MKV file if asked. ;)
AviSynth(v2.5.5) Script:
avisource("F:\tex197_000.avi")
ConvertToYV12()
x264 (http://x264.nl/)(rev516) cmd line:
E:\Program Files\x264\x264.exe --crf 22 --keyint 700 --min-keyint 70 --ref 5 --mixed-refs --no-fast-pskip --bframes 3 --b-pyramid --b-rdo --bime --weightb --direct auto --subme 7 --trellis 2 --analyse all --8x8dct --me umh --cqm "jvt" --progress --no-psnr --output "F:\Tex.mp4"
Here are 5 screenshots(.PNG format) where you can spot the bugs easily
http://img225.imageshack.us/img225/1747/snapshot200604301658427hk.png (http://imageshack.us)
http://img133.imageshack.us/img133/692/snapshot200604301659022nl.png (http://imageshack.us)
http://img135.imageshack.us/img135/4078/snapshot200604301659368bn.png (http://imageshack.us)
http://img222.imageshack.us/img222/5198/snapshot200604301659559ka.png (http://imageshack.us)
http://img222.imageshack.us/img222/3629/snapshot200604301700203cx.png (http://imageshack.us)
Before, I had the very same bugs with a nonmod16 source capture of 320*200(and that time, MeGUI warned me), so I used XviD v1.2 instead. I used also XviD v1.2 with this capture and I had no bugs(so I guess my problem isn't related to ConvertToYV12).
By the way, I'm curious about this story...
Is XviD's unlimitation in Width&Height conform to the MPEG-4 ASP specs ?
And is it H.264/AVC's specs that prevents x264 to have no limitations ?
Any help would be very much appreciated.
I can also upload the source .AVI file, and/or the resulting .MKV file if asked. ;)