Long converting time in tmpg

[mark1969]

Hi all

I'm converting a .avi downloaded movie with tmpg, 23.976fps mpeg4.

I've loaded the ntsc film template and tried changing the enviroment settings,
but I'm still getting a coding time of 142 + hours.

I want the film but not that much!! Any ideas?

Thanks

Mark

[mb571]

The most relevant piece of info in time to encode with TMPGEnc is the CPU speed.
My 1.5 GHz Cpu will do 50 mins of SVCD in around 50 minutes.
My friends 1.0 GHz machine takes around 2 hours.
My old P166 would take a week.

So the question is, What Cpu speed are you dealing with?

Mark

[Gazorgan]

Don't do the highest search precision, this adds time but not quality. Try second or 3rd highest, or even normal. Even with a PIII 450, it shouldn't take more than 24 hours. by the way, just because the estimate says 142 hours, doesn't mean it will take that long. Mine usually starts at 12 and it takes 3.

[puertorican138]

Mine usually starts at 12 and it takes 3.

That's what it does on mine's also.

[ZippyP.]

Are you using any filters, noise etc.? They add a lot of time.

[Bravoxena]

mb571: My 1.5 GHz Cpu will do 50 mins of SVCD in around 50 minutes.
My friends 1.0 GHz machine takes around 2 hours.
My old P166 would take a week.

You actually tried encoding on a P1!? I wouldn't touch that with a 10 foot pole!

[mb571]

I'll try most things once. Har Har

Mark

""Try not. Do, or do not. There is no try."

[Treebeard]

mb571: My 1.5 GHz Cpu will do 50 mins of SVCD in around 50 minutes.
My friends 1.0 GHz machine takes around 2 hours.
My old P166 would take a week.

You actually tried encoding on a P1!? I wouldn't touch that with a 10 foot pole!

I've heard of people encoding on a P1, but has anybody ever tried w/ a 486 machine? or is the software even compatable.

[puertorican138]

Are you using any filters, noise etc.? They add a lot of time.

Especially Noise Reduction. Man, it can quadruple your encoding time!!!

[vhelp]

mark1969,

wow, 142 hours IS a long time. But, if you have a very slow pc, you're
in for long waits.

Some things you might want to consider:
* faster pc - start w/ min. of AMD 1700+ 256MB ram or higher (better)
* adding a little more ram wont hirt, and might help speed things up (only
..if you have very little ram to begin with) but remember, if you are doing
..any frameserving, from what I understand, AVIsynth is very memory
..hogging and has some leaks - people have complained of memory increasing
..exponetially (don't know if that's 100% true though, but something to
..consider)
* turn off any "noise reduction" processes in your encoding (if any)

Might help if you lay down your steps from start to finish so we can see
what exactly is it that is causing your COMMA !!

-vhelp

[mark1969]

Hi all

Thanks for your replies, my computer ain't the best its a pent 3, 733mhz, 512 mb ram, I'm still a real newbie but I've encoded about 10 movies and the normally take about 8 hours, thats why i was so shocked at 142 hours.

I've tried several things different settings etc ,and i'm still getting a real long encoding time, so i reckon its time to scrap it.

Thanks again

Mark

[mats.hogberg]

Have you actually encoded it, and it took 142 hours, or does TMPGEnc say it will take 142 hours? If the latter, then I've read somewhere that TMPGEnc may screw this estimate up under some conditions (was it VBR audio in the source stream?).

/Mats

[2man]

well
time in tmpg is 2~3 hours to encode 90min movie (avi)
time in tmpg is 3~5 hours to encode 90min movie (d2v)
using avs frameserve w/filters (unfilter, fluxmooth, nomosmooth, legalclip, and 2more) and w/Kwag template at 100% quality(300-1350)
on a pc p4 1,7/512dimm/120gbIBM
now after install the directx 9.0 it takes >12hours to encode a 90min (d2v) using the same avs script and i have to unselect directshow in tmpg
but i will install readavs.dll again a give another try
the quality is always super HQ xvcd(mpg2) movie
and i burn as a svcd w/svcd subs and 2 tracks