Malow
29th March 2006, 20:14
hi, im curious about someting ive discovered today.
i allways use procoder with avisynth to convert video, and i was looking for a faste codec to decompress video (so compression will be faster)
after some tests, what i found:
when i opens the file direct in procoder, (using canopus dv VFW codec, aparently it uses windows handler for avi for files with VFW codecs) is converts using "full time" 100% of cpu usage, but, when opened by avisynth, the cpu usage on conversion was 80-95% (using nothing but avisource)
aftes mores tests, looks like the disk usage is direct "poportional" on cpu usage, whe using fast speed, more fast disk usage, less cpu usage(about 75%), slower encodes, more cpu usage.
my question is: this may be a avisynth "read buffer" slowdown, a procoder fault, or im doing something stupid?
i guess this is more problable to a "avisynth area" than "procoder"...
i allways use procoder with avisynth to convert video, and i was looking for a faste codec to decompress video (so compression will be faster)
after some tests, what i found:
when i opens the file direct in procoder, (using canopus dv VFW codec, aparently it uses windows handler for avi for files with VFW codecs) is converts using "full time" 100% of cpu usage, but, when opened by avisynth, the cpu usage on conversion was 80-95% (using nothing but avisource)
aftes mores tests, looks like the disk usage is direct "poportional" on cpu usage, whe using fast speed, more fast disk usage, less cpu usage(about 75%), slower encodes, more cpu usage.
my question is: this may be a avisynth "read buffer" slowdown, a procoder fault, or im doing something stupid?
i guess this is more problable to a "avisynth area" than "procoder"...