http://www.vegascreativesoftware.info/us/forum/updated-fixing-the-pale-screen-of-misery--122436/

It happened to me last week when I inadvertently dragged a camera raw still image to the timeline. It cleared up when I replaced it with a jpg file.

I'm not using any camera raw files, my stills are jpgs and it happens in many other cases besides dropping stills.

Click on John's link for some hints. He was just offering still photos as an example.

I looked at John's link. Turning GPU processing off might correct the issue but really handicaps performance and sets it back 10 years! I have 2 GPUs on my system and I want to use them. I bought hardware to use, not disable! My system is overspec in every way and I generally run Vegas without anything else running. My dynamic ram is set to the default of 200 MB and I have 32gb of system memory

While this hang can happen at any time it most often occurs after an edit when I hit play to preview the change. The preview actually starts and continues to run but VP is hung and you cannot do anything else but watch the spinning cursor until you hit the close a few times to get the stop working message.

This happens so often with every version of VP and on all different hardware configs I don't understand why it hasn't been fixed yet. Just fix it! It's very annoying and makes an otherwise pretty decent produce a pain to use!

I have 15-18 working here. For me 17 and 18 do much more with the GPU and are more stable than 15 or 16.

I'd reset Vegas (hold control-shift on Vegas startup) and see if it helps.

Beyond that use the Pro/Enterprise (not Adrenalin) AMD driver.

What media are you using?

I am using the AMD Pro/Enterprise driver. Vegas was just reinstalled (and reset) with the 527 update and the problem was there in my first project with it. I do think the GPU processing has improved with the latest updates to 18. I get very little if any lag on my timeline/preview and GPU encodes are much faster and with much better video quality then even with VP 17. I really noticed the improvement, now they just need to fix the bugs!

With as often as this happens, it has to happen to the developers too. How can they let it go without fixing it? I've been involved in software development for 40 years, from operating systems, device drivers, control systems, databases and user interfaces. If you see a problem it is the developers responsibility to investigate and solve it!

The developers might have a better chance of helping if you can isolate the problem. I haven't had a hang in a while. They've clearly put a lot of work into stability but that doesn't mean all problems for all users are fixed.

The suggestion above to disable GPU acceleration was to test- see if it helps.

Try one kind of media and then another. What's triggering the hang?

Actually, it's random and happens so often that it's not just happening to me! It's not really my job to track it down! I'm the customer, not the QA/development department!

Its not just me then! Yes I get random hangs - a white screen and 'program not responding' error, but if previewing at the time the audio continues. It's hard to pin down but it is always during the most 'basic' timeline editing.

In 17 it was fixed after one of the updates and I enjoyed uninteruppted editing until 18 when I was sad to see the problem return. In fact I copied a recent project from 18 into 17 just so i could get it finished. I've got so frustrated lately by these random hangs that I have trialled several other video editors but Vegas is just so efficient to use I cant find one I like. Other editors seem so clunky at the most basic editing level of assmbling and trimming clips on the timeline, cross fades, adding titles, stills etc and I wonder if the very speed at which one can navigate the Vegas timeline, move and trim clips and all while playing a full screen HD preview is part of the trouble. I do believe if I work more slowly there are less crashes, give a little time for an edit to complete before moving on.

These hangs are not while adding some unsupported file format or a corrupt video file, this is while working with media that has already be worked on and previewed many times, perhaps it has already been rendered sucsessfully. So how can it be the media content, or the hardware? And I can restart and do the same operation again no problem. How can it be that it can work for hours and then fail. Overheating cpu or gpu after a heavy edit? No indication it is but it is just as likely to occur from startup while still cold anyway. Hard drive errors? I tried different drives.

One thing I am convinced is an issue is the Dynamic Ram Preview setting. There is no doubt that this has to be 0 for rendering with NVEC to complete sucsessfully but if it is left at 0 during editing there are crashes and previewing is not smooth. The recommended 200MB seems a good choice. But why should this be! It's high time this was put to bed once and for all.

As V19 approaches I fear work on 18 will cease. 😟

I just wrote a question about this. Vegas locks up or crashes constantly!! Any ACTUAL FIXES or ANSWERS from the Developers??? PLEASE!

" I wonder if the very speed at which one can navigate the Vegas timeline, move and trim clips and all while playing a full screen HD preview is part of the trouble."

I've wondered about that. There does seem to be a lot of things to keep track of when doing and undoing.

And computers are very good at keeping track of stuff and not getting confused.

https://www.vegascreativesoftware.info/us/users/profile/john-rappl/ wrote: Does anyone else have similar hangs when editing?

Yes, I've had it for years. Almost every time it happens, I notice that the audio meter is green and freezes there. I wonder if it could have something to do with the audio as well as splitting and editing on the timeline.

Note that I have nVidia GPU so it probably isn't your AMD causing it. I have Intel CPU as you can see in Signature.

Good luck, john-rappl. Perhaps yours is fixed by now (almost a year later).

RonB_USA

@RonB_USA Hi, i very much doubt @john-rappl's probs have been fixed, my Vegas 19 (latest version) crashes & stalls, I think people like Vegas & come to accept that it'll crash at some point, bit like an old dog, you love it but it'll bite you now n then & occasionally crap on the carpet 🤷‍♂️

@RonB_USA Hi, i very much doubt @john-rappl's probs have been fixed, my Vegas 19 (latest version) crashes & stalls, I think people like Vegas & come to accept that it'll crash at some point, bit like an old dog, you love it but it'll bite you now n then & occasionally crap on the carpet 🤷‍♂️

@Former user I"ve been really impressed with VP19 532, not seeing any reason to upgrade. Probably mainly to do with the ripple bug being fixed, but in last 10 days or so coincidentally or not after a dual windows 10 upgrade i'm getting crashes for no reason at all, even simple stuff like very basic editing of OBS screen capture, no 3rd party FX used, no 3rd party FX,VST's installed recently.

NowVp19 532 is behaving more like Vegas used to. It shows how fragile Vegas is why every stability complaint about Vegas should be given credence. If I had just installed VP19 532 and it behaved like it is now I'd be really upset, it's just lucky that it didn't and I know it's capable of behaving much better. I'll try 550 to begin with

For "me", I get a white screen of death (and I am looking at Task Manager to see what is happening if anything) when I first open and start editing. I'll use Task Manager to kill Vegas and restart. Sometimes, it will happen again. But on the 3rd try, I could edit for hours with no problem. The last project was 19 tracks of anything you can think of.

Why it would crash, I have no idea. And since I don't get the error sending window, can't give an answer. But again, after that crash or two, it's solid for me.

On our very new Dell laptop with NV3070Ti I was getting crashes when editing at 3x speed.

So I ran some tests using our 4-up Multi-View project, 3 cams are 1080p59.97 reasonably high bitrate, 1 cam is 4K 150Mbps. Project is set to 108030p.
- Intel GPU for decode (File tab) and NVidia for "Video Processing" (display)
- NVidia for decode and Intel for video processing
- Tried with Dynamic RAM preview on and off

I would keep task manger (performance monitoring) on top, and playback our multiview at 1x, 2x and 3x speeds. (I did not take pictures... will do when I have more time).

What I observed was:
- Dynamic RAM preview being disabled slowed performance a lot
- As playback speed increases, the Decode strain goes up significantly. (video display GPU goes up too but not as much).
- When using NVIDIA for decode, when it went above 2.5x playback speed it would max out the GPU and framerate dropped from 30fps to 4 or 5fps.
- Using NVIDIA for display and Intel for Decode ("recommended" default Vegas uses), performance is good but it crashed when GPU spikes happen.
- Using only Intel GPU for both decode and video playback seems very stable -- but does not perform as well at high speed playback when it's doing all the work

I also noted that when the preview window is moved from my external monitor (HDMI connection) to the laptop's built-in monitor, the GPUs were used differently. Sometimes it caused the NVIDIA gpu to spike when I moved it internal, other times it caused it to stop being used all together?!


My beloved is currently editing on that box and is getting quite frustrated. Even editing a single camera's 4K footage is crashing on her regularly -- Dynamic RAM *is* currently enabled.. and Intel card is displaying decoding.. *sigh* No fun. No fun. She noticed that the first many frames of each video clip are GLITCHY on playback. I tested using Windows Media player on her computer and same thing.. glitchy first bit of each clip. On my other computer the clips look fine even at the start! I then observed playback with PerfMon open using Media Player, and see it's using the Intel card for playback on the internal display -- when dragged to the external monitor the glitches go away and it's using the Nvidia card!

SO -- Intel card is making our Vegas more stable than the NVidia card. Intel card is also causing glitches at the start of our 4K footage! I tested within Vegas -- disabled GPU for playback (video tab) and the glitches were still there. Disabled GPU for File I/O (decode) and the glitches disappeared. So... Intel GPU decoding our 4K footage causes glitches in beginning frames!

This is repeatable. But also not a Vegas-exclusive bug. Report to Windows? Intel? Dell?

At least it renders fast? What to DO?! $1800 laptop and it's glitchy with our edits. grrr

On our very new Dell laptop with NV3070Ti I was getting crashes when editing at 3x speed.


I would keep task manger (performance monitoring) on top, and playback our multiview at 1x, 2x and 3x speeds. (I did not take pictures... will do when I have more time).

What I observed was:
- Dynamic RAM preview being disabled slowed performance a lot
- As playback speed increases, the Decode strain goes up significantly. (video display GPU goes up too but not as much).
- When using NVIDIA for decode, when it went above 2.5x playback speed it would max out the GPU and framerate dropped from 30fps to 4 or 5fps.

@RedRob-CandlelightProdctns The glitch problem I don't know anything about, the slow down you are seeing with 2.5x playback doesn't really max out your GPU decode, Vegas gets overloaded, it can't process the frames from the GPU decoder and that sets of a situation where the GPU decoder keeps spitting out frames waiting for an acknowledgment from Vegas, at least I assume that's what happening. I mentioned in another thread that you should try Legacy AVC if it's compatible with your media. It is more efficient and side steps the GPU decode problem. You will notice however Vegas still has problems with the edit points, but recovery is better than with SO4 and GPU decoder

I think you mentioned with an AMD laptop that you returned you did not see that problem which is unusual, in previous testing with users, people experience the lag the same with the same AVC's. some AVC's are more processing heavy than others. AVC 4K60 without B frames can be edited like a knife through butter with Vegas, but in 2022 no B frames is very unusual, B frames require a higher processing load