Then it must bei the mainconcept 1.4 - if it is stil the MC-Encoder.

I know it has 2 - pass VBR. I'm just wanting to know what VERSION number of the Maincomcept encoder. Some people may not want to upgrade to Vegas 5 but want an updated standalone encoder. If we knew what version was included in Vegas 5, we would have more info for making the decision. (go with Vegas 5 that has new features -that some people may not need - PLUS version xx of the encoder, VERSUS, a new, cheaper priced standalone encoder, e.g., Procoder, CCE Basic, Mainconcept, etc.)

I tend to disagree - since a lot of tests has shown, that the old MC 1.1 has delivered a much better performance in terms of picuture quality, compared with othere apps that had the same encoder in (e.g. AP 6.5 but also MSP-6.5x).

Even if it was never published why the performance was soo good - to my experience similar with the CCE - the differences could derive by a better picture transfer mechanism between NLE and Encoder (maybe subpixel-rendering?).

So, take care how to assess the quality of the standalone encoder - to compare that with the integrated encoder (by the way, mainconcept offers a gratis trial with watersign - maybe supports your testing?).

wschmid,

You disagree with what? MC 1.4.2 standalone does a better job than Vegas 4 (FOUR) with it's last included MC encoder. This is unanimously agreed upon.

I simply want to know: Does Vegas 5 include MC 1.4.2 or newer? If it includes 1.4.2, when does MC expect to release a newer version of their standalone encoder and will Sony update the encoder with their bug fix updates? My question is for the benefit of those who aren't sure if they need to upgrade to Vegas 5.

I disagree with the approach that you are able to compare the standalone encoder with the integrated encoder in a simple way - given comparisions with other tools. For example, take the good old svcds: the same encoder in Adobe Premiere (1.1 in 6.5) produced a lot of artefacts - while it was fine in Vegas-4.

But maybe somebody from Sony could answer that question. A simple comparison between the file version will not not answer this question really.

I see where you are coming from now. I hope Sony replies....

Dan

I don't think it's the latest MC encoder. I ran the render tests and go the exact same encoding times with Vegas 4 & 5. People have reported faster then Vegas times with the standalone ones. Also, Sony will probley do what SoFo has done with the encoder: release fixes/small updates, no major revisions. I am disapointed that V5 doesn't render faser though. :(

I am *NOT* a sony worker, but just doing some simple looking - here are the version numbers.

Stand alone encoder

~ MPEG Video and Audio Decoder = 1.0.0.60
~ MPEG Encoder and Muxer = 1.1.0.8
~ MPEG Stream Decoder = 1.1.1.34
~ Mpeg I/II Splitter = 1.0.0.56
~ MPEG File Decoder = 1.1.1.124
~ MPEG Audio Encoder = 1.1.0.18
~ MPEG Multiplexer = 1.1.0.76
~ MPEG Video Encoder = 1.3.32.0 (2004/03/16)
~ MPEG Video Wrapper = 1.3.32.0


Vegas 5

~ MPEG Video and Audio Decoder = 1.0.0.56
~ MPEG Encoder and Muxer = 1.1.0.2
~ MPEG Stream Decoder = 1.1.1.30
~ MPEG File Decoder = 1.1.1.99
~ Mpeg I/II Splitter = 1.0.0.52
~ MPEG Audio Encoder = 1.1.0.17
~ MPEG Multiplexer = 1.1.0.65
~ MPEG Video Encoder = 1.3.26.0 (2003/09/25)
~ MPEG Video Wrapper = 1.3.26.0

If you look in

C:\Program Files\Sony\Shared Plug-Ins\File Formats\MCMPEG

I think the version of the encoder 1.3.26

But as this is the OEM encoder it does not follow that the version information would eb the same anyway

When I looked at the render test the majority of the compute time was rendering the effects and not the mpeg encoding, try rendering to uncompressed and compare the results.

If I render a straight AVI from the timeline the built in encoder does pretty good.

Paul

bump

MC version numbers are confusing since I own whatever version in Vegas 4 plus the standalone 1.4 plus the version in Adobe Premiere 1.2.

There is a BETA 1.3 for the Adobe MC encoder which is supposed to be essentially the same as the standalone 1.4. So, I would hypothesize that the 1.3 version included in Vegas 5 (see post above) is the same as the beta Adobe version AND the standalone 1.4.

As I said, MC's way of naming versions can be confusing. Too bad we don't have a resident MC representative like Mark Bailey who hosts the Adobe MC forum.

Jake

I wish a Sony employee would give us the official word on this (or tell us they can't give us the official word)..

"Too bad we don't have a resident MC representative like Mark Bailey who hosts the Adobe MC forum."

Actually, there have been posts here by MC in the past, can't remember the name though.

bump

Those posts were also from me.

The version number of our standalone MPEG Encoder doesn't necessarily correspond to the versions of integrated encoders like the one in Vegas. The standalone encoder's version number represents not only the encoding components but also the interface features such as realtime MPEG capture, batch processing, etc.

In general, licensing partners get the latest version of our SDK immediately upon release. We are able to add updates to our standalone encoder quickly, but companies like Sony might have to run the components through their own QA and release cycles.

Mark Bailey
MainConcept

Mark

thank you for responding - so I understand, that it is up to Sony to tell us, which version of your encoder is integrated in the actual Vegas-5 version.

Please Sony, it would be really interesting to know that - or is that a secret?
:-)

bump

No secret. Our plug-in uses the latest SDK update provide to us by MainConcept which was October 2003.

So, is that AS NEW as Mainconcept 1.4.2 standalone encoder, or is it older?

I don't know. It's definitely as new or newer than 1.4. (The changes that MC made to their encoder app between 1.4 and 1.4.2 may have only been changes to the encoder app and not the actual encoding engine.)

SonySDB, why don't you have the "employee square"?

Technical issue. I'm working on that with IT right now.