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

Back to post

Comments

3POINT wrote on 8/15/2020, 5:17 AM

Is there maybe a render time restriction in the trial of Vpro18?

As EricLNZ asks, what's on the timeline at 84%? Does that part play in the preview?

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

I think the time limit is 2 minutes, this project is well short of that.

EricLNZ wrote on 8/15/2020, 5:22 AM

Looking at fr0sty's screen grab there's nothing of significance at 84%. It's just one clip, which has been slowed down. So we need to look for another clue.

3POINT wrote on 8/15/2020, 5:25 AM

@fr0sty Showing that something works at your system is no solution to @Jonathan-Burnett 's issue. It's only more frustrating.

3POINT wrote on 8/15/2020, 5:27 AM

When a clip is slowed down, resampling becomes active, maybe a different setting in Vpro17 and Vpro18.

Marco. wrote on 8/15/2020, 5:33 AM

84 % is more or less exactly where the second timeline event starts.

Marco. wrote on 8/15/2020, 5:39 AM

And if you zoom into that time you will see there's something odd.

There's a 2-frame-segment which looks like it does not belong to the project. Try deleting this 2-frame-event and try anew.

3POINT wrote on 8/15/2020, 5:42 AM

@Marco. Explains everything. On my smartphone I couldn't see those details, looked like one event.

Marco. wrote on 8/15/2020, 5:49 AM

I just saw these strange letters might just be a smaller GUI issue and this disappears if you zoom into the timeline even more. Though that 2-frame event between does not seem to make sense there.

EricLNZ wrote on 8/15/2020, 5:53 AM

Well spotted Marco, even on my desktop I hadn't noticed the second event.

3POINT wrote on 8/15/2020, 6:01 AM

It's indeed just 2 frames of video on top of the picture. Besides the rendering works also fine at my PC, this must be the reason for render hang.

3POINT wrote on 8/15/2020, 6:04 AM

I just saw these strange letters might just be a smaller GUI issue and this disappears if you zoom into the timeline even more.

When you move the 2frame video event to the right it becomes readable:

fr0sty wrote on 8/15/2020, 7:38 AM

@fr0sty Showing that something works at your system is no solution to @Jonathan-Burnett 's issue. It's only more frustrating.

I told him I'd try to reproduce the issue on my machine, since I also had an AMD GPU. That was me keeping my word.

Jonathan-Burnett wrote on 8/15/2020, 12:17 PM

It's indeed just 2 frames of video on top of the picture. Besides the rendering works also fine at my PC, this must be the reason for render hang.

And BINGO, that WAS the detail that was triggering the hang in v18. I had not seen it myself because I hadn't zoomed in that closely and it was indeed and unintentional artifact of my editing. When I removed it, v18 was finally able to fully render the project!

So, that mystery is resolved! What the development team might want to ponder is why v18 tripped up on it when v17 didn't have any issue with it? Also, Vegas shouldn't hang so thoroughly that you cannot cancel the render using the interface. Killing the task from Task Manager shouldn't be necessary.

Many thanks to everyone who took the time to download the project files and to play with the data. Your interest and thoughts are much appreciated!

Jonathan

EricLNZ wrote on 8/15/2020, 7:11 PM

So, that mystery is resolved! What the development team might want to ponder is why v18 tripped up on it when v17 didn't have any issue with it?

Also why your machine tripped over it and others didn't.

Anyway your problem is at least solved.