Vegas Being Very Slow and Unresponsive

DarkSparkish wrote on 2/20/2020, 3:47 AM

Doesn't seem like anyone has talked about this issue before, but I am currently working on a YouTube Poop of a nearly 2-hour movie. And suddenly it started becoming really slow, and I've had this issue for quite sometime now. It takes nearly a minute or more to simply move a clip around, splitting a clip takes nearly 40 seconds and pretty much doing anything within the timeline takes forever before they take action. It happened in Vegas Pro 14 and it still happens in Vegas Pro 17 with its latest build (Build 421). I did fix the problem by rendering what I have worked on to a new project, but then the problem arises again as the project went on. In addition to that, it also sometimes refuses to do anything and gives me a message telling me to open up a new project and it repedately displays this message until it stops. I use a pretty beefy computer (Which has a GTX 1070, AMD Ryzen 1700 CPU, 16GB RAM and an SSD which Vegas runs off of) so I don't think that the reason stems from my computer being "weak". And Vegas works pretty well otherwise on other projects. It's just this one specific project it struggles with.

I suspect it could be a RAM-thing, but I could be wrong on that. Does anyone know how I can fix the issue I'm currently having? Am I the only one who's experiencing it?

Comments

EricLNZ wrote on 2/20/2020, 4:29 AM

MediaInfo on your source footage might help others assist you.

DarkSparkish wrote on 2/20/2020, 7:34 AM

MediaInfo on your source footage might help others assist you.

Oh yeah. Here's the MediaInfo on the source.

General
Complete name                            : D:\Videos\Spider-Man- Into the Spider-Verse.mp4
Format                                   : MPEG-4
Format profile                           : Base Media / Version 2
Codec ID                                 : mp42 (isom/iso2/avc1/mp41)
File size                                : 16.5 GiB
Duration                                 : 1 h 56 min
Overall bit rate                         : 20.2 Mb/s
Movie name                               : Spider-Man: Into the Spider-Verse
Encoded date                             : UTC 2019-04-29 18:58:18
Tagged date                              : UTC 2019-04-29 18:58:18
Writing application                      : HandBrake 1.2.2 2019022300

Video
ID                                       : 1
Format                                   : AVC
Format/Info                              : Advanced Video Codec
Format profile                           : Main@L4
Format settings                          : CABAC / 4 Ref Frames
Format settings, CABAC                   : Yes
Format settings, Reference frames        : 4 frames
Codec ID                                 : avc1
Codec ID/Info                            : Advanced Video Coding
Duration                                 : 1 h 56 min
Bit rate                                 : 19.7 Mb/s
Width                                    : 1 920 pixels
Height                                   : 804 pixels
Display aspect ratio                     : 2.40:1
Frame rate mode                          : Variable
Frame rate                               : 23.976 (24000/1001) FPS
Minimum frame rate                       : 23.974 FPS
Maximum frame rate                       : 23.981 FPS
Color space                              : YUV
Chroma subsampling                       : 4:2:0
Bit depth                                : 8 bits
Scan type                                : Progressive
Bits/(Pixel*Frame)                       : 0.533
Stream size                              : 16.1 GiB (98%)
Writing library                          : x264 core 157 r2935 545de2f
Encoding settings                        : cabac=1 / ref=2 / deblock=1:0:0 / analyse=0x1:0x111 / me=hex / subme=6 / psy=1 / psy_rd=1.00:0.00 / mixed_ref=1 / me_range=16 / chroma_me=1 / trellis=1 / 8x8dct=0 / cqm=0 / deadzone=21,11 / fast_pskip=1 / chroma_qp_offset=-2 / threads=24 / lookahead_threads=4 / sliced_threads=0 / nr=0 / decimate=1 / interlaced=0 / bluray_compat=0 / constrained_intra=0 / bframes=3 / b_pyramid=2 / b_adapt=1 / b_bias=0 / direct=1 / weightb=1 / open_gop=0 / weightp=1 / keyint=240 / keyint_min=24 / scenecut=40 / intra_refresh=0 / rc_lookahead=30 / rc=crf / mbtree=1 / crf=1.0 / qcomp=0.60 / qpmin=0 / qpmax=69 / qpstep=4 / vbv_maxrate=20000 / vbv_bufsize=25000 / crf_max=0.0 / nal_hrd=none / filler=0 / ip_ratio=1.40 / aq=1:1.00
Encoded date                             : UTC 2019-04-29 18:58:18
Tagged date                              : UTC 2019-04-29 18:58:18
Color range                              : Limited
Color primaries                          : BT.709
Transfer characteristics                 : BT.709
Matrix coefficients                      : BT.709
Codec configuration box                  : avcC

Audio
ID                                       : 2
Format                                   : AAC LC
Format/Info                              : Advanced Audio Codec Low Complexity
Codec ID                                 : mp4a-40-2
Duration                                 : 1 h 56 min
Bit rate mode                            : Constant
Bit rate                                 : 426 kb/s
Channel(s)                               : 2 channels
Channel layout                           : L R
Sampling rate                            : 48.0 kHz
Frame rate                               : 46.875 FPS (1024 SPF)
Compression mode                         : Lossy
Stream size                              : 356 MiB (2%)
Title                                    : Stereo
Language                                 : English
Default                                  : Yes
Alternate group                          : 1
Encoded date                             : UTC 2019-04-29 18:58:18
Tagged date                              : UTC 2019-04-29 18:58:18

As you can see, the source is ripped from a Blu-ray using MakeMKV and then converted to MP4 using Handbrake. I did try to make a version of the video file that's at a lower resolution, but the problem still occurred. Maybe I should have tried it with a fresh and new project.

Either way, that's the MediaInfo on this source in particular.

fr0sty wrote on 2/20/2020, 9:06 AM

try to right click on your file, select "make video proxy", then, after it is finished, make sure your preview quality is set to either "preview" or "draft". This will enable the proxy you just created. See if that helps.

If not, toss another 16GB in there.

DarkSparkish wrote on 2/20/2020, 3:59 PM

try to right click on your file, select "make video proxy", then, after it is finished, make sure your preview quality is set to either "preview" or "draft". This will enable the proxy you just created. See if that helps.

If not, toss another 16GB in there.

I appreciate the advice. After reading your post, I did try to create proxies for pretty much everything, but unfortunately that didn't work out. Guess I need to bring in more RAM.

fr0sty wrote on 2/20/2020, 10:34 PM

Do the ususal, make sure gpu drivers are up to date, etc. first. Use Nvidia studio drivers. Maybe try a clean install of Vegas' latest version. If all else fails, consider a hardware update. I can't say adding 16GB will be your solution, so best to try everything first.

fifonik wrote on 2/21/2020, 3:05 AM

VP does not like footage with Variable framerate. You should re-encode it.

If you captured the video, you should adjust your capture program settings and encode it in constant framerate.

DarkSparkish wrote on 2/21/2020, 5:55 AM

VP does not like footage with Variable framerate. You should re-encode it.

If you captured the video, you should adjust your capture program settings and encode it in constant framerate.

I see. Well, sure. I'll try to re-convert the MKV-file in Handbrake so that it has Constant Framerate instead of Variable Framerate. I usually do that, but I might have just forgotten to do that with this source. Again, thank you for your advice and I'll try it out when I can. Good to know that Vegas doesn't like Variable Framerate sources.

DarkSparkish wrote on 3/5/2020, 5:53 AM

I am back again. I reconverted the source from MKV to MP4 setting Handbrake settings to "constant framerate". And while I highly appreciate the advice, it's unfortunately still really slow. Guess a RAM upgrade is the only thing I haven't tried yet now. If you guys have more suggestions, then keep em' coming!

Reyfox wrote on 3/5/2020, 6:09 AM

You can monitor your RAM usage with having TaskManager open.

I had basically the same build as yours except using AMD RX480 8GB video card. I recently upgraded to 3900X and 32GB of RAM. I've thought about 64GB down the road, but most of my projects are under 15min. I was working on a rather short (2min) but slightly complex video and was up to over 5GB of RAM used by VP.

IF you are running out of RAM, "virtual RAM" will start making use of your hard drive as additional RAM, which is much slower.

Open TaskManager and see what is happening. Also monitor heat in your case.

DarkSparkish wrote on 3/5/2020, 6:37 AM

You can monitor your RAM usage with having TaskManager open.

I had basically the same build as yours except using AMD RX480 8GB video card. I recently upgraded to 3900X and 32GB of RAM. I've thought about 64GB down the road, but most of my projects are under 15min. I was working on a rather short (2min) but slightly complex video and was up to over 5GB of RAM used by VP.

IF you are running out of RAM, "virtual RAM" will start making use of your hard drive as additional RAM, which is much slower.

Open TaskManager and see what is happening. Also monitor heat in your case.

Total RAM-usage is at 53%, though it seems to increase when setting "Dynamic RAM Preview" to a higher value. But it doesn't increase or decrease when doing any kinds of tasks such as cutting, moving and (The worst one) auto saves, despite taking forever for Vegas to do them. So it has at least half of its total RAM-amount that is still usable. CPU-usage increases when playing the video within the project and that's it and GPU-usage.... is 5% at most. I know GPU isn't much used in editing compared to CPU and RAM, but just wanted to say that.

Overall, while Vegas does use a lot of RAM, it doesn't use the entire 16 gigs to run and I don't see any abnormalities in task manager. Memory doesn't spike and neither does CPU-usage. I am assuming there must be something I need to fiddle with in order for the lag to stop.

j-v wrote on 3/5/2020, 7:27 AM

Are you able to give here screenshots of your used Projectsettings, the complete Vegas interface with this project loaded on the timeline, your settings at Options/preferences/Video and Options/preferences/ File I/O?

DarkSparkish wrote on 3/5/2020, 12:38 PM

Are you able to give here screenshots of your used Projectsettings, the complete Vegas interface with this project loaded on the timeline, your settings at Options/preferences/Video and Options/preferences/ File I/O?

Sure thing.

Also on a side-note, I don't think I have ever touched "File I/O" before. The MKV-reader looks rather tempting.

j-v wrote on 3/5/2020, 1:34 PM

1. Do you use the option Dynamic RAM preview a lot?
2. Set the I/O setting to use the NVDEC in stead of QSV

DarkSparkish wrote on 3/5/2020, 1:47 PM

1. I have used it before, but I am unsure what value to tune it to for the most optimal results.

2. I have done it now, thank you.

j-v wrote on 3/5/2020, 1:58 PM

1. I have used it before, but I am unsure what value to tune it to for the most optimal results.

Only when you use the option it is can be set to a non default amount, but If you don't to use it for no more than a few seconds you can use the default option and when you don't not use the option ,in the menu Tools you can set it to 0 and therefore free a lot of used RAM

DarkSparkish wrote on 3/5/2020, 2:16 PM

in the menu Tools you can set it to 0 and therefore free a lot of used RAM

Wait. Where in Tools is it? Or is it still in "Dynamic RAM Preview"?

fred-w wrote on 3/5/2020, 3:09 PM

He's talking about Dynamic Ram Preview.

j-v wrote on 3/5/2020, 3:09 PM

In Options/preferences/Video

DarkSparkish wrote on 3/5/2020, 3:21 PM

Yeah, I understand. But it was like he was implying some kind of setting under the "Tools" tab. But anyways, I have set Dynamic RAM Preview to 0. So far having done all the suggestions, I still haven't fixed the issue. But I really thank you guys for the suggestions I have gotten so far!

j-v wrote on 3/5/2020, 3:56 PM

But it was like he was implying some kind of setting under the "Tools" tab.

If you don't known that tool I'm sure you don't use it so set to 0 does not harm anything.
Here is the tool to use Dynamic RAM preview

DarkSparkish wrote on 3/6/2020, 10:03 AM

Oh right. I know about this one. I actually like to Shift + B a specific clip to get smoother playback. I have tried to Shift + B specific parts of my project to see if it will fix the issue before. It seemed to work, as it felt like it made the project smooth again like I was editing a normal project. Cutting clips happened in an instant, autosaving didn't take ages and it was all good. But once I saved and exited the software and got back on again, it was slow again, and I couldn't fix it again with Shift + B. It's like the problem fixes itself when it feels like it. It's annoying.

NickHope wrote on 3/6/2020, 10:41 AM

Work through this: https://www.vegascreativesoftware.info/us/forum/faq-how-can-i-make-my-video-preview-play-smoothly-in-vegas-pro--104624/

lachlan145 wrote on 2/27/2025, 4:34 AM

Hey, I've just had this behaviour (running the latest update in VP22) where everything became laggy and ridiculously slow. It's frustrating when you know your computer is capable and all of your other CPU and GPU intensive software is performing just fine but Vegas decides to be a pile of crap.

To be clear, I'm talking about the kind of slow/lag where you can't even move the mouse around without excruciatingly painful delays.

Interestingly, I found something that changed the behaviour INSTANTLY when I pulled out my network cable and turned off Wifi. When suddenly hit with no internet connection it worked perfectly.

This has only just happened and I'm trying to confirm exactly what the issue is, but obviously it's network related - so logging out of Vegas Hub is a first step, and I'll update if I have any further info.

Reyfox wrote on 2/27/2025, 9:37 AM

@lachlan145 I've not experienced anything of the sorts with my "capable" computer with the internet connected to it. I've never disconnected the internet.

What you have failed to do is provide the appropriate information as to what are the specs of your "capable" computer, and which build of VP22 you are using. In addition to what types of video you are using.

Here is a suggestion if you want a possible answer, start a new post, and include this INFORMATION ('B' and 'C') in that post with the issues you are having with specifics, not generalities.