Vegas Video 3 build 127 gives me a problem

Mar_sell wrote on 6/10/2002, 1:48 AM
I did not have that problem before with build 107

If I have one or two dropped frames in my video track and I render my project in MPG1, the resulting file will be fine if I play it but as soon as I reach the point where there was a dropped frame, the rendered file video will turn black from that point to the end of the project. It won't get back ok passed the dropped frames.

It seems I need to find a way to repair those dropped frames but how can I do this without cutting time in the project? can I just put black frames???? how do I do it?

Comments

Caruso wrote on 6/10/2002, 4:10 AM
Mar:
I can't help you at all with your problem, but, shortly after it was posted, build 127 was pulled from the board and replaced with build 128.

I don't know if anything new in 128 will correct your problem, but, you probably would want to download and install the latest version just to keep current.

Caruso
SonyDennis wrote on 6/10/2002, 7:40 AM
The only change from 127 to 128 was related to the QuickTime plug-in detecting QT Authoring components.
///d@
Mar_sell wrote on 6/10/2002, 1:11 PM
It's official. Build 127 definitely has a problem in my system.

Any bad frame that Vegas encounter in any project while rendering an MPEG1 file will stop the video stream in that file. The screen will turn black and the audio will be sent to oblivion. Everything before the first bad frame is ok though.

I just reinstalled build 107 and everything's fine.
deef wrote on 6/12/2002, 4:05 PM
One option is to recapture using Video Capture 3.0b which has improved dropped frame detection to prevent "phantom" dropped frames from bad timecode.

Additionally, ensure that you don't drop any "real" frames by following the various threads here.
Mar_sell wrote on 6/14/2002, 12:36 AM
Thanks very much for the tip Deef...

Quote from your last reply: "Additionally, ensure that you don't drop any "real" frames by following the various threads here."

Would you mind explaining a bit more please?
Jamz wrote on 6/14/2002, 10:48 AM
What happened to update 3.0b anyway. I see it's not posted anymore. I tried doing a project last night with the new update & Reel DVD wouldn't even encode the audio file to dolby digital with the new update. Are there serious problems with this update???
SonyEPM wrote on 6/14/2002, 10:55 AM
Two bugs were found: an a/v synch bug in some MPEG renders and a w64 render problem. The Vegas download/updates page explains the workarounds, and we'll have a new update posted asap.

Jamz: you issue concerns me- please drop me a note at drdropout@sonicfoundry.com and I'll work with you directly.
Mar_sell wrote on 6/19/2002, 11:42 AM
I was curious... I just wish to know if anybody else got the same problem as I did, and what mean was used to counter it?

For now, I keep on using build 107 cos I cannot risk wasting more time with that strange problem.
Mar_sell wrote on 8/19/2002, 3:41 AM
May I point out that this problem I got with build 127 is still present as I am using build 138.

Mind explaining me why please? Now I have to uninstall it and reinstall build 107.
This makes me miss all the new stuff in the latest version. But it is ok I guess... I will only have to do from scratch ALL the old vegas files I lost cos I resaved them in the latest version format. Right?


*|*
+++ (unavailable angry emoticon)
SonyEPM wrote on 8/19/2002, 10:41 AM
Mar Sel: Try this...

Go to:

ftp://porker.sonicfoundry.com/

username: dude
password: sweet
folder: MPEG 3.0a- OLD VERSION

copy the files into :\Program Files\Sonic Foundry\Shared Plug-Ins\File Formats\MCMPEG
and choose yes to overwrite all.

By doing this, you will have Vegas 3.0c with build 107 MPEG files. If you still see the problem, you should re-install 3.0c and we can look elsewhere.
Mar_sell wrote on 8/29/2002, 3:22 AM
SonicEPM,

Thanks, It is working fine now. I tested it for a while and seems ok. But I would like to know... Will I have to do this everytime you guys come up with a newer version?