If a workstation is under spec'd or otherwise so messed up it cannot render with vp20, chances are slim that it'll be able to run vp18 and vp20 simultaneously. If the project's that simple, might be easier to just start over in vp18.

Project is 7 hours long, many edits, so rebuild is torture. PC is fine. Minimal software installed only used for editing. Dexcon, I will try your suggestion. I only use "classic" FX. In this project media is a mix of AVC and EXcam (mpeg2 35mbs).

Project is 7 hours long, many edits, so rebuild is torture.

Always wondering who will watch such giant (7 hours) projects, also watching must be a real torture?

Lectures.

@TVJohn Another approach is to divide your 7-hour project into adjacent regions and see if you can render them sequentially... Vegas comes with a script that can render all the regions in a project. Then you can glue all the region-renders together outside of Vegas, perhaps with a Windows copy command (see: this thread), or pull them into a vp18 project if you prefer.

Thank you I tried rendering from different spots. First 3 attempts crashed 2 hours in 27%. Then tried rendering loops. Seemed to crash quicker each time. Even removed all FX. Right now VP 18 is at 75%

@TVJohn What about creating a project for each lecture?

Render through Voukoder, should work every time regardless of media.

@TVJohn What is the format you are choosing when rendering and what are the settings?

3Point, Client wanted one file for the Day. There were other live events during the lectures.

Roger, Voukoder crashed as well.

Steve, I tried various rendering settings, same result.

Dexcon, the timeline cut and paste to VP18 was successful, and the render completed without error in 20 hours with the same output settings as I used in VP20.

Perhaps file a bug report to VEGAS support (scroll up and click on support). Include details about the media in use.

3Point, Client wanted one file for the Day. There were other live events during the lectures.

As you don't write a book on ONE page, you write a book by bundling several pages. Same counts for video, you can make a video by bundling several video projects into one video, in Vegas we call this nesting. A faster way is to merge those several rendered into one video with a tool like Shutter Encoder.

This is definitely a faster, easier and trouble less way to create such a giant video project.

Roger, during some render crashes dialogue box asked for details to send. I provided those.

3Point, as there were 4 cameras, two alternating remote from a different location overlapping, its much easier to lay everything on the timeline syncing audio either cutting or picture in picture as appropriate.

This has always worked for me. The problem is VP20 render. I have no problems timeline editing. Trying to create mark in mark outs and rendering only sections did not work either.

Dropping the whole thing into VP18 rendered flawlessly.

Had the same problem. I decided to turn back to my previous version of Vegas and I couldn't open the project. I found this method wich literally saved my hours of work.

For events like this, I typically make each section it's own project and then render out each section individually. Once all sections are done, I take the final renders and put them in a new project to create a "single" project for the whole thing and then render that out to the final file.

I have noticed that V21 is not as stable as prior versions. Oftentimes an errant mouse movement is enough to cause a crash. I can use V19 without such issues.

I have noticed that V21 is not as stable as prior versions. Oftentimes an errant mouse movement is enough to cause a crash. I can use V19 without such issues.

And yet, for the most part, I have seen the exact opposite...

I've edited for several hours non-stop and so far with VP21, so good! Using a lot of Boris FX plugins.

The PC is an AMD 8350 8core on an FX990 MoBo with 32G ram. I replaced the Quadro card last summer with an Nvidia 3060Ti, works stabile generally with V21. Until the last 2 versions I can say I Never (really-never) had a Vegas freeze or crash. Perhaps the last 2 versions are leveraging the CPU differently.

AMD FX-8350 is from 2012. In general I try to keep the software within 5 years or so of the hardware.

VEGAS GPU decoding is changing in 21, esp. for NVIDIA GPUs. You could try to enable legacy AVC decoding in preferences file io and then retest when a newer build for 21 comes out. This may help with your AVC media (your mpeg2 media isn't using the GPU).