fps

[RexManning]

Hi,

I'm currently testing XviD 1.0 beta 2 and had to find out that the encoding process is awfully slow (only 4 fps), while the build I used before 1.0 (I think it was one of Koepi's builds from July or so) was a lot faster (about 50 fps).
I realize that using GMC, QPEL, CM, MSP:6 and VHQ:4 slows down encoding significantly (I didn't usw GMC and QPEL with the old build) but shouldn't a P4/2.6 be able to do better than 4 fps? Am I missing something here?

TIA
rex

[Tuning]

RexManning, speed mainly depends on filters and settings used. If you have high noise filtering, IVTC etc then its obvious why it is slow. More than that GMC, VHQ, MP etc slows down encoding speed. Thus without settings and filtering specified no one could say Codec X is faster than Codec Y.
Another reason is resolution, which has high impact on encoding speed. Wide screen movies are encoded faster than full screen movies, bcoz former has a lesser resolution.

Btw, every one tetsed XviD 1b2 atleast posted its as fast as earlier builds. To my tests too XviD 1.0 is faster.(intel p4)

[Teegedeck]

Originally posted by RexManning
I'm currently testing XviD 1.0 beta 2 and had to find out that the encoding process is awfully slow.
Yeah, could you please give the team a hand there and deliver some speed-optimized code?

[RexManning]

Originally posted by Teegedeck
Yeah, could you please give the team a hand there and deliver some speed-optimized code?
Hey, don't get me wrong here. I'm definately not blaming the XviD developers for releasing a slow codec or anything. Quite the contrary actually, I personally don't mind waiting 20 hours for the encoding process to finish if the result is accordingly - which is the case with XviD. I was merely thinking that maybe I just configured it badly.

regards,
rex

[sysKin]

Originally posted by RexManning
I was merely thinking that maybe I just configured it badly.VHQ was designed for maniacs. Especially VHQ4 is horribly slow compared to the total quality gain, normal people just shouldn't use it at all. GMC is also very slow compared to the result.

Radek

[RexManning]

Thanks sysKin, I'll do a little more testing to find out what settings are best for me. Since I don't do a lot of encoding (maybe two or three DVDs a month) I rather go for highest quality possible than for speed.

regards,
-rex

[homersapien]

IMO, don't bother with anything over VHQ1 (if even that). I can't see any difference between 1-4 on anything I encode.

[Leak]

Originally posted by sysKin
VHQ was designed for maniacs. Especially VHQ4 is horribly slow compared to the total quality gain, normal people just shouldn't use it at all. GMC is also very slow compared to the result.

Oh, come on, it's not *THAT* bad. :)

I've just finished encoding a 26 part series (each episode being around 24:30 minutes) and using VHQ4, Trellis, Cartoon Mode, Adaptive Quantization and GMC it took around 3 hours per episode in 2-pass mode (except for a few episodes that came out undersized with those settings and which I just used the first pass of - it's always handy to have some extra space on a DVD+R... :)) which ain't that long.

Of course, having a PC at the office that isn't really used over the weekend helps... :p

(Of course, come next weekend I'll encode it once more without GMC since XviD's implementation seems not to be supported by the new Mediatek chipset and I'm planning to buy such a player after christmas... :()

np: Mikkel Metal - Hemper (Schaffelfieber 2 comp.)

[mf]

Originally posted by sysKin
designed for maniacs.
I miss my Motion Precision 7: "mf mode" (http://mf.onthanet.com/XviD_mf-ME.png) :(.

[RexManning]

Okay, this is strange. I just encoded another movie, and here is what I found out:

The Big Lebowski [DVD to XviD 1.0b2]
* downsized from 720x576 to 704x400
* 2pass, QPEL, GMC, QT:MPEG, MSP:6, VHQ:4, ChromaMotion

Office Space [DVD to XviD 1.0b2]
* downsized from 720x576 to 640x352
* same settings

The interesting thing is: while TBL encodes at only 4fps, Office Space is more than ten times faster (55fps). That seems a little strange to me. Ideas, anyone?

regards,
-rex

[sdsalsero]

Maybe because the first (Big Lebowski) was resized to 400, which isn't an even multiple of 32? I know, "it" is only supposed to care about multiples of 16 but 352 *is* divisible by 32 whereas 400 isn't. Can you try redoing Big L at 704x384 ? If that fixes the encode-speed issue, maybe it'll be a legit bug for the developers to fix.

[sysKin]

Originally posted by sdsalsero
Maybe because the first (Big Lebowski) was resized to 400, which isn't an even multiple of 32? I know, "it" is only supposed to care about multiples of 16 but 352 *is* divisible by 32 whereas 400 isn't. Can you try redoing Big L at 704x384 ? If that fixes the encode-speed issue, maybe it'll be a legit bug for the developers to fix. No, it's definitely not it. It might be some gui bug maybe? The difference clearly indicates that something is wrong.

Radek

[cypher_soundz]

i think i should jump in to this thread and 2nd this bug. if we can call it a bug as i have no idea how to reproduce it. everytime i uninstall XviD ans reinstall the first encode is good (~53fps) than it all goes down hill. i am currently getting 7fps :angry: from rush hour although the first encode i did of this film was around 53fps.
regards
cyph

[Gazza]

Did you use autogk or gknot? I have noticed the same high fps if I used gknot or autogk. When using these packages to handle vdmod I noticed that the first pass blistered along at a great pace. It failed when switching to second pass - I then found out that gknot/autogk are incompatible with xvid 1.0 beta's!
Maybe autogk or gknot sets a mode in the frameserver or xvid that produces the high framerate?

Using vdmod manually gives me around 7 to 11 fps for a 1M P3 depending on resolution and filters, etc.....

[cypher_soundz]

Using gknot 0.29 1806 , but i do not think it is why. I think there must be some setting that is stored and what ever we do does not change???
hmm well i dont know lol
Regards
cyph

[sysKin]

Originally posted by cypher_soundz
Using gknot 0.29 1806 , but i do not think it is why.This is why. There is no gknot that is compatible with xvid 1.0. You just can't use it.

Radek

[Danzel]

@mf Is that a real build or did you just photoshop that screenshot? lol
What did putting precision to 7 do, was this an early test of VHQ?

Danzel.

[mf]

Originally posted by Danzel
@mf Is that a real build or did you just photoshop that screenshot? lol
What did putting precision to 7 do, was this an early test of VHQ?

Danzel.
It was a real build, sysKin made it for me http://www.everwicked.com/virtualdub/html/emoticons/wub.gif. It enabled some unused ME thingies, that added like 0.000001dB extra quality, but did cost some speed. I loved that mode. If it ever returns, I want it to be named after me again.

[cypher_soundz]

OK thanks syskin, major PC crash! but after reinstalling i will try manual vdubmod encode.
Regards
cyph

[Rash]

I've just encoded a movie that took 20 hours to finish. The resolution was 640x336, divisible by 16 (336 is not divisible by 32 though). But anyway, Radek said this was not the problem.

I did not encode using GKnot, I simply used it to make the avs script. Anyway, the same movie would encode at about 20fps on my friend. I have a P4 2Ghz and he has an AthlonXP 2400+. I can see that Rex also have a P4. Maybe that is the problem. (?)

[Soulhunter]

Here... (http://forum.doom9.org/showthread.php?s=&threadid=67010) ;)

Bye