Maybe could talk one of the code wizards here into writing a plugin similar to the one for prem, that lets you frameserve to TMPGenc?

mike

So is this the exact same version of the MPEG2 encoder that was in Vegas 3? If not, can you notice a difference in quality/speed?

Frameserving to TMPGenc would be awesome. I wonder if it's possible with all the new scripting support built in.

It should be the same encoder. Vegas was updated but from what I've seen, the mpeg encoder is the same,but it does have very good quality.

If you read the New Features overview at http://www.sonicfoundry.com/Products/showproduct.asp?PID=808&FeatureID=6877 or look at the release notes you'll see the following:
 
* Improved MPEG-2 encoder

Don't know what that means exactly, since no more details are given.

Sverre

The MPEG encoder UI has not changed. There are a number of new components under the hood that have never shipped before, so some of the "pulsing" low bitrate and stability issues have been, we think resolved. It should be somewhat faster too, but
performance varies widely depending on many factors. It isn't slower under any conditions we are aware of.

When Main Concept releases version 1.4 of their encoder, will Vegas 4 owners get it too?

Hi All,

A few clarifications/observations:

1) The standalone MainConcept MPEG Encoder does not yet have multipass encoding. It should be included in v1.4 in the somewhat near future, although no release date has been set yet.

2) For those anxious to get multipass encoding for quality reasons, don't underestimate the quality you get with single-pass encoding. Some people think that multipass generates better quality because the encoder looks ahead -- but even in single-pass mode an MPEG encoder looks ahead. The whole MPEG encoding process is based on comparing frames. Although multipass can offer enhanced quality from a more thorough look-ahead process, many people think the key benefit of multipass is bitrate budgeting -- the ability for the encoder to use the available data rate more efficiently. Our multipass encoding will be great, but our single-pass encoding offers exceptional quality today.

3) Whenever we update the MainConcept SDK with new features, those features often find their way into our standalone encoder first -- but that's not because we hold back on them. Once we have run new features through QA it's easy for us to add them to our own app. But licensing partners need to run them through their own QA, integrate them into their architectures, QA the integrated versions, and roll the update into their own release schedules. SF handles this sort of thing very efficiently, so I wouldn't anticipate any unreasonable delays.

Best regards,

Mark Bailey
MainConcept