Unable to finish a render in Vegas Pro 16

Zkuggi wrote on 11/9/2018, 7:35 AM

Update: I wrote original post below being fully frustrated after a week of failed rendering attempts. But here is a clear indicator on why I have stuck with Vegas and will continue to do so. This forum is full of clever people willing and able to help with strange issues that can come up with Vegas. My issue was solved within few hours after posting it here on the forum.

Really valuable.

__________________________

Just wanted to share my rendering experience and see if anyone has experienced similar behavior and possibly has some solutions.

Source material
I have edited a 60 minute long video that is a combination of 4096x2160 24p source videos from:

  • Olympus OMD em1 mark II - 8 bit
  • Panasonic GH5 - 10 bit 422 - V-Log

I am not doing any heavy effect work. Occasional neat video to fix noise in few scenes and then color grade the V-Log video using Magixs built in LUT filter.

The problem:
The program was pretty slow while editing the whole video. But once I prevented it from fully using all CPUs and stopped using thumbnail view in project explorer I managed to finish editing. Had maybe 3-4 crashes.

But now I have been trying to render the project for a week and it still has not been able to finish rendering. So far I have experienced:

  • 5 times Vegas Pro crashes to desktop on arbitrary point in the rendering.
  • 2 times it has managed to "finish" the rendering but then stays stuck at 100% indefinitely. Never allowing me to close the render dialog box. (The final render file is nowhere to be seen in destination folder)
  • 4 times it has managed to "finish" the rendering process and I can ack that and close the rendering dialog box. Then I see the file in destination folder but it is only 0bytes and contains no video.
  • 6 times it has started rendering but at an arbitrary point it stops advancing to next frame and just continues to "render nothing" until I cancel the rendering.

This is so frustrating.

I have successfully managed to render two parts of the video to a file... the plan is to eventually manage to render the whole video in parts and then try to re-render those outputs into one whole videofile.

What have I tried so far?

  • Disabled Norton Antivirus (and turned off all unrelated programs that are running)
  • Tried newest and older drivers for the graphic card.
  • Tried to render to H264 with and without GPU
  • Tried to render to HEVC with and without GPU
  • Tried to move my project folder to a larger drive (the default folder was on C drive that has only like 13GB free)
  • Skipped the Magix Vegas LUT filter and used FilmConvert instead.
  • Upgraded Vegas to 307 version.

Please note that I cannot disable the often mentioned so4compundplug as I need it to be able to use the GH5 10bit source material.

My computer is:
- Intel 4770K
- Nvidia 1070 8GB GPU
- 16GB 1600MHz DDR3 RAM (2G used for dynamic preview). No other programs are running.
- Source video files on a 4TB disk. Destination Render folder on a seperate 3TB disk.
- Running Windows 10 64bit.
- While editing I had Vegas create proxy for all 4K videos.
 

This is unacceptable working conditions. I am really happy that I am only trying to create this video for myself but not trying to deliver to a customer. But given all the issues I am having I don't think I will be editing my next project in Vegas.

Has anyone else been experiencing similar issues with Vegas Pro 16? And if so.. has anyone found any solution or workaround?

I just refuse to accept that this can be a common problem because the program is borderline useless in this state.

 

Comments

NickHope wrote on 11/9/2018, 10:15 AM

Did you find this post in your research? Maybe something in it can help you: https://www.vegascreativesoftware.info/us/forum/faq-how-can-i-stop-vegas-pro-hanging-or-crashing-during-rendering--104786/

One thing that might be worth a shot is to use the blacklist to disable so4compoundplug for the Olympus footage but keep it for the Panasonic footage. The post is here: https://www.vegascreativesoftware.info/us/forum/blacklist-for-so4-includes-fix-for-gopro-dji-xiaomi-yi-avc-lag--111716/ It depends on you identifying something unique in the Olympus files' metadata that differentiates it from the Panasonic files' metadata. If you post MediaIndo report for each file I can try to help you with that.

Eagle Six wrote on 11/9/2018, 10:19 AM

I really have no suggestion as to what the problem is, however perhaps a work around will get the project done.

Can you render GH5 V-Log source media to an intermediate? That would be start a new project, bring in the GH5 source media with no changes and then render out to something like the Magix Intermediate format or Cineform (YUV 422 Filmscan 1) or DNxHR (12 bit), or Sony XAVC Intra, or uncompressed.

Then swap this intermediate file to your problem project and try a render.

System Specs......
Corsair Obsidian Series 450D ATX Mid Tower
Asus X99-A II LGA 2011-v3, Intel X99 SATA 6 Gb/s USB 3.1/3.0 ATX Intel Motherboard
Intel Core i7-6800K 15M Broadwell-E, 6 core 3.4 GHz LGA 2011-v3 (overclocked 20%)
64GB Corsair Vengeance LPX DDR4 3200
Corsair Hydro Series H110i GTX 280mm Extreme Performance Liquid CPU Cooler
MSI Radeon R9 390 DirectX 12 8GB Video Card
Corsair RMx Series RM750X 740W 80 Plus Gold power pack
Samsung 970 EVO NVMe M.2 boot drive
Corsair Neutron XT 2.5 480GB SATA III SSD - video work drive
Western Digitial 1TB 7200 RPM SATA - video work drive
Western Digital Black 6TB 7200 RPM SATA 6Bb/s 128MB Cache 3.5 data drive

Bluray Disc burner drive
2x 1080p monitors
Microsoft Window 10 Pro
DaVinci Resolve Studio 16 pb2
SVP13, MVP15, MVP16, SMSP13, MVMS15, MVMSP15, MVMSP16

bitman wrote on 11/9/2018, 2:23 PM

First thing I always before rendering: put dynamic preview to 0

(especially so since you have a NVIDEA)

Next disable VEGAS autosave

Next restart your PC

Next start rendering

APPS: VIDEO: VP 365 suite (VP 22 build 194) VP 21 build 315, VP 365 20, VP 19 post (latest build -651), (uninstalled VP 12,13,14,15,16 Suite,17, VP18 post), Vegasaur, a lot of NEWBLUE plugins, Mercalli 6.0, Respeedr, Vasco Da Gamma 17 HDpro XXL, Boris Continuum 2025, Davinci Resolve Studio 18, SOUND: RX 10 advanced Audio Editor, Sound Forge Pro 18, Spectral Layers Pro 10, Audacity, FOTO: Zoner studio X, DXO photolab (8), Luminar, Topaz...

  • OS: Windows 11 Pro 64, version 24H2 (since October 2024)
  • CPU: i9-13900K (upgraded my former CPU i9-12900K),
  • Air Cooler: Noctua NH-D15 G2 HBC (September 2024 upgrade from Noctua NH-D15s)
  • RAM: DDR5 Corsair 64GB (5600-40 Vengeance)
  • Graphics card: ASUS GeForce RTX 3090 TUF OC GAMING (24GB) 
  • Monitor: LG 38 inch ultra-wide (21x9) - Resolution: 3840x1600
  • C-drive: Corsair MP600 PRO XT NVMe SSD 4TB (PCIe Gen. 4)
  • Video drives: Samsung NVMe SSD 2TB (980 pro and 970 EVO plus) each 2TB
  • Mass Data storage & Backup: WD gold 6TB + WD Yellow 4TB
  • MOBO: Gigabyte Z690 AORUS MASTER
  • PSU: Corsair HX1500i, Case: Fractal Design Define 7 (PCGH edition)
  • Misc.: Logitech G915, Evoluent Vertical Mouse, shuttlePROv2

 

 

bitman wrote on 11/9/2018, 2:25 PM

see my post http://www.vegascreativesoftware.info/us/forum/dynamic-ram-preview-max-not-zero-render-issue-vp16-and-vp15-etc--113652/

 

 

APPS: VIDEO: VP 365 suite (VP 22 build 194) VP 21 build 315, VP 365 20, VP 19 post (latest build -651), (uninstalled VP 12,13,14,15,16 Suite,17, VP18 post), Vegasaur, a lot of NEWBLUE plugins, Mercalli 6.0, Respeedr, Vasco Da Gamma 17 HDpro XXL, Boris Continuum 2025, Davinci Resolve Studio 18, SOUND: RX 10 advanced Audio Editor, Sound Forge Pro 18, Spectral Layers Pro 10, Audacity, FOTO: Zoner studio X, DXO photolab (8), Luminar, Topaz...

  • OS: Windows 11 Pro 64, version 24H2 (since October 2024)
  • CPU: i9-13900K (upgraded my former CPU i9-12900K),
  • Air Cooler: Noctua NH-D15 G2 HBC (September 2024 upgrade from Noctua NH-D15s)
  • RAM: DDR5 Corsair 64GB (5600-40 Vengeance)
  • Graphics card: ASUS GeForce RTX 3090 TUF OC GAMING (24GB) 
  • Monitor: LG 38 inch ultra-wide (21x9) - Resolution: 3840x1600
  • C-drive: Corsair MP600 PRO XT NVMe SSD 4TB (PCIe Gen. 4)
  • Video drives: Samsung NVMe SSD 2TB (980 pro and 970 EVO plus) each 2TB
  • Mass Data storage & Backup: WD gold 6TB + WD Yellow 4TB
  • MOBO: Gigabyte Z690 AORUS MASTER
  • PSU: Corsair HX1500i, Case: Fractal Design Define 7 (PCGH edition)
  • Misc.: Logitech G915, Evoluent Vertical Mouse, shuttlePROv2

 

 

Zkuggi wrote on 11/10/2018, 3:50 AM

Thanks for quick and clever support Nick and Eagle Six. somehow I had missed those articles that you mentioned Nick.

And Bitman... You saved my sanity. Your solution worked :)

Setting the dynamic preview to 0 not only made the rendering smooth as sail. The whole experience of the system became better. No crashes, no strange halts and everything a bit more responsive.

There is obviously something wrong with how Vegas uses dynamic preview RAM allocation. At least in Windows 10 pro (fully up do date) using Nvidia cards.

j-v wrote on 11/10/2018, 4:51 AM

👍
In these cases it is also very important where you do store the paging file.
With me it is now on my fastest and less occupied disc (not Windows choice) and since then I never see more any delay during edit or rendering.

Last changed by j-v on 11/10/2018, 5:44 AM, 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)