Log in

View Full Version : XviD Video rendering rate with Core 2 Duo


Jip
20th August 2006, 10:28
I just switched from an Athlon XP 2200+ to an Intel Core 2 Duo 6300. I expected to get higher rendering rates for XviD encoding, but they are all most the same. I use the XviD MT version and put threads on 2. The frame rate I get in the first pass is around 30 fps and in the second pass it’s 25 fps. I use an mpeg2 file as source in VirtualDubMOD.

I wonder if this is normal or that I’m doing something completely wrong. Are there any people who have better frame rates or have any advice?

Thanks in advance!

Manao
20th August 2006, 12:38
What are the encoding settings ? What is the resolution ? Where did you get the XviD build ? How much speed difference is there between one and two threads on the Duo Core ? Were you loading an avs script or directly the mpeg2 file ? If there was an avs script, can you paste it there ?

I doubt the results you're getting are normal, but without those information, it's only a gut feeling.

Jip
20th August 2006, 14:09
Mmm… your questions all ready made me think.
What I did was drop the mpeg file directly in VirtualDubMOD, add deinterlace and resize filter and set XviD to 1-pass and 2-pass and started the jobs.
Now I’ve created an AVS file with help of GKnot, first pass gives me 70 fps, second one 35 fps. I think that’s more like it! :)

When I set threads to 1, I get first pass 40-50 fps and second 20-30.

XviD version: 1.2-127 (Koepi's CVS Build)

Here is the AVS file, maybe it can be even better?


# Created with Gordian Knot
#
# http://gknot.doom9.org

# PLUGINS
LoadPlugin("C:\PROGRA~1\GORDIA~1\DGMPGDec\DGDecode.dll")
#LoadPlugin("C:\PROGRA~1\GORDIA~1\AviSynthPlugins\decomb.dll")
#LoadPlugin("C:\PROGRA~1\GORDIA~1\AviSynthPlugins\KernelDeInt.dll")
LoadPlugin("C:\PROGRA~1\GORDIA~1\AviSynthPlugins\UnDot.dll")
#LoadPlugin("C:\PROGRA~1\GORDIA~1\AviSynthPlugins\dgbob.dll")
#LoadPlugin("C:\PROGRA~1\GORDIA~1\AviSynthPlugins\Convolution3d.dll")
#LoadPlugin("C:\PROGRA~1\GORDIA~1\AviSynthPlugins\FluxSmooth.dll")
#LoadPlugin("C:\PROGRA~1\GORDIA~1\AviSynthPlugins\TomsMoComp.dll")
#LoadPlugin("C:\PROGRA~1\GORDIA~1\AviSynthPlugins\VSFilter.dll")
#LoadPlugin("C:\PROGRA~1\GORDIA~1\AviSynthPlugins\SimpleResize.dll")

# SOURCE
mpeg2source("D:\--=Montage\temp\M2U00019-1.d2v")

# TRIM
#trim(startframe,endframe)

# IVTC
#Telecide(order=1,guide=1).Decimate()
# or use
#IVTC(44,11,95)
#GreedyHMA(1,0,4,0,0,0,0,0)

# DEINTERLACING (1)
#FieldDeinterlace()
#FieldDeinterlace(blend=false)
#TomsMoComp(1,5,1)

# DEINTERLACING (2)
#KernelDeInt(order=1,sharp=true)
# or maybe
#DGBob(order=1,mode=0)

# DEINTERLACING (3) - special requests
#GreedyHMA(1,0,0,0,0,0,0,0)
#Telecide()
#SeparateFields()

# CROPPING
crop(0,0,718,572)

# SUBTITLES
#VobSub("FileName")

# RESIZING
LanczosResize(640,352)

# DENOISING: choose one combination (or none)
Undot()

# 1) little noise
#Temporalsoften(2,3,3,mode=2,scenechange=6)
#mergechroma(blur(1.3))
#FluxSmoothST(5,7)

# 2) medium noise
#Temporalsoften(3,5,5,mode=2,scenechange=10)
#Convolution3d("moviehq")
#FluxSmoothST(7,7)

# 3) heavy noise
#Temporalsoften(4,8,8,mode=2,scenechange=10)
#Convolution3d("movielq")
#FluxSmoothST(10,15)

# BORDERS
#AddBorders(left,top,right,bottom)

# COMPRESSIBILITY CHECK
# !!!!Snip Size now has to be 14 for use in GKnot!
#SelectRangeEvery(280,14)

# FOOL CCEnc
#empty = BlankClip()
#AudioDub(last,empty)

Manao
20th August 2006, 17:22
Several things still :
- you forgot the encoding settings
- you deinterlaced with virtualdubmod, but the avisynth script you pasted doesn't deinterlace
- you might want to use virtualdub 1.6 instead of virtualdubmod ( vdub 1.6 read the input in a separate thread, perhaps vdubmod doesn't - actually i don't know )

The speed increase for the second pass should be greater than the speed increase in the first pass, so i think there's still a problem somehow.

idiotunes
23rd August 2006, 16:57
question;

is 9-14fps normal for Xvid on a 3.06ghz P4 HT with 1GB Ram? VHQ and MSP are on max as well, turbo mode is on, chroma, and vhq for b frames , AQ is on, Qpel is on, GMC is off, chroma optimiser is on, and encoding @ q3 single pass, encoding resolution is 720x416

iNFO-DVD
23rd August 2006, 20:03
is 9-14fps normal for.............
Not all the setting where given but I tried to copy that as much as possible (using a 3GHz P4 HT) and yes, your FPS seems right.

idiotunes
23rd August 2006, 20:27
hmm, ok

would multithreaded xvid help me any?

iNFO-DVD
24th August 2006, 00:21
To be honest I've tried it a couple of times and not gained any speed at all, maybe it's just for real duals, dunno????

henryho_hk
24th August 2006, 07:07
question;

is 9-14fps normal for Xvid on a 3.06ghz P4 HT with 1GB Ram? VHQ and MSP are on max as well, turbo mode is on, chroma, and vhq for b frames , AQ is on, Qpel is on, GMC is off, chroma optimiser is on, and encoding @ q3 single pass, encoding resolution is 720x416

VHQ=4 is a speed killer.

Try:

Matrix=6of9 or HRv3
Turbo=Off
Trellis=On
MSP=6
VHQ=1
VHQ for B=On
AQ=Off
Chroma Optimizer=On
Chroma Motion=On
QPel=On
GMC=Off
Single Pass Q=4

Resize-then-Deinterlace is horrible. My usual practice is Field Based Deblock -> Deinterlace -> Crop&Resize -> Denoise, all inside Avisynth.

idiotunes
24th August 2006, 12:45
i've found that de-interlace artifacting isnt as bad if i blow the picture up to 1024x576 and crop from there.

though i get awful rendering rates, 6-8fps

idiotunes
24th August 2006, 12:50
henryho, what kind of file size average does that do?
i use q3 because anything below that always looked somewhat blocky to me. what effect can happen by lowering VHQ?

henryho_hk
25th August 2006, 01:08
henryho, what kind of file size average does that do?

I don't know the average size either. The filesize is a product of the source material's complexity, the encoder settings (bitrates/quantizers, matrices, etc.) and your desired quality (resolution, clarity, etc.). Every encode is a struggle between these factors. ;)

Teegdeck has shown us some excellent presets. Your can utilize them through MeGUI. The idea is to use a 5% compression test to check the source complexity again a desired bitrate. Then based on the compr test result, choose a suitable 2-pass XviD setting. I would call it a 2.05 pass XviD encode. :cool:

For your 720x410 encodes, I think 1600kbps is a good starting point and I guess it would probably has a comp test score of 45~40. Just remember to keep all deinterlace, resize, denoise, etc. steps in AVISynth.