TMPGEnc Processing Time VS Processor Speed

[MickeyD]

I quickly browsed through the thread so I apologize if this has already been mentioned.

When I use TMPGEnc to encode I minimize EVERYTHING else. When everything is minimized and TMPGEnc is running in the foreground I get pretty good speeds.

I can encode a .5GB file in about an hour or so when I do it this way. If I start the encode then bring up the internet or whatever that time can jump to umpteen hours real fast. That makes sense because of CPU time, but if I'm running an app or p2p that's minimized I get good encoding times. I don't know why it works, but it does for me.

[txpharoah]

Syphic wrote:
Why dont youy all use Main Concept encoder. Seems to work faster.

Yep, faster than Tmpgenc, but IMHO, quality not quite as good.

thank god! I thought I was the only one.. I'm not alone in the wilderness...

Hear, hear! I'll drink to that! MC seems blurry to me.

[hwoodwar]

Curritch:

I scanned through all of the replies and I didn't see one thing specifically mentioned (there is a slight chance I missed it): You are using Highest Quality Motion Search Precision. It has been my experience that by just changing that setting to "High Quality" it will reduce the encode time 20-40 percent (IE a 10 hour encode (Highest Quality) down to 6-8 hours (High Quality)) and I personally cannot tell any quality difference between the two.


My own system

P4 2.0 gig overclocked to 2.4 gig
512K PC2700 DDR RAM
one 120gig 7200 RPM 8gig cache Western Digital hard drive
one 200gig 7200 RPM 8gig cache Western Digital hard drive

During encodes I leave Norton Antivirus and ZoneAlarm (temporarily set to "Stop all Internet activity") running.

I capture from cable TV at 352 x 480 resolution to avi using VirtualDub and the HuffyUV codec. Then after I cut out the commercials I have about 44 minutes left. I do ocasionally use a few filters, applying them in VirtualDub and then resaving to a different avi file.

I do not use any filters in the encoding process.

I encode in TMPGenc using one of KWAG's older SKVCD templates to 352 x 480 resolution, 2-Pass VBR (bitrate settings generally 1000/2350/4000) and High Quality Motion Search Precision. Using these settings on my system it generally takes about 2 hours 20 minutes to finish the 44 minutes encode. When running any other programs simultaneously the encode time is lengthened.