Divx5 speed quality

[wing1]

d/l divx5 and installed (pro version). Encode 10min capture clip with Bframe option + 1-pass quality mode. Result is somewhat equal to what xvid's quality as late and filesize is a few Mb's smaller. However, the filter reminded me of the old problem that used to happen in version 4.11 ( slider function freakout the player ). Nevertheless, the DivX5.0 filter is less CPU hungry then xvid's filter and a little sharper detail, but color is a little washed out. Furthermore, Divx5.0 some how affects Avisynth functionality and crashes it when DS source option is used to open the video clip. Now the speed is a little slower then xvid for my test on 1900XP AMD ( where does the 2x/3x realtime speed came from ??? ). The only option that I would like to use with this new codec is the de-interlacing option; However, with the speed which I am seeing from my test, I would doubt if this option is going to work for capturing purpose.

[chokoboii]

I currently do a lot of my movies in SBC with divx 3.11. With nandub, i usually got around 30fps on my 1.7ghz Pentinum 4. However when I encoded a movie last night, i got an average of 15fps!! what the heck is going on?!

[chokoboii]

I currently do a lot of my movies in SBC with divx 3.11. With nandub using divx3.11 on SBC, i usually got around 30fps on my 1.7ghz Pentinum 4. However when I encoded a movie last night with divx5.0, i got an average of 15fps!! what the heck is going on?!

[Darrius "Junto" Thompson]

Originally posted by chokoboii
I currently do a lot of my movies in SBC with divx 3.11. With nandub using divx3.11 on SBC, i usually got around 30fps on my 1.7ghz Pentinum 4. However when I encoded a movie last night with divx5.0, i got an average of 15fps!! what the heck is going on?!

What features did you have turned on? I'm supposing none of the new ones since the new features really chew up CPU (?)

Darrius "Junto" Thompson

[chokoboii]

The settings i used were just the GMC and bidirectional encoding. everything else is set to the default. i know that these features would slow it down, but i didnt think that it would slow it down to 15fps!! especially since i was encoding at 30fps using SBC. the results of the divx5.0 is really really good, dont get me wrong. but the time it takes is a long time, and it really does hog the CPU power. Is using divx 5.0 worth it?

[Killah]

The first pass is slower yes. But the second pass is a lot faster, quote from Doom9 Divx5 guide : MV file contains motion vector data. If it is stored the 2nd pass will be performed quicker since the motion compensation does not have to be performed again

I think if you time both the passes, you'll get the same encoding speed you used to get with SBC encoding (maybe a bit faster)

[Doom9]

I can only speak for the single full lenght 2 pass test I did so far but the 2nd pass was 33% faster.. going almost at 30fps which is considerably higher than what I get in nandub.. but the first pass definitely is slower, especially b frames slow down the encoding. But if you don't use the motion vector file (takes another 100-200mb temporary space but well worth it imho) the 2nd pass won't be any faster.

[tg0021]

Here are a few tests of the encoding speeds we made with jotenakis. Internal resizer of DivX 5 is quite good but not always. Avisynth is sometimes beter e.g. with GMC+B-frames which seem to be the most relevant parameters

http://l.sonia.free.fr/Codecs.jpg

PS : Xvid parameters are
2 passes int w/o luma, H.263 (1st pass)+Modulated (2nd pass) & 6-ultra high
Curve compression : 240, 25%, 15%
I-Frame quantizer : between 2 et 5
Keyframe boost : 30%

[ppera2]

I tested 'lite' version (no B frames), and first pass is slightly faster than by 4.12 and second is faster by some 60 % when use motion vector file.
I made it with Mpeg1 source in Virtual Dub, because of fast decode of it, so I get much better result than when use VOB source, resize, frameserving etc.

With Mpeg1 source res 704x320 i get 77 fps in second pass (Athlon@1386 MHz). First pass was at 47 fps. Speed/quality set to slowest. It means that encoder is really fast like hell.