[Paul Berk]

Probably will not help — but here are some things to try (why not?) …

1 .. reboot your system (get a clean start) ..

2. .. rename the backup file as it was .veg.bak .. try to open that.

3… if file still corrupted, I’m out of ideas unless you know how to debug the corrupted file header and see if the corruption can be fixed ? Debugging takes an expert and the right software.

4. Most of us have been bitten too .. sometimes the fastest way is to rebuild it. You’ll find 2nd time around the edit will go faster.

[Paul Berk]

For the Record from Vegas Help:

Automatic project saving
A backup copy of your project is automatically saved every five minutes. If your system crashes, you will be prompted to open the backup file the next time you start the application.
Backup files are saved in the location specified in the Temporary files folder box on the General tab of the Preferences dialog. Files are saved with the .autosave.veg extension and are deleted when you exit the application. For more information, see Preferences – General Tab
If you prefer not to autosave your project, you can clear the Enable autosave check box on box on the General tab of the Preferences dialog.

When you save a project, .veg.bak files are created in your project folder to allow you to return to the project’s last-saved state. Creation of backup files is independent of automatic project saving.

[Paul Berk]

Look for a back up file in the same directory your .veg was saved. The file will have a tail of .veg.bak ..
To see the backup files when you “open” a .veg, select ALL FILES *.* in the pulldown list for file types.

The Backup file is automatically created by Vegas when you “save” a .veg file. Each save overwrites the previous backup, so only the last save gets backed up. I think that’s right.

[Paul Berk]

Just for the record … In V12 (oldest version I have loaded) you can do:

Select all images on timeline (not the audio), right click, Switches/disable resample

Not sure you can do this in V9

In VP16, you can set disable resample in the project properties.

[Paul Berk]

George … Thanks for your post .. spot on … I’m far from expert on rendering …

Question for George or anyone: Would “disable resample” on all those stills be a good thing in this case?

[Paul Berk]

First, just for the record, make sure you have enough disc space to fit the renders you are doing. Low disc space can do funny things. As suggested above, CPU temp should be watched too .. but generally if things get too hot, the PC will simply shut down.

I see your project properties. I suggest you TURN OFF 32 bit floating point unless you really know what you are doing with it. Use 8 bit.

You should match your project properties to your render. You are rendering at 1440 x 1080 but your project is 1920 x 1080 .. Why not render at 1920 x 1080? Or change your project properties to 1440 x 1080. That’s my opinion.

But this does not account for why your render went blurry at 28 min. I would have thought something was wrong at 28 min to account for the image going blurry .. but you say everything renders fine at that point when rendering a loop region of about 5 min.

So … I’m perplexed .. Even with Vegas 9, this should not happen. But finding out the reason may be very time consuming.

IF it was me, I’d render the first 20 min or so as an MXF file that matches the project properites (MXF is essentially lossless). IF that part is OK, I’d render the next 20 min and so on until you have the entire timeline rendered in sections. IF all of the sections are ok, then you can assemble the sections into the full length timeline and render that to the format you want for the final output. If that works, your loss of quality will be minimal, and this method might be faster than attempting the entire timeline over and over again hoping it will complete ok. Normally I work in sections. Long timelines have many disadvantages, especially when it comes to making changes later.

I just finished a 4 1/2 hour piece. It was rendered in MXF sections as I suggested above. There were two parts, both over 2 hours in length. Each part had about 10-12 MXF files. I had no problems rendering as a 1920 x 1080 MP4 file. From there the piece was rendered as a Digital Cinema Package. Ultimately we screened the piece at an iPic theater on a 50 foot screen. It looked amazing. I was expecting a huge loss of quality with all the rendering generations from the original. But things looked as good as on my editing room monitor.

[Paul Berk]

Create a selection area from where the problem begins on the timeline, 28 mins or so, and render out maybe 5 or ten minutes from there and see what happens? Same problem? Or no problem?

[Paul Berk]

Whoops … Sorry .. You don’t see the Preset “Black Background” since it was one that I added myself to the presets for ProType. Here’s what to do to get you started doing your own presets, starting with the one you want now.

1. In Protype titler, drag the “empty” preset to the timeline.
2. Double click in the black area. You should see “Sample Text” highlighted. Leave that. Do not touch it.
3. On the left, under Span Properties, click the “Style” tab
4. Look for “Background” check box on left.
5. Click on the “Background” check box.
6. Click on the color box and change the color to black or whatever you wish.
7. You can now save this as a preset. Look above Span Properties and to the left to see “Preset”. Highlight the name of the preset (in this case it should say “empty”) in the pulldown window. Type a new name to replace what was there. Save the new preset by clicking on the Disc Icon to the right of the preset pulldown window.

Now. Use the Vegas Help and find ProType. Read the help. Go online and find YouTube Tutorials about ProType Titler. Mess around with ProType yourself. It is not easy to learn — but once learned — very powerful. IT does a lot.

[Paul Berk]

Then use ProType Titler to give your text a black background.

Media Generators/ProType Titler .. there should be a preset called “black background”.

[Paul Berk]

Which version of Vegas are you running?