Pro Vegas 16 hangs when rendering to MPEG-2

David-Eff wrote on 6/29/2019, 7:58 PM

I've had Pro Vegas, 10, 12,14 & just now 16 Suite Bundle. I just bought a new pc last week from Microcenter, a Powerspec G157. Specs are 8 GB memory, Intel Core i5-9400F Processor 2.9GHz, NVIDIA GTX 1650 4GB GDDR5, 250GB SSD, Windows 10 home. I added 8 GB memory, now it was 16 GB memory. Also added a 1 TB WD Blue internal hard drive.

I just bought the 16 Suite Bundle & installed it on this pc. Also installed QuickTime, all installed a week ago. Vegas is Build 424.

All editing is working fine. My projects are multicam, 2 cameras. No problem at all with 16 until I started rendering.

I am trying to render a 45 minute project. project has only camera MTS files and wav files. No graphics. Trying to render MPEG-2 , NTSC Widescreen, video only. Variable Bit Rate, 2 pass. All other settings are default.

All MTS, wav files are on an external hard drive. Vegas 16 is installed on the pc's C drive ( SSD ). I've rendered off the external drive for at least a couple years with Pro Vegas 14, with no problem.

I tried the trouble shooting from another post and checked the following :

Windows has the latest update
GPU acceleration is OFF

No Virus software besides Windows

DYANAMIC Ram Preview Max set to 0.

latest version of Quicktime installed

deleted all files in  temp folder
C:\Users\Dave\AppData\Local\VEGAS Pro\16.0\

I removed all unused media from project.

C:\Program Files\Common Files \ OFX renamed to OFXA for rendering.

Vegas does not crash, but after rendering 10 - 20 %, it makes no further progress for 5 minutes. It stays at 10 - 20 % rendered, with the elapsed time still ticking, so I cancel the rendering. I tried rendering with and without GPU acceleration. No success.

Does anyone have any suggestions how to render ?

Thanks, Dave

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

Comments

David-Eff wrote on 6/29/2019, 8:20 PM

Forgot to say, I am able to render a 3 minute video as .WMV with no problem. I did not try rendering to any other file type.

j-v wrote on 6/30/2019, 3:23 AM

Which rendertemplate did you exactly use? Screenshot please.
Is it this one?

I tried it with as source a GOPRO HEVC 4K 2,5 minute file, no problem and as result MediaInfo tells this about the rendered file

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)

 

Musicvid wrote on 6/30/2019, 5:25 AM

Is t your user permissions on the outboard drive?

Former user wrote on 6/30/2019, 2:37 PM

Probably unrelated, but I noticed that if I try to render the Red Car test using XDCAM EX HQ 1920x1080i 36mbps template (2nd. of the two recommended tests) that it hangs at the 51% mark.

This happens with VP 16 and 15, latest updates, tested on different PC's and laptops. I doesn’t happen with VP 13, maybe someone else could check this out in case its something thats crept into VP over a few versions?

The cluster of markers in the screenshot is where the issue is, any rendered section outside of that and the render is fine.  I tested a different source media instead of Red Car and it rendered fine using the XDCAM EX HQ template. 

j-v wrote on 6/30/2019, 3:29 PM

[OT] here no problem, renders in 2 min 26 sec, and with me that template has a default bitrate of 35 Mbps[/OT]
The OP has a total different rendergoal>>> MC mpeg-2

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)

 

Former user wrote on 6/30/2019, 4:19 PM

@j-v Thanks for checking that out, just thought i’d throw it out there in case it comes up in the future.

David-Eff wrote on 7/1/2019, 10:16 AM

I was gone all day yesterday. Tried rendering again this morning. I use all the default settings, except I check "two pass". I tried different Quality settings. It still takes 1:45 min to get to 1 % rendered.

j-v wrote on 7/1/2019, 11:57 AM

I was rendering a project of 1 minute to the same mpeg 2 template in 35 sec., but did it also hang again with you?
Your rendertime is very bad so I think something is wrong on your hardware setup.
The only thing that much differs from mine is that you use an i5 processor, while I always follow the rule that for AVC and HEVC decoding and encoding you need an i7.
This is how it goes with me

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)

 

David-Eff wrote on 7/2/2019, 1:12 AM

Still bad. I let it render for 2.5 hours today. It was 50 % done then it bombed. I rendered to MPEG2 all the time with Vegas 14 on my other pc, a Dell 3668 that is only 1 year old but has a weak power supply of 240w and couldn't be upgraded. I bought this new pc for the Vegas 16 bundle.

With my Dell 3668, I rendered frequently without fail with Pro Vegas 14. A project of 60 minute content would render to Mpeg2 could take up to 60 minutes, 90 minutes when I rendered a multicam project, but it would always finish rendering with no problem. This Vegas 16 problem put me behind. I couldn't deliver dvds this weekend.

bitman wrote on 7/6/2019, 6:30 AM

Probably unrelated, but I noticed that if I try to render the Red Car test using XDCAM EX HQ 1920x1080i 36mbps template (2nd. of the two recommended tests) that it hangs at the 51% mark.

This happens with VP 16 and 15, latest updates, tested on different PC's and laptops. I doesn’t happen with VP 13, maybe someone else could check this out in case its something thats crept into VP over a few versions?

The cluster of markers in the screenshot is where the issue is, any rendered section outside of that and the render is fine.  I tested a different source media instead of Red Car and it rendered fine using the XDCAM EX HQ template. 

@Former user

Confirmed, same here on my PC with the XDCAM template, hangs around 51 % mark in Vegas 15 and 53 % mark in Vegas 16

Last changed by bitman on 7/6/2019, 6:31 AM, changed a total of 1 times.

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

 

 

Former user wrote on 7/6/2019, 6:59 AM

Perfect timing @bitman, thanks. I just finished installing VP16 (purchased the 17+16 so spare ver 16's to play with) onto my old HP laptop, Amd gpu, to see if it made a difference. Sure enough, no problem here (3:14s LOL) for XDCAM. So its not because of VP version, maybe as @j-v's works its an Nvidia driver version issue? It took 4:28s using Mainconcept.

 

HP laptop specs ...

Intel i7 (Sandy Bridge) 2670QM, 2.2ghz, 8mb DDR3 memory.

Graphics .. Intel HD Graphics family. 

Intel HD Graphics 3000.  Supports Quick Sync.

AMD Radeon HD 7400M.

ATI Radeon HD 6490M

1 GB DDR5 dedicated up to 4.97 GB total

43,9 cm (17,3") HD+ High-Definition LED BrightView Display (1600 x 900)

Screen 1024 x 768 (Prolite E2607WS Monitor 1920 x 1200)

Blu-ray ROM with SuperMulti DVD±R/RW Double Layer

Integrated Gigabit Ethernet LAN

Bluetooth with WiDi, Intel 802.11 b/g/n

Beats Audio with HP Triple Bass Reflex Subwoofer