Vegas Pro 18 hangs during render and can't be cancelled

Jonathan-Burnett wrote on 8/14/2020, 6:29 PM

I mentioned this within a different problem post, but I wanted to break it out so it wasn't lost.

I'm trialing v18 as a regular and long time user of v17 (going back to v8). I was simply testing a completed v17 project to compare rendering speeds and this very tiny project never completes rendering under v18. Under v17 this is about a 60 second render but under v18, it gets to 84% complete and then hangs. I've waited as long as 30 minutes and it doesn't progress, though it reports that is consuming about 8% CPU.

That's bad enough, but the CANCEL button on the render dialog can't cancel the render. Even attempting to close out Vegas Pro can't seem to cancel what its hung up on. The only way to terminate it is go into Task Manager and kill the process, and fortunately THAT works!

I'm attaching a progression of screen captures to demonstrate the various things.

Someone suggested I install AMD's "pro" driver set, which I did but did not make any difference in this behavior. I presume to further analyze and debug you'll need more details. Just request and I'll provide.

Thanks,

Jonathan

Comments

fr0sty wrote on 8/14/2020, 7:00 PM

I notice free disk space says "--"... do you have sufficient room on the drive?

Jonathan-Burnett wrote on 8/14/2020, 7:07 PM

I render to a NAS device that has about 9TB free...the same as I do with v17.

fr0sty wrote on 8/14/2020, 7:10 PM

Does the same thing happen when rendering to local storage?

Former user wrote on 8/14/2020, 7:15 PM

Did you want to upload the video and project files to google drive or similar so others can see if they have the same problem?

And if it's ungodly large, the smallest project media files you have the same problem with

Jonathan-Burnett wrote on 8/14/2020, 7:17 PM

Does the same thing happen when rendering to local storage?

I just tried to my local SSD and the answer is; YES, it still hangs at the same place.

Jonathan-Burnett wrote on 8/14/2020, 7:18 PM

Did you want to upload the video and project files to google drive or similar so others can see if they have the same problem?

And if it's ungodly large, the smallest project media files you have the same problem with

Sure, I can do that. They are not very large as it is a tiny project. I'll set this up on DropBox and then post a link.

Here's the link to the project files: https://www.dropbox.com/sh/f6revru9ll6jigm/AADqIlpek67zFDFy6rkiuLrta?dl=0

Thank you.

fr0sty wrote on 8/14/2020, 7:56 PM

Thank you. I have a render going right now, but as soon as it finishes, I'll give this a try and see if I can reproduce it.

Jonathan-Burnett wrote on 8/14/2020, 8:04 PM

What is Lightning in the sky - v18.mp4 ?

I can't actually read it on my computer, and vegas wont' load it

Also could you include your project veg file

Sorry, I thought I had dropped that in too. It's there now. Thanks!

Jonathan-Burnett wrote on 8/14/2020, 8:07 PM

What is Lightning in the sky - v18.mp4 ?

I can't actually read it on my computer, and vegas wont' load it

Sorry, I apparently dragged that file instead of the .veg file. What you tried to open was the render file that didn't finish. Just for comparison purposes, I just added the v17 rendered file in case you wanted to see it.

Former user wrote on 8/14/2020, 8:20 PM

I have basically the default settings for VP18. it rendered without a problem to AVC via voukoder NVENC. I"ll try the internal encoder later too, but normally it's not the encoder stage that causes the crash it's the rendering part

Jonathan-Burnett wrote on 8/14/2020, 8:24 PM

I have basically the default settings for VP18. it rendered without a problem to AVC via voukoder NVENC. I"ll try the internal encoder later too, but normally it's not the encoder stage that causes the crash it's the rendering part

I haven't tried rendering it any other way than to HEVC

Dexcon wrote on 8/14/2020, 8:35 PM

The same thing happened to me yesterday during testing rendering between VP17 and VP18 - but in reverse.

I tested rendering 20 mins of a 4K project in VP18 using a custom MAGIX AVC/AAC MP4 template to 1920x1080 25fps. It worked fine and the render finished without a problem. Then going to the same 20 mins segment of the same project in VP17 (using the VP17 version of the .veg file) and using the same custom MAGIX AVC/AAC MP4 template, the render stalled at 23% and wouldn't proceed even after half an hour. Many attempts at cancelling the render were unsuccessful and VP17 had to be closed by the Task Manager. BTW, VP18 was not open at the time of doing the VP17 render, but VP18 could have been lurking in the background as has been an issue with VP for some years.

The computer was then rebooted and another attempt was made to render the same 20 mins segment in VP17 using the same render template - this was successful.

It seems that both VP17 and VP18 use common render templates as custom templates I created in VP17 auto appeared in VP18 and vice versa

My 'voodoo reasoning' conclusion is that the same render template can't be used with VP17 and then VP18 - and vice versa - without first rebooting the computer between the two renders, the reboot fully clearing the first used VP version from the computer's memory.

Former user wrote on 8/14/2020, 8:38 PM

Oh, well that's differnet, maybe it is a hardware/driver problem if you're using hardware encoding. I tried with my Nvidia card using HEVC hardware encode but you've got a AMD Vega can't haven't you. Frosty would be able to test your project better

john_dennis wrote on 8/14/2020, 11:03 PM

@Jonathan-Burnett @Dexcon

I copied the assets from the Vegas 18 project into a Vegas 17 project and rendered to templates customized in 17 and 18. Then, I did the same in 18 with a template saved in 17. I didn't experience anything unusual in this effort. Here are my results:

Jonathan-Burnett wrote on 8/15/2020, 2:15 AM

It is interesting how other can render this project in v18 and I can't. No idea what environmental changes exist between my system and yours but the fact remains this project DOES render fine in MY environment under v17, so within my domain, the only thing that changed is the version of Vegas Pro. I am running the trial version and trust that's not a factor but I think I would be stupid to upgrade to v18 knowing it doesn't work as well for me as v17 does...

john_dennis wrote on 8/15/2020, 2:25 AM

I'm also running the trial at the moment.

3POINT wrote on 8/15/2020, 2:40 AM

It is interesting how other can render this project in v18 and I can't.

Give Voukoder a try to render your project. I never faced a render issue with Voukoder AVC/HEVC but constantly with Magix AVC/HEVC.

Jonathan-Burnett wrote on 8/15/2020, 2:55 AM

It is interesting how other can render this project in v18 and I can't.

Give Voukoder a try to render your project. I never faced a render issue with Voukoder AVC/HEVC but constantly with Magix AVC/HEVC.

So, I wasn't familiar with Voukoder but I found it (v6) and I installed it and the Vegas Pro 18 connector. When I went to render, I have NO choices of codec, so I went with the default whatever that was. It began to render but it did not use my GPU, though it did consume memory on the graphics card. Regardless, it got to 84% and hung too:

3POINT wrote on 8/15/2020, 3:34 AM

When it also still renders till 84%, then I guess something is definitely wrong in your project. What? I can't tell you, but is probably not codec related.

Former user wrote on 8/15/2020, 3:38 AM

You may have already mentioned this, but what happens if you do a software encode, a standard avc, does it work with vp18?

If it does, that would point to some problem with vegas and VCE HEVC encoder, that affects you but not everyone

EricLNZ wrote on 8/15/2020, 3:39 AM

When it also still renders till 84%, then I guess something is definitely wrong in your project. What? I can't tell you, but is probably not codec related.

Yes, if it always hangs at 84% have a close look at what's on your timeline at that point. Source material, FX applied etc.

Jonathan-Burnett wrote on 8/15/2020, 3:44 AM

When it also still renders till 84%, then I guess something is definitely wrong in your project. What? I can't tell you, but is probably not codec related.

So I took your suggestion and deleted the V18 project and instead opened up the V17 project file, the one that renders just fine in Vegas Pro 17. When I had V18 try to render this V17 project file, it once again got to 84% and stopped.

The project file is not broken for VP 17 and if it doesn't work in VP18, that sounds like a bug to be fixed to me...

EricLNZ wrote on 8/15/2020, 4:04 AM

that sounds like a bug to be fixed to me...

Maybe, but it won't get fixed until it can be identified. What is on your timeline at 84%?

fr0sty wrote on 8/15/2020, 5:15 AM

Got around to rendering your project. Here's my results.

System Specs:

OS: Windows 10.0.18363 Build 18363

CPU: Ryzen 7 1800x

GPU: AMD Radeon VII

RAM: 64GB 3000mhz DDR4

HDD: OS and media on the same solid state NvME HDD, on the windows desktop.

Codec used: HEVC (1080p 25fps AMD VCE Preset)