csirke
17th February 2002, 13:38
Hi!
I made some tests today. I've set up Nandub and opened a compressibility check avs file (8645 frames). I've made a first pass and a second pass (bitrate: 2000) using full and fast processing modes. The sizes are:
1st pass (stats file), w/full proc. mode :: 587864 bytes
1st pass (stats file), w/fast proc. mode :: 587864 bytes
2nd pass (avi file), w/full proc. mode :: 81219584 bytes
2nd pass (avi file), w/fast proc. mode :: 83476480 bytes
There is no difference between the two 1st passes, GKnot gave me the sane percents. But the two 2nd passes. Using the fast proc. mode, the file is around 2 MB's bigger than with full processing and anti-shit.
Is the ~ +5-7 fps worth the plus size? For me, not. The full movie is 172000 frames long. That is ~40 MB plus!!
And a question: when using anti-shit, there will be fewer macroblocks? (Ok, this is in the FAQ's, but i'm too lazy to do this :))
Thanks for your help!!
______
csirke
I made some tests today. I've set up Nandub and opened a compressibility check avs file (8645 frames). I've made a first pass and a second pass (bitrate: 2000) using full and fast processing modes. The sizes are:
1st pass (stats file), w/full proc. mode :: 587864 bytes
1st pass (stats file), w/fast proc. mode :: 587864 bytes
2nd pass (avi file), w/full proc. mode :: 81219584 bytes
2nd pass (avi file), w/fast proc. mode :: 83476480 bytes
There is no difference between the two 1st passes, GKnot gave me the sane percents. But the two 2nd passes. Using the fast proc. mode, the file is around 2 MB's bigger than with full processing and anti-shit.
Is the ~ +5-7 fps worth the plus size? For me, not. The full movie is 172000 frames long. That is ~40 MB plus!!
And a question: when using anti-shit, there will be fewer macroblocks? (Ok, this is in the FAQ's, but i'm too lazy to do this :))
Thanks for your help!!
______
csirke