render stuck at 99% and the counter is running....

michael-leonard wrote on 12/27/2017, 9:16 AM

Hi all, I'm hoping there is some community wisdom that some of you can share.

I have a project that I'm trying to render. It is a little over 2h in length, involves 6ch of video and audio, and all of the video is 1920x1080 29.97fps. Nothing fancy going on. The vast majority of the total time is one track of video and audio, with a "bug" overlaid in the bottom right.

Here's the deal. No matter what I've tried in rendering, it stops at 99%, and the elapsed time counter continues to run. The preview runs on it's marry way the whole time, through to the last frame, then goes black when 99% is hit. I did let it run up to 4hrs after it reached 99% just to be certain that I wasn't being impatient with it closing the file. This has never happened in the past. And I have rendered more complex edits that have exceeded 2hrs.

I'm rendering to the same MAGICS mp4 for internet 1920x1080x32 @ 29.97 as I have used in the past

Things I've tried:

  • I always keep my CPU affinity limited to 5 of my 8 cores
  • I have tried limiting the data rate of the video output as low as 8kbps (no change)
  • I have tried both GPU and no GPU rendering (no change)
  • I have also tried other pre-defined render options, no dice.

My system:

  • Win 10
  • i7-6700 @ 4Ghz (4 physical, 8 logical cores)
  • 64gb RAM
  • 2 gpus (NVIDIA 970 4gb and 1060 6gb)

Nothing has changed in the software or hardware, not even a Windows update.

Any help, or nudges in the right direction would be greatly appreciated.

Comments

Former user wrote on 12/27/2017, 9:21 AM

Does it do it on all projects or just this one?

michael-leonard wrote on 12/27/2017, 9:57 AM

Hi David-tu and Cornico.

To answer your questions.

Just this project is affected, so it's a totally new issue. Right now I'm trying to render it in two chunks. First half totally fine. I'll know about the second half in about 20min.

As for total free space, I have just over 400gb free on the target drive. The project is stored in a sub folder of the same physical drive. I did try a target drive other than the one where the project is stored, same result... In that case the target drive had about 200gb free. Neither of these drives are the system drive.

michael-leonard wrote on 12/27/2017, 10:12 AM

Okay, new news.

Rendering the second half just failed inthe same manner. Stuck at 99% complete, counter still running.

This seems to tell me that it has nothing to do with the length of the project or the processing needs.

Another worth while note, I can't cancel the render. It just sits there when I do. I actually have to go into the task manager and halt the program. Only then do I get the Vegas error report screen.

Any thoughts?

diverG wrote on 12/27/2017, 10:17 AM

OK you now know it fails in the back half.  Split that in two and render each half.  Then repeat again.  Eventually it will fall to maybe 1 clip.  Just bad luck when this happens.

Sys 1 Gig Z-890-UD, i9 285K @ 3.7 Ghz 64gb ram, 250gb SSD system, Plus 2x2Tb m2,  GTX 4060 ti, BMIP4k video out. Vegas 19 & V22(250), Edius 8.3WG and DVResolve19 Studio. Win 11 Pro. Latest graphic drivers.

Sys 2 Laptop 'Clevo' i7 6700K @ 3.0ghz, 16gb ram, 250gb SSd + 2Tb hdd,   nvidia 940 M graphics. VP19, Plus Edius 8WG Win 10 Pro (22H2) Resolve18

 

Former user wrote on 12/27/2017, 10:38 AM

Yep, sounds like a bad clip.

michael-leonard wrote on 12/27/2017, 11:01 AM

Yup, Just found the bad clip. Right at the very end...

So riddle me this Batman.

This clip is used twice in the timeline. At the intro and at the outro. Same clip, and it is on the same channel, just duplicated as a second instance.

What make a clip "go bad?" Other than having negative influences in it's life :-)

michael-leonard wrote on 1/9/2018, 8:28 AM

Hi all, sorry for taking so long to reply back.

Cornico, I did exactly as suggested and the issue was resolved. It appears that previously I had created the instance of this clip by making a duplicate reference to the source file. The second time I had Vegas create an actual duplicate. Issue resolved.

I really appreciate all the fast help here everyone.

karma17 wrote on 1/10/2018, 2:52 AM

That is interesting. I had the same type of issue when I copied multiple clips. It wouldn't render properly and only by rendering out the copied portion on its own, then bringing it back in under a different name, would it finally render. So sometimes a failed or stalled render is due to a single faulty clip. And clips that are copied are probably the first prime suspects.

ivanLeal wrote on 10/18/2018, 7:23 AM

 

 

it worked for me, but it was not enough to make copies of the clips to work, you have to delete the track of the clips and redo with the copies.