I paid for Vegas Pro 17 and it works badly...

SantiagoF wrote on 1/3/2020, 6:50 AM

Hi, I bought the license for vegas pro 17 thinking that I was not going to have any problem with the program.
However the program stops. And this makes me think that this program does not work well (I paid a lot of money to go well and that is not the case).
I have a pc i7 9700k, video board rtx 2080 ti and 32 gb of ram, windows 10.
With adobe premier I have no problem, but I like vegas pro more but I always have this problem when editing:

https://prnt.sc/qivfvs

Is there any solution for this?

Version number: https://prnt.sc/qivij6

Back to post

Comments

SantiagoF wrote on 1/8/2020, 11:58 AM

where do i look at that?

@SantiagoF - You go to the nVIdia site and look for your GPU Card:

Then select the STUDIO option:

Now compare YOUR Driver Version with what nVidia are offering for your GPU Card.

You find this information on your nVidia Control Panel or your Windows Device Manager.

Keep going! We will hope to get you there - 😉

I was using the game ready, I didn't know that I had to use other controllers, right now I am downloading it, thank you very much!

joost-berk wrote on 1/8/2020, 4:15 PM

Okay, So in stead of using Dynamic RAM Preview, you could rather go for the PreRender Video option. That gives the same result. The advantage is that you don't need any MB's be available in the Dynamic RAM Preview. So by setting this to "0" makes Vegas much more responsive (in my opinion). It seems that this is because VP does not have te claim and reserve any RAM for video preview at al. If Vegas can claim lot's of RAM it becomes verry sluggish which results in crashing / not responding.

Grazie wrote on 1/8/2020, 8:14 PM

Okay, So in stead of using Dynamic RAM Preview, you could rather go for the PreRender Video option. That gives the same result. The advantage is that you don't need any MB's be available in the Dynamic RAM Preview. So by setting this to "0" makes Vegas much more responsive (in my opinion). It seems that this is because VP does not have te claim and reserve any RAM for video preview at al. If Vegas can claim lot's of RAM it becomes verry sluggish which results in crashing / not responding.

@joost-berk - Sure. Also give Wayne’s HOS KwikPreview a go. Using Satish Kumar’s FrameServer it too is a Volatile Process and as such is also Temporary but, and here is the major advantage, I can utilise an nVidia Fast Renderer to produce a file - it is like lightning-fast. It is verrrry Kool 😎.

joseph-desaavedra wrote on 1/8/2020, 9:52 PM

Thank you. That makes sense if you have plugins in your project.

Are you able to use the Scrubber with acceleration turned off?

I dislike my ignorance but what is "Scrubber", I am a regular editor, I have a YouTube channel with almost 200 thousand subscribers. Sometimes when I use many effects it stops. My problem now is that the preview loads a bit slow, when I had enabled the "" GPU Acceleration of Video Processing "I was going much faster

Are you using the studio drivers or the game ready drivers? Studio drivers are recommended.

All my pc is updated, I have updated nvidia drivers. I have vegas pro 17 updated. I have a high end PC and sometimes vegas pro works for me more or less

well, I have been struggling with the same thing for almost a year, so far the only way I have mitigated crashing is to turn the frame rate to 30fps on the preview window rather than matching the source footage of 60 fps that I use on my Youtube channel. and stay with Build 321 everything else crashes. I too have a 2080ti. None of the suggestions here have done anything at all and lord knows I have tried everything. Tech support isolated the crashing to the video card during edit from the encoding to for the previews screen. I have no issues with actual rendering. So far Tech support (sluggish as they are) has offered no solutions. If not for the fact that I like the interface this would have found it's way to the bin a long time ago paid for or not. Initially I did proxys before starting the edit session thinking that was the solution as the crashing almost completely stopped until I realized my frame rate in the preview window was at 30fps. If I upgrade to the newer build it starts crashing again. Hope that helps.