-
Desperate–Vegas quits rendering 90% through same set of events
I’m running Vegas Pro 10e with Boris RED 5 (the latest version) on a system with 6GB of RAM. Both apps are 64 bit versions.
I have a 9 min, 26 sec sequence that I’m trying to render to an uncompressed AVI. Some of the clips are 29.97 fps, some are 15 fps. I’ve rendered sequences like this before countless times without a problem.
If I render the entire sequence, Vegas will halt approximately 90% of the way through after it begins one of the clips at 29.97 fps.
I can render that final sequence by itself without a problem, but not in toto with the entire 9 plus minutes.
My working set in memory is about 85% consistently throughout the render process.
I’ve tried uninstalling and re-installing both Vegas and RED. Neither reinstallation has helped.
I’ve run a CHKDSK on the system. Problems in the volume bitmap were found and fixed. Again, there’s no difference in behavior.
Vegas did give me one specific log error during a failure, when it called out a Windows dll under C:Windows…..MSVCR90.dll. The problems was an “unmanaged exception.”
I’m completely stuck and frustrated at this point…I’ve never had a problem this severe with Vegas before, and like many of you, I have to fix this to complete a project. Any help would be appreciated.
Thanks in advance,
Carl
-
8 Replies
-
MSVCR90.dll is one of those runtime libraries that gets installed by almost every program. There are 35 copies on my editing PC – various sizes and dates. No wonder it’s a target for hacks.
However, just for grins, make sure the “close media when not active” option is unchecked, and click on the lightning icon in the project overview to remove all unused media.
Steve Mann
MannMade Digital Video
http://www.mmdv.com -
Thanks, Stephen…I believe this copy of the dll is Microsoft’s generic one. I just reinstalled it, and rebooted. I’m trying the render again.
One update–it turns out that while Vegas would render the last few minutes of the segment by itself (the 29.97 fps portion), it will NOT render the previous segment by itself. This is strange, because when I try to render the segments together, the failure did not occur until Vegas got into those last few minutes where the 29.97 fps section is (I hope all that makes sense).
I did try your option of unchecking the unused media checkbox before my last rendering attempt (which ultimately failed), although I did not tell Vegas to drop its listing of unused media from the bin.
Anyway, I’m rendering the whole segment now after reinstalling the C++ libraries and a reboot. We’ll see if that solves it. Fingers crossed.
Carl
-
OK, so far all my efforts have failed in pretty much the same fashion. I’ve tried reinstalling the dll, and I’ve tried reinstalling Vegas twice. Vegas still typically fails at just over 90% into the render, usually with an “unknown error.”
I did increase the RAM in the box from 6 to 8GB, although my working set in memory has left more free memory, it hasn’t helped with this problem.
I did find that I made one boneheaded mistake in adding several clips from my backup copy on the NAS, rather than my local RAID 0 drive, into the segment I was rendering. Again, fixing this problem and restarting Vegas has not made any difference.
Is it possible that adding Boris RED chroma filters in “compositing mode” in one of my video tracks might be an issue? I don’t know what else to think at this point…it’s the only thing I’ve done differently on this project than on my previous projects.
Any suggestions? Anyone? I’m getting quite desperate. And frustrated…and embarrassed with my co-workers.
Carl
-
Can you render the sections separately? If so, then try a nested solution. Put section1.veg and section2.veg on the timeline of the project.veg file.
Steve Mann
MannMade Digital Video
http://www.mmdv.com -
I’ve taken the first part of the sequence that rendered correctly, and placed it adjacent to the second part that rendered correctly on their own, dedicated tracks. My objective is to produce a temporary workaround that allows me to have the single uncompressed avi that I was trying to get in the first place.
What I’m now wondering is whether my application of Boris RED chromakey effects using compositing mode at the track level without nesting the background track as a child is causing me all this trouble. In my present configuration, is it likely that the chromakey filters are performing calculations through every video track beneath it, rather than being confined to the green screened track and the background track beneath it? Most importantly, can this be causing the renders to ultimately stop?
-
Nesting does that. your final project file consists of a few nested veg files from the segments that do render OK.
Steve Mann
MannMade Digital Video
http://www.mmdv.com -
OK, I finally seemed to have resolved this. When I nested the backplate track and made the foreground track with the Boris RED chromakey filters its “parent,” the render finishes. In fact, instead of a projected 2 hours and 15 minutes, it finishes in 1 hour and 15 minutes.
In retrospect (and to the more knowledgeable than yours truly), this all makes sense, given that I’ve limited the application of the filters to the parent and child exclusively, rather than to every “lower” track in the timeline.
A lesson painfully learned.
-
“A lesson painfully learned.”
Most are. I have the scars to prove it.
Steve Mann
MannMade Digital Video
http://www.mmdv.com
Reply to this Discussion! Login or Sign Up