Vegas Pro 17 build 421 stops rendering 4K video

Helge-Volden wrote on 4/6/2020, 1:18 AM

I am using DJI Osmo pocket videos to make a movie. The footage is 4K 50p

I want to render the finished video back to 4K 50p,

Render settings: MAGIX AVC/AAC MP4, Internet UHD 2160p 50 fps (NVIDIA NVENC)

but when the rendering comes to the first dissolve transision, the rendering stops.

No action is possible, it just stops, CPU load and GPU load goes to zero, I have to kill the application.

What can be the problem ?

I have done exactly the same in Vegas Movie studio 16, and there it works great.

My equipment:

Windows 19 Pro, Version 1909, OS build 18363.720

Vegas Pro 17 build 421

Main card: Gigabyte Z390 Aorus Pro

CPU: OctalCore Intel Core i9-9900K, 4800 MHz (48 x 100)

Video card: GeForce RTX 2080 Ti

Memory: 64 Gb, 4x Corsair Vengeance LPX CMK64GX4M4A2666C16

Has anybody had the same problem?

 

 

Comments

j-v wrote on 4/6/2020, 2:56 AM

Never.
Maybe your settings in Vegas caused this.
For possible help we need to know some things.

1. What is the render-to location and the empty space there.
2. Screenshot of Options/Preferences/Video
3. Screenshot of Options/Preferences/File I/O
4. Screenshot of your Projectsettings
5. Exact driverversion (number) of the Nvidia GPU
6. That used first transition is????

Last changed by j-v on 4/6/2020, 3:10 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, W10 home version 2004 build 19041.264, i7 9700 4.7Ghz,16 DDR4 GB RAM, Gef. GTX 1660 Ti.
Laptop  :Asus ROG GL753VD, W10 home version 2004 build 19041.264, CPU i7 7700HQ, 8 GB RAM, GeF. GTX 1050 (2 GB) + Int. HD Graphics 630(2GB).VP 16,17 and VMS PL 16,17 are installed, all latest builds
Both Nvidia GPU's have driver version 451.48 Studio Driver, desktop the Studio DHC driver
TV      :LG 4K 55EG960V

My slogan is: BE OR BECOME A STEMCELL DONOR !!!

Reyfox wrote on 4/13/2020, 10:39 AM

I haven't experienced any issues with editing and rendering 4K video, but my computer build is different than yours.

Look in my sig to see computer build.

 

3POINT wrote on 4/13/2020, 11:01 AM

I am using DJI Osmo pocket videos to make a movie. The footage is 4K 50p

I want to render the finished video back to 4K 50p,

Render settings: MAGIX AVC/AAC MP4, Internet UHD 2160p 50 fps (NVIDIA NVENC)

but when the rendering comes to the first dissolve transision, the rendering stops.

 

In VMS16 GPU acceleration of video processing is switched off by default. You could try to switch it off also in Vpro17 and see if it makes a difference.

Another option is to use the MAGIX AVC/AAC Mp4 Internet UHD 2160p50 render template instead of the NVIDIA NVENC. Or installing Voukoder, renders everything without issues.

I use the same footage as you DJI Osmo Pocket 2160p50, having the same problems with rendering MAGIX AVC NVENC with my GTX videocard, but none with Voukoder.

Musicvid wrote on 4/13/2020, 11:08 AM

Does it do the same if you render to a software codec, such as XAVC?

Helge-Volden wrote on 4/13/2020, 1:20 PM

The problem is when I set the render settings to MAGIX AVC/AAC MP4, Internet UHD 2160p 50 fps (NVIDIA NVENC), not any other render settings.

I want to use that setting to utilize the speed of my Nvidia GeForce RTX 2080 Ti card.

That rendering goes very fast, and it works in Vegas Movie studio 16, so why not in Vegas Pro 17 ???

The problem is that I can't import my project from Vegas Pro to Vegas Movie studio 16 and render it there, I have to start over again.

 

j-v wrote on 4/13/2020, 1:54 PM

If you have the same effects and mediagenerators used in Vpro 17 also in VMS 16 to can start both and copy all of your timeline to your timeline in VMS 16

Last changed by j-v on 4/13/2020, 1:58 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, W10 home version 2004 build 19041.264, i7 9700 4.7Ghz,16 DDR4 GB RAM, Gef. GTX 1660 Ti.
Laptop  :Asus ROG GL753VD, W10 home version 2004 build 19041.264, CPU i7 7700HQ, 8 GB RAM, GeF. GTX 1050 (2 GB) + Int. HD Graphics 630(2GB).VP 16,17 and VMS PL 16,17 are installed, all latest builds
Both Nvidia GPU's have driver version 451.48 Studio Driver, desktop the Studio DHC driver
TV      :LG 4K 55EG960V

My slogan is: BE OR BECOME A STEMCELL DONOR !!!

3POINT wrote on 4/13/2020, 2:08 PM

I'm always wondering that the speed of the rendering process seems to be the most important. When I see how many hours spending on editing a project, I don't care about the few minutes more or less the final rendering takes. For me it's important that I have a smooth preview while editing and a final output in good quality and small file size without struggling with rendertemplates, latest GPU drivers etc. For this purpose Voukoder is perfect.

I think that some editors spill far more time (and money) in tweaking Vegas to get the fastest renderspeeds, than the time they ever will save with those fast renderings.

Glenn-C wrote on 7/5/2020, 4:22 AM

The problem is when I set the render settings to MAGIX AVC/AAC MP4, Internet UHD 2160p 50 fps (NVIDIA NVENC), not any other render settings.

I want to use that setting to utilize the speed of my Nvidia GeForce RTX 2080 Ti card.

That rendering goes very fast, and it works in Vegas Movie studio 16, so why not in Vegas Pro 17 ???

The problem is that I can't import my project from Vegas Pro to Vegas Movie studio 16 and render it there, I have to start over again.

Yes I'm having these exact issues with my Nvidia GTX 1660 ti GPU. I have an 8min timeline, where rendering stops at a specific shot, everything goes to 0 as the Render Timer freezes. If I render from that shot onward to the end, that renders out fine. But I can't render out the entire timeline.

As to someone above discussing how we're chasing fast render times with GPU -- yeah, that's why we purchased a computer with a good GPU card, because we have businesses where time is money. Rendering something that normally takes 2-3 hours, instead of the non-GPU speed of 12 hours = money/time/initial investment in laptop.

Has MAGIX and NVIDIA commented yet? I'm really getting tired of these Nvidia issues popping up constantly. Seriously, this is not professional level software with professional tech support.

  • Windows 10 latest build
  • 24GB RAM
  • Laptop: Lenovo Y545
  • NVIDIA latest Studio drivers
  • GPU turned off at Render
  • Dynamic Ram Preview set to 0
  • Render threads set to 12 (for my i7 9750 six-core)
JN- wrote on 7/5/2020, 4:49 AM

@Helge-Volden @Glenn-C Yes, Nvenc is brilliant when it works. Very good quality and exceedingly fast, whats not to like. The only suggestion I can think of is to try varying the RC mode, and Preset settings.

I use item 7, mostly no issues, though with vp17 I need to have Dynamic Ram preview set to zero if its UHD.

VP16 is more stable. Maybe there’ll be a final vp17 update before VP18 release.

I did this a while back with just some of the different combinations, hopefully it might improve things.

Beware that although item 11 is best quality above, it has massive seek times, probably only suitable for streaming.

Note that there is a later version than what you are using, b421, i.e. b452.

Last changed by JN- on 7/5/2020, 5:00 AM, changed a total of 6 times.

---------------------------------------------

Benchmarking thread

Codec Render Quality tables

---------------------------------------------

PC ... Corsair case, own build ...

CPU .. i9 9900K, iGpu UHD 630

Memory .. 32GB DDR4

Graphics card .. MSI RTX 2080 ti

Graphics driver .. latest studio

PSU .. Corsair 850i

Mboard .. Asus Z390 Code

 

Laptop ... (Acer Predator G9-793-77AC)

CPU .. i7-6700HQ Skylake-H

Memory ..32 GB DDR4, was previously 16 GB

Graphics card .. Nvidia GTX 1070

Graphics driver .. latest studio

Glenn-C wrote on 7/7/2020, 10:26 AM

I have the current 452 version of VP17.

 

As far as the chart, I didn't understand it. I'd need a legend or explanation.

JN- wrote on 7/7/2020, 1:52 PM

Yes, @Glenn-C, @Helge-Volden posted he was using an earlier version.

Re: a legend, the items displayed in the table are simply some of the different combinations that are available with the Magix Nvenc encoder render template. If you’re not using Nvenc then I understand you may not be familiar with them.

I mention this because I have previously had issues rendering with Nvenc, zero byte files etc. The table highlights the ones to avoid having this happen, in my case anyway.

---------------------------------------------

Benchmarking thread

Codec Render Quality tables

---------------------------------------------

PC ... Corsair case, own build ...

CPU .. i9 9900K, iGpu UHD 630

Memory .. 32GB DDR4

Graphics card .. MSI RTX 2080 ti

Graphics driver .. latest studio

PSU .. Corsair 850i

Mboard .. Asus Z390 Code

 

Laptop ... (Acer Predator G9-793-77AC)

CPU .. i7-6700HQ Skylake-H

Memory ..32 GB DDR4, was previously 16 GB

Graphics card .. Nvidia GTX 1070

Graphics driver .. latest studio

Glenn-C wrote on 7/7/2020, 4:24 PM

Ok thank you. I am trying to use Nvenc with little success.