How 2 configure TMPGEnc 4 fastest performance?

[daamon]

Hi,

I've recently upgraded to a new PC and wanted to know what the best settings are (now) to make sure I'm making the best use of the machine's resources (HT P4 3.0GHZ CPU) while encoding. You can see my PC specs in "Computure Details".

I create basic titles, use DV AVI and the odd JPEG in Adobe Premiere 6.0 and then use Debugmode Frameserver to frameserve to TMPGEnc (RGB24). I do the video only. In TMPGEnc, I set the "Motion search precision" to "High (slow)". I know this impacts the time, but that's where I want the quality.

I typically use VBR- max: 9,000kbps; avg = 6,000kbps; min = 500kbps. Again, I know that this impacts the time but that's where I want the quality.

I've done loads of searching in the forums (what do you search for to get a reasonably unique match?) and not found anything. I've looked through the guides and found this one by lordsmurf and set up TMPGEnc accordingly.

I also set the process priority in Task Manager to "High" for both TMPGEnc and Premiere. Before encoding, I close all non-essential processes and disconnect from the net.

I've done rough test encodes that suggested 2-3 x realtime, but I haven't tried this on a decent length clip. I thought I'd post and ask to get the ball rollling... I was kinda hoping for near realtime or 1.5 x realtime. Is this unrealistic?

So, thoughts / suggestions for improvement? (Excluding the settings I've mentioned above that I want as they are).

EDIT: Additional note - I monitor Task Manager and the CPU runs around 90 - 98%. This is rougly split equally between the tmpgenc.exe process, and the premiere.exe process. Does this suggest that I'm getting the best already?

Mem usage (I think) doesn't look to heavy. But I may be looking at the wrong figure, not quite sure which one...

Thanks... Daamon.

[deckard8]

I use Motion Estimate Search (very fast) and I really can't see any different between that and High (slow) quality mode. I dont think the extra 2x encoding time is justified for high quality mode.

[daamon]

Hi deckard8,

I'll try a test encode for each and see what I think.

Anyone any thoughts on other settings for optimisation?

[Gillies]

set ur tast priority in options to high and if ur really eager set ur task priority in the task manager to realtime. however the task manager setting will mean everything else will crawl and can crash ur computer. i usually only set the tmpgenc priority and leave it.
ps. make sure uv got hyper threading running in ur bios

[daamon]

Hi Gillies,

I know how to get into the BIOS at startup, but what / where am I looking for to see if hyper threading is running.

If it's not, is it an obvious setting to make?

See additional note in original post...

[Skynet107]

Setting the priority of a process will not speed it up more than 1%. Encoding is very CPU intensive, the encoding process requires a certain number of CPU cycles, this is something that cannot be changed. Nothing you do will speed up the encoding short of getting a faster computer.

Frameserving (especially from Premiere) slows down the process even more because the CPU cycles are being shared between Premiere, the frame server, AND the encoder. TMPGEnc is known for being slow as it is, frameserving to it makes it even slower.

[jimmalenko]

Hi Daamon,

I've got basically the same box as you so hopefully some of these tips might assist:

1. Motion Estimate Search will be fine for DV source, and will improve your times a lot.

2. Set TMPGEnc's Task priority (both when active and when idle) to high.

3. If you know much about the insides of your box, make sure that your RAM is in slots 1 & 3 or 2 & 4, and not in adjacent slots. This enables the DDR capability to work properly and can make improve your performance around 20% IMO.

4. Don't use any filters within TMPGenc unless you really desperately need to. I would suggest getting to know AVISynth, as it's filters are better IMO then the TMPGEnc ones, and are also much quicker.

[daamon]

Hi jimmalenko,

I was hoping you'd pitch, I was gonna PM you to ask your opinion.

1. OK - I'll check it out.

2. Done, though not tested.

3. OK - I'll have a look.

4. Never needed to use filters - it's all from my miniDV cam. Useful to know that Avisythn is better and quicker though.

Cheers.

P.S. How's "the project" coming along? I won't name it - it's your baby to reveal when you see fit...

[jimmalenko]

How's "the project" coming along? I won't name it - it's your baby to reveal when you see fit...

Going good. I haven't done much work on it since yesterday morning because I had my work's christmas party in Bendigo last night and I've only just got home. The head feels a little heavy ATM, so I might just watch the aussies pump the kiwis in the cricket for the rest of the day I think.

[daamon]

Ha ha... I've Skyped you on that one...

Returning to the thread, do you know how to see if hyperthreading is running in the BIOS? I don't want to go poking around unless I know what I'm doing / looking for.

Ta.

[jimmalenko]

Returning to the thread, do you know how to see if hyperthreading is running in the BIOS? I don't want to go poking around unless I know what I'm doing / looking for.

On my motherboard it's in the Advanced BIOS Settings, and there's an entry called CPU Hyperthreading, which should be set to enabled. I'd be pretty confident that centrecom would have set that for you already though

[daamon]

Cheers... I'll check it out.

I though that too (about CentreCom). Hey, wait a minute, how d'you know I got it from there

[jimmalenko]

I though that too (about CentreCom). Hey, wait a minute, how d'you know I got it from there

I know everything about you. In fact, I could see the centrecom sticker on the front of your tower

That's a nice t-shirt you're wearing today, BTW

[daamon]

"jimmalenko" - Is your real name Bill?

There's even a film about you...