Sony Vegas Pro 13.0 Crashes when pressing "Shift+B".

kieran_alexander_hughes wrote on 12/28/2017, 9:16 AM

Hello everyone, new to this site here.

 

So I've been using Sony Vegas Pro 13.0 for over a year now with Windows 10. Been experiencing issues a long the way and have been able to fix them easily. I'm no "Tech" expert but the internet has helped tremendously.

But up until yesterday I came across a problem that seems to look like nobody else has had before. So I go to open up my project file in Sony Vegas which opens up perfectly. No problems yet. Now I want to see how the video looks that I have in my timeline (with effects on the clip) so I go to select part of the clip and press "Shift+B" to prerender it. But every time I do so, Vegas starts to freeze for about 10 seconds and then crashes with a message coming up saying "Vegas Pro has stopped working" and that Windows will tell me a solution for the problem which they don't.

I have tried everywhere to find a fix for this but to no luck at all. Nobody else seems to have this problem I see, just me???

 

Any help would be great thanks from you all.

Comments

Former user wrote on 12/28/2017, 9:26 AM

What format/codec is set as the pre-render?

kieran_alexander_hughes wrote on 12/28/2017, 9:36 AM

I'm no Tech expert so I don't exactly know what you mean, sorry.

 

Edit: I noticed it also crashes when trying to play the video on the timeline too.

Former user wrote on 12/28/2017, 9:57 AM

Okay, I checked and shift-b is not a prerender but Dynamic ram preview. It is treated differently, than a prerender, but if your video is crashing on the timeline, you have a different issue.

 

kieran_alexander_hughes wrote on 12/28/2017, 10:13 AM

Okay thanks anyway for any help. I'll be sure to find any solutions if I can. If not, then I'm screwed.

NickHope wrote on 12/28/2017, 11:26 AM

Try adjusting the "Dynamic RAM Preview max (MB)" figure at the top of the Options > Preferences > Video window.

Bear in mind that this is the least understood setting in Vegas, and could cause all sorts of other issues, so if it doesn't help, set it back to the default (200MB in VP13) or whatever value you had it before.

Grazie wrote on 12/28/2017, 11:37 AM

SHIFT+B will gobble as much of the RAM you set for in your Preferences. Here are several things that can cause it getting indigestion!

1] Media v Settings: I'll fitting Media for the Project. Do your Project settings match the media at this point in your Project?

2] Plugs that Block: Plugins that require plenty of Math to perform. Also any CHAINS of plugins? Any Text Plugs?

3] Less Is More: The amount you have Selected. Is it 2 seconds or 20 seconds or what ? ? ?

 

 

 

kieran_alexander_hughes wrote on 12/29/2017, 9:54 AM

Right, sorry I took so long everybody. Try and download my veg file and see what you think the cause is.

 

Here's a link to the website to download the veg file:

Edit: you may need to copy and paste this link that will direct you to the page.

 

Don't know if this will work. But it's all I can do sorry.

Note: I have downloaded "plugins" on the clips that some of you may not have so I don't know if the file will open or not.

 

Marco. wrote on 12/29/2017, 10:00 AM

So chances are one or some of the external plug-ins you use is causing the trouble.

Also you are using a floating point project. I would rather set it to 8 bit.

kieran_alexander_hughes wrote on 12/29/2017, 10:11 AM

Hi Marco. So you've said that one or some of the external plug-ins maybe causing the issue. I just tried deleting all plug-ins I have on all of my clips but in result Vegas starts to crash again with a message saying "Vegas Pro has stopped working" and forces me to close out the program.

You also said that I'm using a "floating point project" which I don't seem to understand what that means. And how would I set it out to 8 bit as you say? I'm no tech expert so I wouldn't know what to do.

Marco. wrote on 12/29/2017, 10:15 AM

It's a mode in project properties. 8 bit is the default (and recommended) pixel format.

kieran_alexander_hughes wrote on 12/29/2017, 10:28 AM

Yes maybe it's to do with my sourcefiles. Thanks for any help.

Grazie wrote on 12/29/2017, 10:29 AM

Looks like we’re getting closer guys 😉

kieran_alexander_hughes wrote on 12/29/2017, 12:31 PM

So it seems to be that nothing has fixed the issue yet. The issue still remains unknown to me but what I have done is I've started the project all over again. Let's just hope this problem doesn't occur anymore. Thanks to everyone who tried to help out.

Marco. wrote on 12/29/2017, 12:36 PM

So you already tried to run the project in 8 bit mode?