New TMPG Plus version

[Nogami]

Registered TMPG users can download TMPG Plus v2.57.41.146 from here:

http://www.pegasys-inc.com/e_download.html



List of changes:

TMPGEnc Plus Version 2.57 (2.57.41.146) July 19 2002

-Stop reading MPEG-file with "DirectShow Multimedia File Reader", one of the VFAPI Plug-in which is included in the program.

-New dedicated VFAPI Plug-in to read MPEG-1 files included. This operates decoder made by MICROSOFT through DirectShow.

-New dedicated VFAPI Plug-in to read MPEG-2 files included. This operates decoder through DirectShow if one of the following MPEG-2 decoder is installed.
* CyberLink
* Ligos
* Sony

-At "VFAPI Plug-in" of Environmental setting, "Reset to recommended setting" option added.

-MPEG setting can be displayed to check even while encoding.

-At 2 pass VBR encode mode, it displays"Analyzing" while 1st pass (50%).

-Bug-fix : Could not read TMPGEnc project file as DirectShow source through TMPGEnc.vfp plug-in.

-Fixed "playback time" when reading MPEG-2 file through Ligos MPEG-2 decoder which is included in DVDit 2.3.

-Fixed noise on the right/left top corner of screen when using Ghost filter.

-Bug-fix : Audio part may have disappeared if dealing with more than 3 hours movie.

-At Project Wizard, if source file is DV format, it always treated as "Bottom field first" without judging field order.

-Improved bitrate allocation of 2-passVBR mode (old 2pass mode is same as before.)

[Nogami]

May have something to do with the new bit allocation on this version, but it seems to be making files that are too big when in 2-pass VBR mode. According to my calculations, it should've created a file 3.7gb for my encode, however I would up with a file at 4.1gb.

Re-encoding using the same project file with an older version to see if there's a difference.

[Sven72]

Odd as it may sound, I have experienced just the opposite, especially when using low bitrates, i.e. around 1500-1700 kbps, where TMPG wastes up to 250 MB, which is unacceptable. The higher the bitrates are (up to 2400), the better TMPG sticks to the limit. Calculations were made with fitCD.

I've experienced this already in the last version (2.56), and when reading about the corrected bit allocation in the changelog, I hoped that this has been fixed, but it hasn't.

Doing another run with a higher bitrate that would fill the missing MB fails, for whatever reason - the file gets too large.

I have no other solution for this issue than going back to an earlier version. Which means 2.02 ;-)

Greets,

Sven72

[Nogami]

2.56 was spot-on for me when encoding at about 2.5Mbps for my last project (3hrs 20min). Size came out exactly where it should've been.

I very rarely do extremely low bitrate encodes so will have to see how 2.56 does with the same settings I used under 2.57

[Nogami]

Sorry about the delay, got busy with some other projects. Anyways, I re-encoded with an older version of TMPGEnc, and the file size came out exactly right. I think they broke something in the bitrate profiling and 2.57 is making files that are too large (at least for my target bitrate, which was around 4500kbps).

[psp_3]

I experienced the same case like sven72.

I was encoding the movie The X-Files with TMPG version 2.56. In the first try I used an average bitrate of 2250, which gave me 3 CDs of size, 795, 795 and 358 MB resp. To fit the movie in 2 CDs I reduced the average bitrate by 400Kbps to 1850 Kbps. After re-encoding I still am getting 3 Cds of size 795, 795 and 150MB.

I later tried doing the same with my older version (2.51) but got the same result (filesize). I dont know if the new version screwed my older version too!:mad:

[Taokane]

Nogami,
I'm having the same problem with my files coming out too large with this new version. Do you recomend going back to an earlier one? Did you notice any quality detriments with these larger-than-estimated files? Additionally, which calculating program do you use to figure out your resulting bit rates? Or do you do it by hand?
thanks

[Erik_Osterholm]

I've noticed the same problem, and did some tests to help track it down.
To test, I encoded the first episode of Buffy the Vampire Slayer season 2. Resizing and all filters (including a smoothing filter) were done in AVISynth, so TMPGEnc got a 480x480 29.97 AVI and just had to encode it. Using the project wizard, I set Highest and Motion Estimate Search for the quality on various percent of disk capacity settings: 99, 95 and 90. These were all with respect to an 80min CD, so the average bitrate came out to be 2228, 2133, and 2014 respectively. At the end of the day I came out with 6 files. The three that were set to Motion Estimate Search all came out to the exact same filesize, despite varying average bitrates. The three that were set to Highest Quality also came out to the same filesize, although it differed from the Motion Estimate Search filesize by a few bytes. All filesizes were approx. 813mb, which is, of course, too large to fit on a standard 80 minute CD.

It seems as though TMPGEnc is now actually ignoring the Average Bitrate setting altogether. My next round of tests (starting in about 4 hours) will involve lowering the Maximum bitrate to see if that helps.

Erik