@JakeGetCake

The problem is with the footage- try to do a better job with the capture and you won't get crashes. Many other gamers successfully edit in VEGAS.

Try recording to fragmented mp4 with OBS (AVC) and then remuxing to AVC MP4 in OBS setting keyframe interval (keyint) to 1.

In VEGAS put dynamic ram preview back to the default of 5% as you need ram for everything else. You may be able to edit in best/full.

For existing footage just do a conversion. I use ShutterEncoder for that. https://www.shutterencoder.com/ Output codec MP4 with advanced settings limiting GOP to your framerate (60).

@JakeGetCake Gamers across the globe, rely on Vegas Pro as their editing tool of choice.... Hence, your problem is deriving from one thing: The captured footage you are dropping on the timeline. Do not use variable frame rate captured footages !

"I used youtube to get advice on how to fix VEGAS"

Mistake #1 People on Youtube don't know what they are talking about most of the time.

"I allocated a whopping 32GB to dynamic RAM preview without even knowing what dynamic RAM preview is"

Mistake #2 It doesn't do what you think it does. Setting it too high actually works against you.

Your best bet is going to be to open a support ticket with VEGAS Creative Software. That will get the development team involved to help you with your issue, rather than just fellow VEGAS users. Sign in with your Magix account and put in a support request, and they will get you sorted quickly.

https://www.vegascreativesoftware.com/us/support/service-center/

Through that you should then go to > Support > FAQ and Support

Or go directly to: https://www.vegascreativesoftware.info/us/support/

The advice to the optional route here https://www.vegascreativesoftware.info/us/forum/contacting-vegas-support--137601/

I have whopping 32GB of RAM allocated to the preview and I set it to Good (half) and it still crashes

If you allocate that much to Dynamic RAM preview, I would expect VEGAS to crash.

I kept that Dynamic RAM setting as default.... and so far so good...

I understand your problem perfectly. I've been working on Vegas for many years. I've always had problems with it. Even today there are two my tickets in support waiting to be fixed...

Interestingly, in the case of exactly the same project run on different software, only Vegas crashed.Just turn on Let's get Adobe Premiere Pro and Vegas as an example... Upload the same movie files. You will see that everything works smoothly at the competition. Only Vegas has problems.

Even very recently I started working in a new place. New computer, new Vegas. Of course, as the project's content expanded, Vegas began to run slower and slower. Believe me, your computer is not important. Vegas works very poorly on any hardware.

AMD Ryzen 7 1700X Eight-Core, 64GB RAM, GeForce 1080 6GB

I have mastered the program perfectly, I work in it very quickly and that's why I don't want to change to another one.

"Vegas works very poorly on any hardware."
That isn't true. NVDEC decoding with certain media in VEGAS is known to work poorly (had the same issue with my GTX 1050). Changing the media or disabling the decoding (enable legacy AVC, etc.) avoided the problems. Using an Intel iGPU also improved stability.

Other programs crash. The reason I moved to VEGAS initially was because Premiere wasn't stable on my machine. I also have Resolve and it's very GPU-dependent which is great until it crashes the GPU. Fairlight also had its share of bugs (I still like it for audio editing).

Read this https://www.vegascreativesoftware.info/de/forum/sony-vegas-vs-vegas--119881/ first, before you try to make us believe you bought "Sony" Vegas 18.

Thank you so much. Calling it just Vegas instead of Sony Vegas has fixed all my problems. You are a genius.

Could you deliver a Mediainfo screenshot from your footage?

A lot of screen record software produces files that are difficult to edit unless you make some changes in their settings to specify certain codecs, framerates, etc... Variable refresh rate video, for instance, doesn't edit well, so it's best to go with a constant framerate. Some codecs, like MKV, don't always work well either, so it's best to use AVC or HEVC.

Dynamic RAM preview is not how much RAM VEGAS is using when previewing your video, even though its misleading name might lead some to think that. Instead, it is what VEGAS renders to when you press CTRL+B, it will render whatever portion of the timeline to your RAM that you have selected with the loop region (or as much of it that it can fit into your RAM), so you can smoothly play back even effects-heavy clips that play back slowly. So, setting the Dynamic RAM Preview number higher doesn't actually make VEGAS' timeline playback any smoother, it just hogs up more of your RAM for the shift+b preview and leaves less for VEGAS to use for other things, like editing or previewing on your timeline. I personally think it needs to be renamed for this reason, and I will be making that suggestion to the dev team. Ideally, you want to leave this setting alone, unless you are using shift+b to preview a section of your timeline and can't render enough in with the default settings. Otherwise, as Derek suggested, it can actually cause VEGAS to crash.

One quick way to test if your media capture settings are what is causing VEGAS to crash, is to download the free app "handbrake", and use it to re-encode your media to mp4. Import what it encodes, and see if it still crashes. It most likely will not. If not, then we know we need to tweak the settings in your capture software, and that gives us a head start on fixing your problem for you.

Media Properties

- 60fps

- 3840 x 1080

- 147788kbps

Wow.

Your project is 8 bit HD, standard dynamic range 😶

Project Settings

- I have a whopping 32GB of RAM allocated to the preview 

Why?

That doesn't affect timeline preview. Except to slow it down.

That is the memory allocation for Dynamic RAM Prerender, not what you imagine.

• We are patient with new users while they gain experience. Proceed accordingly.

I won’t be home until later this afternoon, but I think part of the problem is that I use CQP set at 14 and I think VBR with 5K - 20K would be better. I also need to make sure that OBS isn’t recording in a variable frame rate. I don’t believe it is but it won’t hurt to double check. I think the CQP is a bad choice because my 15min videos are like 30GB and I think that’s what’s bogging Vegas down and making it crash. Y’all have been very helpful so far and can’t wait to try these suggestions when I get home. Also I record in MP4 and someone suggested going to fragmented (which I would like to avoid) is there a better format for me to record in that can handle up to 3 audio tracks and works better with Vegas?

I won’t be home until later this afternoon, but I think part of the problem is that I use CQP set at 14 and I think VBR with 5K - 20K would be better. I also need to make sure that OBS isn’t recording in a variable frame rate. I don’t believe it is but it won’t hurt to double check. I think the CQP is a bad choice because my 15min videos are like 30GB and I think that’s what’s bogging Vegas down and making it crash. Y’all have been very helpful so far and can’t wait to try these suggestions when I get home. Also I record in MP4 and someone suggested going to fragmented (which I would like to avoid) is there a better format for me to record in that can handle up to 3 audio tracks and works better with Vegas?

@JakeGetCake If you are happy recording straight to AVC in MP4 that's fine. The point of fragmented or MKV is in case of a failure with the stream. If that's not of concern to you then you can skip that step. The key is a final video for VEGAS that's constant framerate AVC with a short keyframe interval.

CQP itself isn't a problem but why set it at 14? I think you are right that very high peak bitrates are challenging to playback. Try 19 and see if the quality is acceptable for your purpose.

I'm sure you'll get it working.

Read this https://www.vegascreativesoftware.info/de/forum/sony-vegas-vs-vegas--119881/ first, before you try to make us believe you bought "Sony" Vegas 18.

Thank you so much. Calling it just Vegas instead of Sony Vegas has fixed all my problems. You are a genius.

@JakeGetCake just a piece of cake to make a Vegas genius of you too!

I think the CQP is a bad choice because my 15min videos are like 30GB and I think that’s what’s bogging Vegas down and making it crash.

Hardware encoder bitrates are high and file sizes are large by nature; it is your low setting of 14 that makes the files bloated for editing.

QCP is more efficient at a value of 20 -- if you need more quality, inch your way down -- somewhere between 75-100 Mbps is easier on Vegas, consider building proxies if you still need more . . .

Media Properties

- 60fps

- 3840 x 1080

- 147788kbps

Wow.

Your project is 8 bit HD, standard dynamic range 😶

@mark-y It's a non standard HD resolution though 32:9 aspect ratio. I had more crashes moving from a 1080P monitor to 1440P for screen recordings

 

Even very recently I started working in a new place. New computer, new Vegas. Of course, as the project's content expanded, Vegas began to run slower and slower. Believe me, your computer is not important. Vegas works very poorly on any hardware.

AMD Ryzen 7 1700X Eight-Core, 64GB RAM, GeForce 1080 6GB

@Vegas21_user that's many users experiences that have posted here. Some believe it's a mix of complexity and length of project, going over 10 minutes see's the slow down. In my experience when Vegas slows down it's also more prone to crashing.

Let's keep this on-topic... we're not here to rant about VEGAS, we're here to help this user fix their problems.

So I adjusted the CQP number from 14 up to 20 and I am able to use vegas much better now. I can actually watch some of the preview now without it crashing instantly. Still keeps crashing when a lot is happening on screen though. Do you guys recommend switching to VBR? The only reason I was using CQP at 14 was because I watched a YT video and the guy said if your PC can handle it that would be the best route for recording (so that's what I did. hahaha yea I'm still new). When I went up to 20 I saw virtually no loss in quality. Could bumping this number up some more allow me to edit without crashes, or lower my quality? Also the reason I record in 3840 x 1080 is so I have more freedom for editing (if I can figure out how to make vegas handle it) when It comes to my face cam. I record the gameplay and my camera "seperately" but still in the same video if that makes sense.

ANYTIME i try to play or pause the preview it crashes with the 20 CQP from OBS

This is exactly what I am talking about right here. This is a 20 CQP recording, Im using 5% of my ram for dynamic preview, and it doesn't matter what preview setting I select it still does this. In the video I looped a region to try and watch it to make sure I got the effects and all right, but just the audio plays when I start it and the frame section below the preview just has the dots like I showed and when I pause it crashes.

@JakeGetCake Did you also set the keyint length (don't leave it at 0 or auto in OBS)?

Can you share screenshots of all of your OBS settings?

Is your NVIDIA driver recent? I'm using the latest studio driver on my system.

20 is fine for a quality level and reducing it further won't affect crashing. VBR and CQP are two ways to get to the same place- you can see with MediaInfo exactly what bitrate it's ending up at. (so no VBR won't help).