TPMGEnc Batch Encoding

[xuy_98]

Does anyone know how TMPGEnc batch encoding work? I can't make it work. It quits after each job. I am not sure whether the functin is disabled in triad version or not.

Now I am using P4 3.0, SCSI HD, 2GMB.

The program quits silently just after finishing the first pass very often. 2 out of 5 at least.

What a trial experience TMPGEnc wants to give users! Terriable!

I am not sure whether I should spend money on this program or not.

[jimmalenko]

Does anyone know how TMPGEnc batch encoding work? I can't make it work. It quits after each job. I am not sure whether the functin is disabled in triad version or not.

I can guarantee you that the batch fucntion works. I hope you mean trial version too, and not some asian mob gang version

Now I am using P4 3.0, SCSI HD, 2GMB.

What's that, 2 giga mega bytes of RAM ???

What a trial experience TMPGEnc wants to give users! Terriable!

I am not sure whether I should spend money on this program or not.

It is well worth spending your money on it. I think you need to stop the PICNIC first though.

[xuy_98]

I download the trial version from TMPGEnc website, latest 2.521...

I created different settings to process avi files ranged from 40MB to 500MB for testing.

Basically I used 2 pass VBR plus nosie filter with other different settings.

I couldn't process 300MB avi on my IBM ThinkPad P4. The program constantly quits after 1st pass is done. I don't know what's going on. Then I tested on my desktop (P4 3.0/2GB not 2GMB:>). A little better. But still 2 out of 5 failure.

I heard people have some kinds of problems with TMPGEnc. I still couldn't figure out why the batch encode couldn't work. I have over 40 samples I want to test.

[vcdforme]

1.Open program
2.Load avi
3.select encoding choice
4.save
5.select batch encode
6.load what you saved
7.run

[jimmalenko]

You shouldn't be using the filters unless you really have to IMO. AVIs could be giving you the trouble also, especially if they have VBR audio. Have you a MPEG that you could run through it, trimmed to about 1 minute duration, no filters, 2-Pass VBR in batch mode to test ???

[xuy_98]

Thanks. I am going to try some simple tasks to test batch encoding.

I did find it took 40 minutes to process 2.5 minutes avi. So I am not surprised people are warned for 60 hours for processing a movie. :>.

So you are saying filter and avi does not get along with well?

Ok well I will try without filter.

[jimmalenko]

So you are saying filter and avi does not get along with well?

No I'm not saying that. Both are separate issues with TMPGEnc.

AVIs can cause problems with TMPGEnc in general if the have VBR audio. To check, use VirtualDub to open your AVI. You will get a warning saying that the video has VBR audio. If you don't get a warning then it isn't VBR.

Filters should only be used when they really have to be because of the extra time some of them will add to the encode.

[xuy_98]

Ok the batch encoding only works for samll avi files like 10 - 20MB. Also only two files can be batch processed.

When processing an avi file and its size exceeds 40MB, it quits after processing.

I am not sure whether the problem I ran into is trial version only or it exists in the registered version.

The support is awful. TMPGEnc should mention what the trial version limits are except expriation. Or TMPGEnc does have the problem I have.

Bascially I cannot run the program on my IBM ThinkPad P4 2.0MHz. It always quits or throws an exception after the first pass. What a program it is. It's like a toy. No reliability. Not user friendly.

[flaninacupboard]

i'll warn you now, if you carry on baselessly critcising tmpgenc you'll get heavily flamed.

i am going to wildy assume that your .avi clips are divx or xvid format. both of those codecs are hacks. .avi was never meant to be used in that way, and in paticular, downloaded divx and xvid files will have major problems. try scanning your avi's for bad frames and checking what type of audio is used before you blame tmgpenc.

[hwoodwar]

xuy_98:

I'm not sure about the latest version (I am running 2.52 I believe) but I have set as many as six encodes in the batch encode and had it work fine.

Also, you mentioned "So I am not surprised people are warned for 60 hours for processing a movie." Those times would be on "slow" systems, systems not optimized for video encoding, or people using filters, or resizing.

I have two systems that I run TMPGEnc on (P4 2gig, 512meg RAM and a Athlon XP 2000+ 384meg RAM.) Both of these with no, resizing or filters take about 6-8 hours using 2-Pass VBR to encode a two hour AVI to MPEG-2 format. With the 3ghz system you have I would expect the encoding time to drop by about an hour.

[jimmalenko]

It is either the programs/codecs you have installed on your PC, something you are doing but not telling us or a problem with the files you are trying to run through it. Sometimes certain programs just don't work with certain setups. I can assure you that it is not the software's fault, as there are so many users of this software that don't experience these problems. It is rated as probably the best MPEG encoder for quality and options.

Ok the batch encoding only works for samll avi files like 10 - 20MB. Also only two files can be batch processed.

I have had 14 files in there and let it run. It took 2 days but worked without a problem.

When processing an avi file and its size exceeds 40MB, it quits after processing.

This indicates to me that there is something wrong with that particular file. I have run DV through it (6 hour AVI, so about 78GB file) with no dramas.

I am not sure whether the problem I ran into is trial version only or it exists in the registered version.

Are you using the Free version or the trial version of TMPGEnc Plus ?
version 2.521.58.169 ?

The support is awful. TMPGEnc should mention what the trial version limits are except expriation. Or TMPGEnc does have the problem I have.

It does mention what the limits are. MPEG-2 Encoding for 30 days. That is the only restriction.

Bascially I cannot run the program on my IBM ThinkPad P4 2.0MHz. It always quits or throws an exception after the first pass. What a program it is. It's like a toy. No reliability. Not user friendly.

You might want to add "...for me..." at the end of this statement.

Have you tried running these same files through in normal (not batch) mode ?

Have you tried running MPEG files through it ?

Are you running poor quality DivX/XviD downloaded movies/TV shows through it ?

If you don't have any success trying these things then you might have to look for another encoder.

[lordsmurf]

I just finished some 60-hour batches.

You need to be sure the source is good. Sounds bad, especially downloads of DIVX/XVID.

Set the software up correctly and use good settings. My site has more info on that (www.digitalFAQ.com).

Most of my encodes are realtime for 352x480, ½x realtime for 352x240, and 2x realtime on 720x408. Adding filters can make it take 2x-7x longer, depending on what's used. The heaviest filters can make it 7x on HIGH MOTION setting.

[xuy_98]

Some clarification:

Source: captured DV (home video) from Sony Camcorder using VS7 and VS8. According to VC7, no drop frame, and saved as Type I avi.

Target: NTSC DVD using TMPGEnc 2 VBR + noise reduce filter

Testing platform: IBM ThinPad P4 2.0 MHz 512MB; HP P4 3.0MHz SCSI HD, 2GB

Results:
Batch processing of avi works only when the first file is less than 20MB and the total in queue is no more than 40MB. Batch processing of mpeg works fine.

It quits silently or throws exception after 1st pass on ThinkPad 60% of time. But it works 2nd time for the same file.

It always works on HP workstation.

Conclusion:
The trial version has restriction on avi data being processed one time.
Its behavior is unpredictible on my ThinkPad. It quits processing an avi but it works on the same file in a few minutes. It;s very unstable.

[vcdforme]

Seems to me you no make proper avi.

[jimmalenko]

Source: captured DV (home video) from Sony Camcorder using VS7 and VS8. According to VC7, no drop frame, and saved as Type I avi.

I'm pretty sure that if you are using DV with TMPGEnc you should save as type 2 AVI or you can experience issues.

Target: NTSC DVD using TMPGEnc 2 VBR + noise reduce filter

The noise filter will add heaps of time to your encodes.

Conclusion:
The trial version has restriction on avi data being processed one time.
Its behavior is unpredictible on my ThinkPad. It quits processing an avi but it works on the same file in a few minutes. It;s very unstable.

It doesn't work with your setup. That does not make it a bad program.

I "capture" DV from VHS with an ADVC-100 through firewire using ScenalyserLive. Save to AVI using Canopus DV codec. Edit with VirtualDubMod and load into TMPGEnc with an AVS script using Convolution3D instead of TMPGEnc's noise filter. It is much quicker and the results are as good as the source.

Maybe VS is causing the problems.

[flaninacupboard]

yep, i'll bet Type 1 is your problem. download DVIO or DVapp (both free) and save as type 2. i just left a batch running on type 2 DV last night, completed this morning no problem.

[xuy_98]

Thanks all for your input.

The problem was the DV source.

After I recaptured in Type 2 DV, TMPGEnc works fine.

2 VBR no filer, no motion search, 2 minutes for 25 seconds video.
2 VBR no filer, highest motion search, 6 minutes for 25 seconds video.
2 VBR noise filer, highest motion search, 12 minutes for 25 seconds video.

These data are based on ThinkPad P4 2.0MHz.

Now I am a happy TMPGEnc registered user.