Old bug.. just re-reporting... render freezes when GPU is enabled

RedRob-CandlelightProdctns wrote on 6/30/2017, 12:16 PM

New computer with Radeon R470, 32 GB RAM, 4.2 GHz quad processor... Vegas 14 Build 252

Whenever I render regardless of target format, if GPU is enabled it fairly reliably will stop part-way through if the length is sizable (e.g. over 45 minutes).. sometimes sooner.. sometimes later.

The behavior is the render-clock keeps counting, but the frames stop ticking in the preview (and CPU essentially drops to 0%)... I have to kill in task manager and start over.

I realize this is an old bug previously reported, and disabling the GPU before rendering resolves... but it's still a bug nonetheless, ya?

Comments

OldSmoke wrote on 6/30/2017, 12:57 PM

I don't see that behavior on my system and I have GPU acceleration always enabled.

What is your project like? Do you use any 3rd party plugins? What driver is installed for your RX470? Is your power supply sufficient?

RedRob-CandlelightProdctns wrote on 6/30/2017, 2:06 PM

Power supply is not an issue. 700W is ample for this setup.

Has happened on a number of projects.. source media is mixed cameras, most .MP4/AVCHD 1080i60 and 1080p30. Rendering shows which are 1-3 hours long. The only effects used are BRIGHTNESS/CONTRAST on this show, and two clips with Neat Video (latest version).. other projects also had primary/secondary color correction, saturation, and Mercalli stabilization. Sometimes I will create regions and use Excaliber's "assets" tool to render the different regions (so if it stops/crashes, at least *some* the project render might not have to start over).

So last night rendering stopped around 40% with that problem on this project. Task-killed vegas (did not reboot), started vegas and disabled GPU in Video preferences, exited and restarted Vegas, loaded project and am rendering now.. 61% complete on an appx. 3-hour render.

Video driver info:
Radeon Settings Version - 2017.0606.1509.25443
Driver Packaging Version - 17.10.3211-170606a-314971E-CrimsonReLive
Provider - Advanced Micro Devices, Inc.
2D Driver Version - 8.1.1.1599
Direct3D® Version - 9.14.10.01261
OpenGL® Version - 6.14.10.13476
OpenCL™ Version - 22.19.171.1
AMD Mantle Version - 9.1.10.0189
AMD Mantle API Version - 102400
AMD Audio Driver Version - 10.0.1.1
Vulkan™ Driver Version - 1.5.0
Vulkan™ API Version - 1.0.39

Radios Software Version 17.6.1, graphics chipset Radeon RX470, , graphics profile set to "balanced"

Shinra Bansho wrote on 6/30/2017, 5:42 PM

I used to frequently suffer similar render errors with which I was VERY frustrated. My solution was simply to import (i.e. nest) the project file, then render. I am guessing (can be totally wrong) that somehow pre-renders at the time of import allow VEGAS manage data more efficiently. My rig has changed since then but I still use this method when I render (I use RX470 as well.) Zero render error with GPU enabled. (Occasionally, tho', I do have hangs and crashes other times but not render time.)

set wrote on 6/30/2017, 5:53 PM

How about set DRAM to 0 ? Can this help ?

(RX470 user here as well)

RedRob-CandlelightProdctns wrote on 6/30/2017, 9:55 PM

Disabling the GPU seems to resolve the problem. I haven't tried setting DRAM to 0, but read the reports recently here that doing so significantly slowed rendering time.

It appears there are some VERY technical folks here on the forum. I personally come from a software/tech background and enjoyed digging into low level operations and optimization. I would *LOVE* to hear from the developers exactly how/what the DRAM Preview setting does, and how it uses memory/disc differently when on, or off, such that fluctuations appear to unveil memory and render-related problems.

OldSmoke wrote on 7/3/2017, 9:06 AM

Disabling the GPU seems to resolve the problem. I haven't tried setting DRAM to 0, but read the reports recently here that doing so significantly slowed rendering time.

It appears there are some VERY technical folks here on the forum. I personally come from a software/tech background and enjoyed digging into low level operations and optimization. I would *LOVE* to hear from the developers exactly how/what the DRAM Preview setting does, and how it uses memory/disc differently when on, or off, such that fluctuations appear to unveil memory and render-related problems.

I doubt anybody inside Magix even knows?

shanedk wrote on 12/5/2017, 3:31 PM

I was having this problem under VP14, and still am under VP15. Only when GPU is selected, and not all of the time.

NickHope wrote on 12/6/2017, 1:36 AM

@shanedk This post (& the post linked in section #1 of it) contain most known troubleshooting steps for this issue. Something in there might help you, even if it's a roll-back of your GPU driver.