The other interesting thing I see on the MC site is a new vesion of theirDV codec. If I'm not mistaken this is the one that VV uses as well.

The new version MC DV codec claims to support HT. If this is the case then renders may run a lot faster using it for those who have HT.

I recently asked about this:

http://mediasoftware.sonypictures.com/forums/ShowMessage.asp?MessageID=218370&Replies=8&Page=3

Best/Tommy

I am not sure you just copy the MC 1.4 files over the SF MC files, if anyone has tried this with success it would be good to know.

We would all like faster renders and hope the latest encoder will fly.

I thought I would do a couple of quick basic tests - any commnets welcome.

I am using a dual 2.* GHz with Hyperthreading and XP SP1

I downloaded the rendertest from the sundance site, it uses internally generated media and text within Vegas.

If I try options of encoding with the V4 built in encoder, frameserving to MC 1.4 and other perms here are the results.

V4 built in MC Encoder 1:23

V4 Frameserve to MC 1.4 1:22

V4 to AVI from timeline 1:21

AVI to MC 1.4 2.53

AVI on timeline built in Encoder 3:00

It appears that some of the large renders I do are mainly time constrained by the work V4 has to do i.e VFX, Audio, etc. in converting the timeline the MPEG overhead is constrained by the speed it is being fed frames.

So I am not sure the faster encoders will have that big am impact.

There are other reasons why you may want to use the external encoders, my conclusion would be to frame serve to them using the plugin from Satish (thank you Satish).

If you want to use 2-pass it would make sense to render an AVI first as the encoders are offering realtime encoding from an AVI. Frameserving 2 pass needs a second conversion of the timeline within V4.

Does this make sense or have I been drinking too much coffee......

PAW

I sent an email to SONY last week asking the same question as the original poster. An answer came back that said NO you can not just replace the files. I'm at work now and can not post the email. When I get home tonight I'll copy SONY's email to this post.

My question is, is Sony's response just the company line, or is there a real software problem? I followed the advice by BJ_M in this thread:

http://www.dvdrhelp.com/forum/archive/t176872.html

And tried it on a short render (5 minutes), using a DVD template I'd created earlier. Seemed fine & fast. Of course, I have the old files in a backup folder, just in case... ;-)

No extra features are added, as the thread mentioned above says. The only bennies would seem to be whatever speed & quality improvements were implemented. I assume the next VV update will open up features (2 pass VBR).

Sometimes the interface statements are the same from one version of a library (.dll) to another and newer libraries can be used with older programs. Sometimes the new libraries make changes in the call parameters and the old program and the new libraries may be incompatible. To fix this the old program would need to be recompiled with the new interface statements (.h) and libraries. Sony is probably correct, but try it after saving the directory; you can always put it back like it was. It should just crash with an error message and not hurt anything (not guaranteed but most likely).

i'm not really sure there is a real advantage -- i have had not the time to to do a real extensive (or not even non-extensive test) on speed and quality -- though it SEEMS slightly better quality and SEEMS slighlty faster (replacing the files mentioned above) .. the real benifits are when one changes some settings internal in the vegas interface -- whech is reverse engineeering and SONY doesnt like that .. they get mad at me for ripping thier tape machnes (and an audio board once) apart to play with them :) ..

ive been running with a "modified" vegas for awhile -- and have not experianced any isues at all .. though most times i would render avi or frame serve out anyway ..
I also mentioned that the new soundforge comes with a different mpeg build also -- and other than the fact that installing the new sound forge at first completly toasted my vegas and acid installation - requiring a complete new install and authorization -- when sonys lic server was down - so it was over the phone , WHICH I HATE , as i never get the numbers right .. was non to happy.. anyway -- soundforge comes with a different build but not sure how that fails into things -- you can frame serve out of vegas to soundforge to use that encoder but you cant install soundforge to use a shared mpeg plug in directory or it will toast your vegas and acid ... really screwy ..