(Yet Another) VegasPro 18 Render Crash/Hang Post

sakendrick wrote on 10/12/2020, 9:25 AM

If you been following my posts - I'm in a world of hurt... just upgraded from MSP to VP18 this weekend and spending more time troubleshooting than being productive. The latest issue is rendering hanging or sometimes the app just shutting down as soon as I go to Render As - no errors, nothing.

I've tried almost everything listed here: https://www.vegascreativesoftware.info/us/forum/faq-how-can-i-stop-vegas-pro-hanging-or-crashing-during-rendering--104786/ and all the suggestions from Scrapyard films (on youtube)

There's lots of conflicting information when you google

- use acceleration, don't use acceleration

- set your ram to super high, set it zero

I've tried different file formats for rendering. I've deleted my app temp folder.

The most common issue is it gets stuck at 29%... I've investigated the file around 29% through it's timeline and nothing peculiar there. The weird thing is it has gotten stuck at 29% when I render the whole project (4 minute video) and when I render just a small part of the project.

The file content is mostly multiple videos (in tiles on the screen, sometimes up to 8), and track motion on various tracks, but not for the full 4 minutes, only in parts. There are no fx on the video, haven't even got to coloring yet. But all that said - I have a much simpler version with no track motion that renders fine in MSP 17 but won't render in Vegas.

I'm desperate for help - this is my last day to work on this project. Any suggestions welcome.

Back to post

Comments

Michael-Crawford wrote on 10/16/2020, 11:54 PM

Respectfully, @RogerS, I disagree. I see plenty of evidence in these forum threads that people are broadly having major issues with crashes and rendering in the very fact that so many of the incidents are so similar in nature (e.g., renders hanging at consistent points in the timeline with no apparent cause, etc.). Repeatable errors, albeit with different file types or render formats, are fundamental flaws in the coding of any software product. If MS Word, for example, crashed or stalled when users wrote different sentences or words we wouldn’t blame it on their specific choice of words or sentences. We would say there is an overall issue with the software. As you point out yourself, in the case of VP 18, there are observable “patterns... specific to the system or types of files.” Starting a new thread at this point to look for help would accomplish little at this point because I see that no one has yet to identify a specific solution that works to resolve what, in essence, is the same issue or set of issues. This version is deeply flawed, in my view.

walter-i. wrote on 10/17/2020, 3:22 AM

Respectfully, @Michael-Crawford I disagree.
I am very satisfied with both VP 17 and VP18.
If you are really looking for help - open your own thread - this is the only way to keep this forum clear and to specifically address your case.

Michael-Crawford wrote on 10/17/2020, 7:12 AM

walter-i, I don’t want to get into a p*ssing match but I will make one last observation in a thread that has clearly gone in many different directions. I should note that I edit 8-10 major programmes and a half-dozen shorter videos per week, so I am giving VP 18 a good workout. As proof that VP 18 is flawed, I recently took a fairly large project that was crashing frequently and ultimately failing to render at all, and I exported an EDL file. I then imported that EDL into VP 17. Same files, same cuts, same transitions, and same effects. The project then rendered in VP 17 without ANY issue at all and in a fraction of the time I am seeing in VP 18. For mission-critical edits, VP 18 simply cannot be trusted at this time in my view.

RogerS wrote on 10/17/2020, 8:04 AM

Respectfully, @RogerS, I disagree. I see plenty of evidence in these forum threads that people are broadly having major issues with crashes and rendering in the very fact that so many of the incidents are so similar in nature (e.g., renders hanging at consistent points in the timeline with no apparent cause, etc.). Repeatable errors, albeit with different file types or render formats, are fundamental flaws in the coding of any software product. If MS Word, for example, crashed or stalled when users wrote different sentences or words we wouldn’t blame it on their specific choice of words or sentences. We would say there is an overall issue with the software. As you point out yourself, in the case of VP 18, there are observable “patterns... specific to the system or types of files.” Starting a new thread at this point to look for help would accomplish little at this point because I see that no one has yet to identify a specific solution that works to resolve what, in essence, is the same issue or set of issues. This version is deeply flawed, in my view.

Sitting here and also on two Vegas Facebook groups, I don't see that. I see fewer issues than we had under VP 17 with GPU acceleration.

For those with problems, there are a few themes, however. One is black frames and glitches on render- dynamic ram preview is one apparent cause, and setting it to zero doesn't help. For freezes at a certain place during the render if zeroing out dynamic ram review doesn't help, next step is to inquire about what kind of footage. Often it's variable frame rate footage from phones. Transcoding using Handbrake and replacing the files can solve these issues. I'm seeing some issues with AMD GPUs not being found or used properly by Vegas. Fewer issues on the NVIDIA side, and where we do see them, updating to recent studio drivers often helps (it did for me).

For your Word example, I actually had issues many years back where it bluescreened and took down Windows entirely. After a few times I realized what triggered it- the scroll wheel of my mouse. It took some time to identify the core issue, which wasn't Word or my mouse, it was my graphics card which for some reason crashed when that kind of scrolling occurred. A driver update fixed it.

I agree software should work and don't blame the user. If we are methodical we can identify the source of the problems. I've volunteered to take projects and clips from other users to test and see if I have the same issue on my machine. Where Vegas is the source and we can verify the situations where it occurs, we can help the small team at Magix speed the development of fixes.

Anyway, as a NVIDIA user working with mostly Sony and Canon .avcs I don't personally have problems, whereas I did with 15-17 (final builds of each were okay).

set wrote on 10/17/2020, 8:08 AM

Like I observe as usual.... one user may found VP17 and/or VP18 fully compatible, while other user found the opposite...

Dexcon wrote on 10/17/2020, 8:09 AM

Worst VP version ever IMO was VP11 - only the last build provided any stability.

sakendrick wrote on 10/17/2020, 9:01 AM

Just my 2 cts --- recall my problems started when I moved away from my $80 version of MSP 17 to Vegas Pro 18. My project was rendering (quickly) in 17 prior to moving to 18 Pro, which I did for features that ultimately I couldn't use (because of instability). @set makes a good point that likely the issues in 18 are tied to certain hardware configurations or project attributes (and perhaps other configurations, projects didn't work as well with earlier versions).

In my case I think the contribution to my resolution was using the Vegas recommended drivers for my system, and converting all files to CFR (again - two issues that I didn't have with MSP 17). I'm also surprised at the lack of available technical support for a pro-level product. No number, no chat, I logged a ticket on the 11th, still no response. Thankfully there is an awesome community of supportive users to help one other. That speaks volumes.

All in - it is extremely impressive software and if 18 is a relatively new release - from a guy that has worked in the software industry for 25 years, not overly surprised that there may be some improvements needed. Hanging on hope that it will improve.