Tmpgenc Encoding Dramticly Under Average Bitrate Setting

[DJ_Izumi]

I'm doing my norm, encoding video using Tsunami with 2 Pass VBR. My average bitrate is set for 3200. (Min: 500, Max: 8000) I used the birate calculator to determin the most efficent bitrate to use but Tsunami is giving me files that are undersized. In my latest encode the log reported "Average bitrate of video = 2347.10 kbps" This is 850kbps under the average I had set, it means a lot of quality that could be in the file is going right out the window.

Does anyone know why Tsunami would be going well below the average bitrate over and over agian?

[aamir12345678]

I have posted about this same problem a numerous amount of times on this site. I don't know when this problem started, but I have tried everything to fix it (including formatting). It doesn't make any sense. All of these files play fine, and other encoders encode them fine, but TMPGEnc doesn't handle them properly. In fact, it now does this with every type of file (.avi .mpg etc.). I've emailed about this to Pegasys Inc, and they just blow me off every time. CQ & CBR work fine, but 2-Pass VBR has problems. Sorry, no solution at this point in time.

[teegee420]

I'm doing my norm, encoding video using Tsunami with 2 Pass VBR. My average bitrate is set for 3200. (Min: 500, Max: 8000) I used the birate calculator to determin the most efficent bitrate to use but Tsunami is giving me files that are undersized. In my latest encode the log reported "Average bitrate of video = 2347.10 kbps" This is 850kbps under the average I had set, it means a lot of quality that could be in the file is going right out the window.

Does anyone know why Tsunami would be going well below the average bitrate over and over agian?

Just out of curiosity, what are you using the find the bitrate of your video?

[victor010170]

Hi

I exchanged few things with aamir12345678 when I encounted the similar problem in couple months. Now, my tmpgenc 2.5 plus seemed to work very well in any code, any bitrate steeting. Here is what I did.

1. Uninstalled all video software (yes all. I have dvdshrink, tmpgenc 2.5, tmpgenc dvd author, windvd, windv, ulead video, sony program, nikon program.)

2. Reinstall window direct x (I make sure I get the latest version for my xp home)

3. install tmpgenc 2.5 plus.

4. test the program with open wizard mode.

5. test the same movie (whole movie) in cbr, vbr 2-pass with highest qa, hi qa, highest qa with filter. At all time I use wizard mode, i select auto bitrate calculate. Mine auto setting in movie Patton is around 8700. Yes it took around 22 hours to finish encode at highest qa with noise reduction, sharpness improve.

I tested in order to make sure the program is working at any settings (with auto mode or wizard mode). What ever setting is working, I save it in my template with different name. It has been a month now, I am extremely happy with tmpgenc 2.5 plus as far as encode with hi qa. Again, I am aware the hours for encode is too long but I do not mind. I have encoded avi to dvd, vcd to dvd, dvd to dvd; all work well.

Why I am sharing this? I just want to let you all know there is nothing wrong with the program. If the program do not work, it shouldn't work at the first time you installed, not later. Something in your pc has changed that cause the program stop working. I am not an expert on pc, so I do not know what it is. After that, I gradually install other programs one at a time while still encode my movies. And tmpgenc 2.5 plus still doing well.

I hope this help for some of you. Good luck.

[DJ_Izumi]

I use the video help.com calculator.

The case seems to actually be this:
The higher the bitrate, the less accurate and undersized Tmpgenc is.
At bitrates of 2500kbps I get pretty much dead on accuracy.
At 3500 the files are a little undersized and the DVD has a couple of houndred MB free.
In the 5000kbps+ range I can get up to 1gb of unused space, which approaching that area, is just a total WASTE of space.

[aamir12345678]

Exactly as you are describing it, is exactly how it is happening with me. Read the TMPGenc Crash VBR thread in the Advanced Conversion forum. My TMPGEnc was crashing with an "Illegal Floating Decimal Point Calculation Order" error when doing 2-pass, but now it gives a significantly lower avg bitrate. I think the problems are related, but I don't know how. Some people are suggesting DirectX, but everything still doesn't add up. Every other encoder works fine. Why is it just TMPGEnc that is having the conflict?