[John Bean]

I know with Vegas Pro 11 build 521 that sometimes Ctrl+Z undo takes a long time depending on what needs to be undone.

So you may sit there thinking that Vegas has crashed. Trying waiting a few minutes and maybe Vegas will complete the undo.

I’m not sure if this was a bug that was related to some of things that got fixed for the latest build 594/5.

I having tested undo yet with the latest build.

[John Bean]

The Update, Trials, and Full Versions are all the same.

It doesn’t matter what page you download from you will get the same file.

[John Bean]

That’s the nature of releasing software products.

There is no way you can test for every possible case scenario.

And it’s all about meeting corporate profits every cycle. So it’s better for profits to release a product that is 51%+ working great than it is to hold off until it is 100%. You release the product on time to meet the cycle deadline. Then within this cycle, there is time allocated to fixing all the remaining bugs. And there are always bugs!

Within their team, some developers are focuses on fixing bugs while the majority of the developers are working Vegas Pro 12 for the next cycle.

[John Bean]

Is your Vegas real-time preview set to BEST-auto or a lower quality?

Does the file play correctly in any video players, like QuickTime and VLC?

[John Bean]

Yeap, that’s a deinterlace issue!

Google: sony vegas deinterlace

Lots of info there to help you.

Lots of other threads in this forum as well on the very same issue.

You mentioned you had 1080-60i source footage.

So, here is probably what you want to do.

1. Make sure you select the “HD 1080-60i” template for your Project Properties. This matches your source footage. If you are unsure, in the project properties settings you can click the “Match Media Settings”, then select one of your source footage files. Vegas will then select the project settings that matches your source footage. Hopefully, Vegas gets it right.

2. When you bring in your source media into the timeline, verify that Vegas has interpreted the media correctly. Sometimes Vegas does not. Right click the media and click “Properties”. Then select the “Media” tab. Make sure the video “Field Order” value is correct. For HD 1080-60i media, it should say “Upper field first”. If it says “None”, then you will need to select “Upper Field First”. (If your source media is “Lower Field First” then select “Lower Field First”).

3. Now in your Vegas realtime preview window, you should not see any glaring interlace problems (ie. stripes). If you still see those interlace lines, then verify steps 1-2 again.

4. Now when you are ready to render your video, make sure you know what you want your target video format to be.

If your target video is still an interlaced format, then you should be fine. For example, if you are rendering out to “HD 1080-60i”, then you don’t need to do anything else.

But if your target video format is “PROGRESSIVE”, then you need to tell Vegas which deinterlace method you want to use. In the Properties Settings again, select your desired “Deinterlace Method”. Usually, “BLEND” should be OK. For example, if you wanted to render your video out as “Sony Tablet 1080p” or “HDV 720-30p”, then you need to tell Vegas what “Deinterlace Method” to use.

After rendering a PROGRESSIVE video output, you may still see some tiny interlace lines. If you want to try to reduce those lines even more, in the video track, right click the media and go into “Properties” again. There is an option there to “Reduce interlace flicker”. Click that. Render your video out and see if it made any difference.

Again these are all just suggestions.

It all depends on your project requirements are.

I hope that helps!

[John Bean]

You’ll need to provide more information.

PC System Info (memory, CPU)
What video codec for AVI?
What bitrate is your video?

Also provide some stills of the problem frames.

Does your video appear OK in the Vegas realtime preview window?

[John Bean]

I got it working for me now.

I’m not sure what did it exactly.

I was running build 521 previously and the new build 595 didn’t work on an update install.

So I uninstalled everything, including my trial extensions of Vegasaur and VASST.

Then, I did a clean install of build 595. Still no go.

Then I did a clean re-installed of build 425. Then upgraded to build 595 from that version. And voila! Build 595 now works!

Yeah, Windows knows magic sometimes.

[John Bean]

Anyone else having problems with the new build?

After install of the update, Vegas no longer runs. Click Vegas to run. But nothing happens. It seems like it just crashes but there are no error messages.