Trying to render a video, but it keeps stopping at 64%

enenera wrote on 9/7/2019, 11:46 AM

So I've been editing a video for about a week and now it's finished and I want to render it. But whenever I try to render it, it literally renders up to 64% and then it freezes and stops rendering. I usually have to go to the task manager and kill the Vegas 15. I have a Ryzen 5 1600, GTX 1080 and I'm rendering at 1080p 60 FPS (Nvenc) from 1440p.

This actually happened to me recently with my other videos and I really don't know what's causing it. I tried turning off GPU Accerelation but no luck. The render timer keeps going but the percentage/preview just stops rendering.

Any help is appreciated, more information can be provided.

 

http://prntscr.com/p33pmx

Comments

Musicvid wrote on 9/7/2019, 11:51 AM

You have a rogue event on the timeline at 64%.

Identify it, remove it from your project, and carry on.

j-v wrote on 9/7/2019, 12:01 PM

What and where is your renderlocation?
Which codec you are rendering with, AVC or HEVC?

Why did you made a selection of the timeline?

Last changed by j-v on 9/7/2019, 12:05 PM, changed a total of 1 times.

met vriendelijke groet
Marten

Camera : Pan X900, GoPro Hero7 Hero Black, DJI Osmo Pocket, Samsung Galaxy A8
Desktop :MB Gigabyte Z390M, W11 home version 24H2, i7 9700 4.7Ghz,16 DDR4 GB RAM, Gef. GTX 1660 Ti with driver
566.14 Studiodriver and Intel HD graphics 630 with driver 31.0.101.2130
Laptop  :Asus ROG Str G712L, W11 home version 23H2, CPU i7-10875H, 16 GB RAM, NVIDIA GeForce RTX 2070 with Studiodriver 576.02 and Intel UHD Graphics 630 with driver 31.0.101.2130
Vegas software: VP 10 to 22 and VMS(pl) 10,12 to 17.
TV      :LG 4K 55EG960V

My slogan is: BE OR BECOME A STEM CELL DONOR!!! (because it saved my life in 2016)

 

enenera wrote on 9/7/2019, 12:17 PM

You have a rogue event on the timeline at 64%.

Identify it, remove it from your project, and carry on.

I tried that and replaced it with another clip. It still is stopping at 64%. What should I do now? Thanks

enenera wrote on 9/7/2019, 12:20 PM

What and where is your renderlocation?
Which codec you are rendering with, AVC or HEVC?

Why did you made a selection of the timeline?

It's on my SSD which is NVME. I still have 60GBs available so I don't think storage is a problem. It's rendering to a file called videos also where the VEG project is.

I'm using the AVC codec, I haven't had any issues with it until now.

I made a selection of the timeline because that's usually how I tell Vegas to only render that selection because it's not pictured, but I have some other scrap clips off to the side.

 

Musicvid wrote on 9/7/2019, 12:27 PM

https://www.vegascreativesoftware.info/us/forum/faq-how-to-post-mediainfo-and-vegas-pro-file-properties--104561/

j-v wrote on 9/7/2019, 12:50 PM

@enenera Thanks for the info.
Have you checked this setting?

met vriendelijke groet
Marten

Camera : Pan X900, GoPro Hero7 Hero Black, DJI Osmo Pocket, Samsung Galaxy A8
Desktop :MB Gigabyte Z390M, W11 home version 24H2, i7 9700 4.7Ghz,16 DDR4 GB RAM, Gef. GTX 1660 Ti with driver
566.14 Studiodriver and Intel HD graphics 630 with driver 31.0.101.2130
Laptop  :Asus ROG Str G712L, W11 home version 23H2, CPU i7-10875H, 16 GB RAM, NVIDIA GeForce RTX 2070 with Studiodriver 576.02 and Intel UHD Graphics 630 with driver 31.0.101.2130
Vegas software: VP 10 to 22 and VMS(pl) 10,12 to 17.
TV      :LG 4K 55EG960V

My slogan is: BE OR BECOME A STEM CELL DONOR!!! (because it saved my life in 2016)

 

enenera wrote on 9/7/2019, 1:03 PM

@enenera Thanks for the info.
Have you checked this setting?

Those are the exact settings I have for rendering.

j-v wrote on 9/7/2019, 1:13 PM

Then I'm out of suggestions for possible causes.
Did you try what @Musicvid suggested in his first comment?
A further possible workaround maybe is to render in 2 or 3 parts and stitch them together with MP4Joiner.

 

met vriendelijke groet
Marten

Camera : Pan X900, GoPro Hero7 Hero Black, DJI Osmo Pocket, Samsung Galaxy A8
Desktop :MB Gigabyte Z390M, W11 home version 24H2, i7 9700 4.7Ghz,16 DDR4 GB RAM, Gef. GTX 1660 Ti with driver
566.14 Studiodriver and Intel HD graphics 630 with driver 31.0.101.2130
Laptop  :Asus ROG Str G712L, W11 home version 23H2, CPU i7-10875H, 16 GB RAM, NVIDIA GeForce RTX 2070 with Studiodriver 576.02 and Intel UHD Graphics 630 with driver 31.0.101.2130
Vegas software: VP 10 to 22 and VMS(pl) 10,12 to 17.
TV      :LG 4K 55EG960V

My slogan is: BE OR BECOME A STEM CELL DONOR!!! (because it saved my life in 2016)

 

Andrew-Lenczycki wrote on 9/7/2019, 1:29 PM

See what frame the render is stopping at (it will be displayed at the bottom of the view viewing window), then look thru all media that are on the timeline at that frame. I have (in the past) found that it was the result of a Sony Fx being applied at that point. An example was the effect was set to go to 100% on the offending frame. When I changed the effect to go to only 99% the file rendered fine.

 

karma17 wrote on 9/7/2019, 1:47 PM

Some times I feel like a rogue event.

You might not like my solution, but I'd suggestion splitting the clip in two. Render to 63 % to some good edit point, then render the other 37%. Render them as sony xavc mxf files, then re-render those two files in whatever format you want. Not an elegant solution but usually works for me when I have issues.

The other thing is sometimes you can have that happen when the source files are on the same drive as the disk rendered to. However, maybe you are already doing that.

It is hard to say because you don't get a specific error message.

Musicvid wrote on 9/7/2019, 8:23 PM

Are there any effects like NewBlue on the timeline?

Grazie wrote on 9/7/2019, 11:48 PM

@enenera - I’ve had this. You need to stop thinking it’s worked before. Well, it’s happening now. As others suggest, you need to nail the Issue Area. Render in Chunks of, say, 20% at a time. Progressively move through the Timeline. Once you get to the “choking” point, now Render well beyond. You say it happens at 64%, then move to 70% and render a Selection. Once you approach/get to the Pinch point and it Fails, Render in small Chunks. Hopefully you WILL identify the exact Region that’s creating the problem. You’ve not lost anything by doing this as you can CHAIN all your Renders back into your Final assemblage. But hopefully you’ll have an option to rectify the Gremlin!

Look, Vegas is choking on something. There’s some maths that’s going on that’s too much for your System. Do try my Regression Analysis approach. As I said, you’ll at least have a Chain of working Renders.