Curious what your encode times are like

[neoreturns]

Computer specs:

Epox 8RDA+
Athlon XP 1700+ overclock to 2.4 Ghz (200x12)
2x512 PC3200 @ 200 mhz

And it seems with 2 pass my average encode time is right around 1:45-2:20 with most movies

Just curious how fast you guys encode....computer specs and times please

[mf]

Average fps is a more universal way of measuring encoding speed. Mine go at about 8-12fps.

[epere4]

Using XviD (old version) I get 2-5 fps :(
DivX is faster (around 10 fps), but I think the XviD quality is better and worth the time.

(I have an Athlon 700 Mhz, 256 MB PC133 RAM)

Edit: Added my RAM memory to my computer data

[mf]

Oh yeah I forgot. My rig is an Athlon 2500+ (barton), with 1gb dual-channel DDR ram.

[Tuesday]

My rig is a decaying Athlon TBird 1.2 o/c'd at 1.4Ghz, i generally use some form of denoising in my avs and 3-passes with DivX 5.1.1 at the slowest setting which gets me 1-3fps, so rips usually take about 3-4 Days :D

[colordog]

I have an Intel P4 HT @ 2.4GHz, 1GB of Dual-channel DDR-400 RAM, Intel 865 MB chipset. Use DivX 5.1.1, with B-frames, on "slower" setting, fast psychovis. I get ~14-16 FPS.

[KpeX]

P4 @ 1.99 Ghz, 768 MB ram

XviD 1.0 Beta, ASP features, VHQ 2, Adaptive quant, 640x272 with no filtering, approximately 6-7 fps.

[DevilsChild]

Athlon 2600+ with 512 MB of RAM:

XviD 24062003-1 gives ~8 fps with Motion Search 6, MPEG quants, Qpel, Chroma, GMC, and 3 max B-frames. Default settings on AutoGK give me 20-30 fps (4-5 hours per movie).

I get 5-10 fps using DivX5 on the "slowest" quality setting with fast psychovisuals.

AutoRV9 gives ~3 fps (10-15 hours/movie) using 2-pass VBR, Sharpest Motion, Very High EHQ, and "Improve High Motion Scene".

[Brother John]

P2 400 MHz. Have thought of offering it to a museum ;)

Commonly around 4-5 fps with DivX 5.1.1, standard mode + b-frames and without filters (well, noise filter maybe). That makes about 20-24 hours per movie. I'm really glad the computer is not in my bedroom.

[ppera2]

Originally posted by neoreturns
Computer specs:
Epox 8RDA+
Athlon XP 1700+ overclock to 2.4 Ghz (200x12)
2x512 PC3200 @ 200 mhz
And it seems with 2 pass my average encode time is right around 1:45-2:20 with most movies
Just curious how fast you guys encode....computer specs and times please

That's fine, but you should get more info - at least codec and it's settings. And speed depends much from source (res.) and output res. too...

My average two pass time is about 3 hours (XP1700 @ 1850MHz, 512MB PC2100)

[mikeson]

My rig:
Asus P4P800
P4 2.6Ghz @ 3.1Ghz with HT
1GB RAM dual-channel DDR

My frameserver
- AviSynth 2.5.3
- Crop, LanczosResize
- Limiter
- ConvertToYUY2 and then back to ConvertToYV12 when using Dust
- 60% encodings with Dust (FaeryDust) :)
- 20% encodings with VagueDenoiser
- 20% encodings with MipSmooth

My encoder:
- Latest (or 1-2 day old) dev-api-4 CVS build in MSVC6
- MSP6, VHQ4, Chroma motion, Trellis quantization, Adaptive quantization, MPEG quantization type, Qpel, GMC, B-frames (2/1.50/1.00), Chroma optimizer
- usually encoding resolution like 720x288 and 720x304 (16:9), or 512x384 (4:3)

FPS
- encoded movie: Lord of the Rings: The Two Towers with resolution 720x288
- with Dust filtering: 3-5 fps, CPU load around 90%
- with VagueDenoiser filtering: 5-7 fps, CPU load around 60%-80%
- with MipSmooth filtering: 5-9 fps, CPU load around 60%-70%

[Soulhunter]

CPU: Athlon 2600XP | RAM: 512MB DDR400


DivX 5.1.1 with PAL (25fps) source

Quant2 / Standard / DVD Res. = Runs nearly in realtime speed

Quant2 / Standard / 1024x576 Res. = 30% longer than the movie

Quant2 / Slowest / 1024x576 Res. = 10x the movie duration


XviD v.1 Beta2 with PAL (25fps) source

Quant2 / VHQ1 / 1024x576 Res. = A bit more tahn 2x movie duration

Quant2 / VHQ4 / 1024x576 Res. = 7x movie duration


Any codec and any source with one of mf's scripts = +/- 1 Week !!! :D :D :D

Bye

[Fantasma]

Computer specifications:

Athlon XP 2400+
384 Megabytes Ram DDR SDRAM 266 (Motherboard KT4 Ultra with VIA Chip)
60 Gigabytes Hard disk (Maxtor)
Codec: DivxPro 5.0

30 Frames per second with no filter processing - First Pass
40 Frames per second - second Pass*

*(The increase of speed during the second pass is due to the use of binary file MVInfo.bin used by the DivX Codec)

Gracias.

[cypher_soundz]

xvid (200312202140 )latest from http://xvid.gamrdev.com/
rig below , with qpel, b-frames,trelis, 704x288 from pal 16:9,mpeg matrix.

avs:
crop(4,74,710,424)
BicubicResize(704,288,0,0.5)
Undot()
Temporalsoften(2,3,3,mode=2,scenechange=6)
mergechroma(blur(1.3))
FluxSmooth(5,7)

~24fps

(my computer is a little trashed though lol)
been getting 53fps on ciao.

[Kb_cruncher]

MY RIG

-P4 2.4Gig HT OCed to 3Gig
-512Mb PC500
-Abit IC7-G

MY ENCODE SETTINGS

-AVISYNTH - idct=5,UnDot, c3d(MovieHQ), 640-688 vertical res,filters before resize
-XviD1.0beta2 - VHQ1, ChromaMotion, Trellis, BFrames(2,1.75,1.25)
-Vdub - Fast recompress,no preview.

I get 18FPS average.VHQ and QPel are the speed killers i think, resize before filtering too but give much better quality.

Unfilterd and everything off i can get 50+ FPS.

[mikeson]

But with last CVS build, it is all different... ;)

[cypher_soundz]

i found the last build on http://xvid.gamrdev.com/ (200312210320) to be the same speed, due to the way it was compiled, are you talking about another build?

[mikeson]

@cypher_soundz:

I'm talking about FAST1PASS feature that has been implemented few days ago. First pass is significantly faster. Have a look at changelog in CVS.

[cypher_soundz]

oooh! sounds nice ;) will have to try this, still not on http://xvid.gamrdev.com/ or am i missing it somewere? lol
Regards
cyph

[Tom|420]

P3 500

With a average size video (say around 640x480)
XviD
Audio not counted (usually I re-encode audio to Ogg using external software, not the same as the one used for video)
between 8-12 fps, 10 fps on average

Just tested to verify that number, to be sure the numbers in my head weren't out of my imagination.

On average I calculate about 1:15 hour for a full CD re-encoding. Most of the time I do an aspect ratio readjustment because I like the actual video to be the correct ratio, eventhough my player could do that on the fly, which would decrease the speed by a small amount.