I'm getting only 35fps when encoding

[Dark_Breaka]

P4 2.4GHZ
512MB
80gig 7200RPM 8MB Cache
Radeon 8500 All-In-Wonder

I'm currently using avisynth to encode to xvid. My problem is that when I use a deinterlacer in my avs script, my encoding speeds drop from 50fps(w/out deinterlace) to 35fps(w/ deinterlace). Is there someone that can help me identify the problem or maybe suggest other deinterlacers.

[stephanV]

processing video takes up time so a drop in encoding speed is normal if you deinterlace. there are scripts that slow the encoding down to 1 fps or something (depending on your hardware specs of course).

its kinda difficult to advice other interlacers as you have not told us which one you are using now :p. there are a few of them mentioned in the avisynth docs though.

[Dark_Breaka]

Here's my script when de-interlacing a 29.97 clip.

video=MPEG2Source("C:\Downloads\Episode Series and etc\Captures\test.d2v")
audio=MPaSource("C:\Downloads\Episode Series and etc\Captures\test MPA T01 DELAY 0ms.mpa")
AudioDub(video, audio)
dgbob(order=1,mode=0)
Crop(0,0,-0,-4)
SimpleResize(512,384)

I've configured xvid for the fastest possible encoding, i won't get into details about that. But this is what I have so far. I drop 15fps when I use a deinterlacer. I've also tried this on another PC with the same specs as me and the result was almost identical.

[Sharktooth]

It's perfectly normal...

[Teegedeck]

Actually this is something like a 'my Porsche drops to 200 mph when I drive uphill'-kinda-problem. :p

(who am I to speak, encoding with an AMD64...)

[Dark_Breaka]

But someone i know can hit 50fps with the same script on a 2.4ghz.

[Teegedeck]

There's an abundance of possible explanations; faster memory; a different built; or - most simply - different XviD settings somewhere where it perhaps escaped your attention. Oh; and of course it might be just the different content you're encoding. A game of soccer will most probably take longer to encode than a gardening-show.

[stephanV]

its not that encoding speed is a constant... during encodings the speed goes up and down all the time, so its quite possible he got 50 fps somewhere during the encoding.

[Soulhunter]

Originally posted by Teegedeck
Actually this is something like a 'my Porsche drops to 200 mph when I drive uphill'-kinda-problem. :p
Lol... :D :D :D

Gonna save this in my "nice quotes archive" under -> compares !!!


Bye

[Teegedeck]

@Dark_Breaka: Just a blind guess:
Use

video=MPEG2Source("C:\Downloads\Episode Series and etc\Captures\test.d2v",idct=5 )

in order to make use of the p4's sse2 capabilities. If that ain't fast enough, try idct=6.

Also try if

Crop(0,0,-0,-4,align=true )

makes any positive difference.

[SeeMoreDigital]

You want to try generating XviD encodes using anamorphic pixel frame sizes of say 720x576, or true 16:9 frame sizes of 1024x576 before you start complaining about encoding speeds ;)

35fps at 512x384 (4:3) ain't too bad for an P4 2.4Ghz!


Cheers

[Teegedeck]

Hm-hm; I get about 6-10 fps at 704x560 (TV-series) at highest quality with the Athlon64 @ 2.2 Ghz. (I knew it was time for an upgrade when my old PC's speed dropped below 1 fps...) Am I crazy or what?

[SeeMoreDigital]

Originally posted by Teegedeck
...Am I crazy or what? How does one answer that without getting striked?

Are you thinking of upgrading Teegedeck?


Cheers

[Dark_Breaka]

Originally posted by Teegedeck
@Dark_Breaka: Just a blind guess:
Use

video=MPEG2Source("C:\Downloads\Episode Series and etc\Captures\test.d2v",idct=5 )

in order to make use of the p4's sse2 capabilities. If that ain't fast enough, try idct=6.

Also try if

Crop(0,0,-0,-4,align=true )

makes any positive difference.

Damn, really thought that this would increase FPS. I get the same 35FPS with these settings.

[Teegedeck]

With all that OT-talk by all rights I should've striked myself!

[SeeMoreDigital]

Hmmm! I've currently got an 2.8 P4. But those 3.4 P4's sure look tempting.... I wonder how well they over-clock?


Cheers

[Teegedeck]

I'd wait till Intel introduces the innovations from their mobile-CPUs into their desktop product line as promised.

[ChronoCross]

All I can say is I hate you :mad: stop complaining about 35fps. lol I'm just kidding of course I don't hate you. lets just say I go from 21fps encoding with 0 filers just loading an avi to 7fps when I add a deinterlacer. so GRR lol

[Boulder]

Originally posted by Dark_Breaka
Here's my script when de-interlacing a 29.97 clip.

video=MPEG2Source("C:\Downloads\Episode Series and etc\Captures\test.d2v")
audio=MPaSource("C:\Downloads\Episode Series and etc\Captures\test MPA T01 DELAY 0ms.mpa")
AudioDub(video, audio)
dgbob(order=1,mode=0)
Crop(0,0,-0,-4)
SimpleResize(512,384)

I've configured xvid for the fastest possible encoding, i won't get into details about that. But this is what I have so far. I drop 15fps when I use a deinterlacer. I've also tried this on another PC with the same specs as me and the result was almost identical.

Use KernelDeint() instead of DGBob(), there's an MMX optimized version being discussed in the Avisynth usage forum. You could try KernelDeint(order=1,sharp=true,threshold=7). Many people feel that KD is the most efficient (note, I didn't say the best:D ) one for pure interlaced streams at the moment.

[GrofLuigi]

Maybe not entirely related, but I have always found out that the biggest limiting factor to my encodes is the speed of the hard disks. Just ask yourself how long does it take to read a big file CONTINUOUSLY for a large period of time. Although harddisks are getting faster over time, the usual sources are not that small either (lossles captures or DVDs, for example).

Just my thoughts...

GL