Is this encoding speed normal?

[morgensonne]

Hi,

I know it's an old question, but today i wanted to make my first Xvid Encode. I have bin 05/03/02 and my avs loks so:

LoadPlugin("C:\PROGRA~1\GORDIA~1\mpeg2dec.dll")
mpeg2source("E:\DVD Rip\Fantasy\Fantasy.d2v")
crop(4,32,704,512)
BicubicResize(704,352,0.333,0.333)

I use the standard settings for 2-pass encoding (2-pass Int.).
no luma...
i want to make an 2 cd rip, so i took mpeg quant type.

i have an amd thunderbird 1.33 and 512 Infineon SDRam (but only CL3). I use winXP.
My max encoding speed is about 15fps!!!
in dooms codec comparison he has about 27 with an xp1800+ and ddr ram.

Should i change my system to an XP (is SSE the solution?)?

ciao
morgensonne

[Koepi]

Nope.

Since a few days ago user defined quantizer natrices were introduced, the mmx code for that was disabled (it was specialised to the two matrices we had).

You may try my build, which should be a little faster.

Since you encode at an real LARGE resolution (don't start wondering why the quality isn't as amazing as it could be!) it will be slower as well.
I recommand 640xYYY as resolution, then your speed will be amazing I'd say... :)

Regards,
Koepi

[morgensonne]

thanks for your answer...but should i deinstall the old version before i install your new? because the xvid.dll is skipped! or should only the xvid.ac being copied?

thanks

[morgensonne]

i've found the answer in the release notes...not dll update till its necessary!!

okay
ciao

[morgensonne]

after install the version from your homepage 07/03/2002 the encoding speed is much faster (i think the same like befor)!

what 2 matrices you mean?

morgensonne

[Klumsy]

He means the MPEG and the H.263 matrices, which are included in the codec itself.

[morgensonne]

but i have now installed the binary version 05/03/2002 AND reduced the size to 640*xxx BUT my encoding speed is the same and not AMAZING...

ciao

[Koepi]

Uninstall your 5/3/2002 build, the dll only gets updated when it's newer than the present file.

You can easily check that by looking at the "about" tabulator at the codec setup, it should be something like "2.2.2002 (Koepi's Version)" - then you're running the "right", faster binary.

Regards,
Koepi

[avih]

@koepi: maybe an installer option to overwrite newer dll (and perhaps dsf as well)? since ppl are moving back and forth between releases in such frantically great times :) ...

my 2 cents
regards
avi

ps. i thought about the "DirectX SDK decompressor from 2 bytes file" that u mentioned a while ago... unfortunately, as hard as i think, i can't see how you compressed the sdk to less than 3.14159M bytes... :( so i decided to get it the hard way, asked someone to download the stuff and i'll probably have it on sunday, wish me luck with porting to dsf ;)

[Nic]

Hi Avi,

Im probably going to comit my code to the CVS on tuesday (im away this weekend & monday), or if you want to add it to it sooner, I might get chance to email it to you....

Good luck! :)

-Nic

[avih]

hey nic :) thx for the concern, and congrats for your popular dsf ;) ...

anyway, i'm now rewriting my code, and adding some features. i'm in no hurry with the cvs, as i don't want to put in messy code, and my code IS a mess ATM :(

however, if u want a quick feature add, u can add contrast and saturation very "cheaply", just take them from the code i released already (3-mar) (saturation = applying contrast function to u and v).

regarding the other features (MV/histogram), well, if u have the time/will, u can add whatever u like. i didn't touch the code of MV and histogram.

regarding the filters, yours are fine and i don't think we need 2 kinds of deringing filters :)

and finally, hopefully i'll have the sdk on sunday, so i'll start porting my stuff to dsf instead of the awkward configuration as it is now. (i may need your help with that)

gonna b a busy weekend, let's hope i'll finish the rewriting by the time i'll get the sdk.. :)

cheers
avi

ps.
after (if?:) ) i finish the porting, we can/should think of a unified filtering system (i already have few in my latest code), such that filters can be added easyly and without modifying 80% of the code ;). then it might be a good time to merge our code, otherwise, it could be too much work just to make our codes comply with each other.. (note that brightness/contrast/MV/histogram can then be considered as filters as well)

[Nic]

The unified functions is easy enough to do, as the parameters for functions almost always contain the following params:
1) Image component (unsigned char *)
2) width
3) stride
4) height
5) Chroma? (Boolean)

And thats all you ever need really....so its not a problem to add filters....

Cheers,
-Nic

[avih]

what're stride and chroma(bool)?
i think of IMAGE(= y,u,v), width, edged_width, height, and maybe a pointer to the macroblock array, as i have some ideas of filters that depend upon mode (inter/intra/interv4) and motion vectors (i.e. MV visualization). maybe also a pointer to the dec->cur image, since i also have ideas for a filter that will have to write back data to the decoder, such that it's used in the next frames also.

or, instead of just adding parameters, just give a pointer to the DECODER structure. afterall, the filters do reside in a codec, and not plain bitmaps stream. the codec information can be used to produce better filters.

special case of a filter might be an import filter, that will use virtualdub/avisynth/other filters API, and ppl will b able to use their favourite filter.

what do u think?

[LigH]

You lucky guys!

All you having an encoding speed above 10 fps, be proud of it!

My average speed is between 6 and 8 fps on a Duron 800, using DVD2AVI projects in VirtualDub per VFAPI.

The reason? I need to use VirtualDub filters because that kind of filter I need is not available for AviSynth. I once asked for it, but no result: I'd like to have a chrominance enhancing filter, like the H/S/I filter by Donald Graft.

My usual filters and settings:

- Level: 1.4
- H/S/I: 1.2 (saturation)

[Hanty]

I'm at 2-3 fps with my 866Mhz P3, I have 15 hours for every pass.
I blame Smart Smoother, Warp Sharp and smart resize that's really killing my speed. So hey, even 6-7 fps for me would mean I could cut encoding time in 1/2.

[avih]

@hanti: Smart-Smoother = 2D cleaner (optimized)? i got fine results with the latter, if they're not the same, u can try it out.

@nic: also, initialization and destruction should be handled, since some of the filters may need/utilize consistent data structures (i.e. temporal filter)

[Hanty]

avih :

Smart Smoother is an original Filter by Graft, unlike 2D cleaner who is by Casaburi. I however found these interesting figures when looking further into it: ( http://sauron.mordor.net/dgraft/2dcleaner.html )

On one test of a given clip with equivalent settings the following timings were obtained for the Athlon version:

2D Cleaner (original by Jim Casaburi) -- 200 seconds
2D Cleaner (optimized by Jaan Kalda) -- 32 seconds
Smart Smoother -- 83 seconds

Mighty interesting, that's a 60% drop in encoding time (for this particular filter), I'll be all over it like a blanket when I get home from work. Thx!

[Nic]

Your over complicating things Avi ;)

Stride == the number of pixels to the next line == edged_width

Chroma? I.e. are you sending a chroma (UV) or (Y) part to the function

You dont have to make things complicated, writing to the next frame the decoder uses isn't any more difficult than writing to the outputted frame.

Wait till you see my code, it will make it more obvious :)

Cheers,
-Nic

[avih]

@nic: i'll shut up for a while till i c your code, in the mean time i've got my own to handle ;)

@hanty: good luck :)