Rendering "Freeze" with Some Codecs

Lee_Thompson wrote on 8/13/2018, 4:50 PM

Vegas Pro v15 (Build 384)

OS: Windows 10 Enterprise 1803
RAM: 16GB
CPU: i7-7700
GPU: (Active) nVidia GTX 750 Ti (Driver is 398.36)
GPU: (Inactive) Intel HD Graphics 630
Misc: Wacom Pen is present as well as a mouse.
SSD/HDD

I use a Dell Inspiron 3668 as a workstation, including Vegas Pro. It has 2 GPUs, an Intel HD graphics and an nVidia. I recently disabled the Intel and am just using the nVidia (for more processing power with the Red Giant universe package).

I'm now having a strange issue, when rendering to some codecs (Magix AVC and MainConcept AVC), rendering will freeze at a random frame (if I just immediately re-launch and render the project using the same profile the frame # will be completely different). My main project does not have any processing filters, I do those as smaller projects that I pre-render (to HVEC) at a higher resolution and bitrate.

I've gone through the FAQ and tried with and without hardware acceleration and it makes no difference. My workaround is to just render everything with HVEC and just downmix it with another program

This all worked fine (oddly) when I was using the Intel GPU (the nVidia was completely disabled).

Examples:

MAGIX AVC/ACC stopped at frames 11122, 11657, 9423, 18599 (NVENC), and 8856.
MAINCONCEPT AVC/AAC usually doesn't get past 2%.

Project is 1280x720 (29.97 Drop), 8-bit Pixel Format, Best Render Quality, Gaussian Motion Blur (bypassed on all video tracks), De-interlace is set to none (since none of the material is interlaced), Resample is disabled. (Audio is 48k 16-bit stereo.)
Source media is 1920x1080 (29.97 Drop, Progressive) (AVC)
Sub-Projects are rendered at 1920x1080 (29.97 Drop, Progressive) (HVEC)

Render Profile:

(Profile name reflects the project which is under an NDA.)

Vegas GPU processing is on or the VFX filters I use in the sub-projects don't work.

I can't bring myself to try Sony's AVC because it's a horrible implementation...

In closing, I want to re-iterate, this profile worked perfectly every time with the Intel GPU active (nVidia disabled). I have a workaround (HVEC as an intermediate) but it seems odd that this is occurring now.

(EDIT: Added more information. Upgraded to Build 384, no change.)

UPDATE: I double checked the BIOS and i7's Intel GPU is as disabled as it can be, which means it's not completely gone. However, it is not enabled at all in Windows (no drivers loaded). I double checked Vegas's log and it sees the Intel but says it's not compatible and moves onto the nVidia.

INFO 2018-08-17 13:32:38 *** Start of GPU-accelerated video processing log ***
INFO 2018-08-17 13:32:38 VEGAS Pro 15.0
INFO 2018-08-17 13:32:38 Version 15.0 (Build 384)
INFO 2018-08-17 13:32:38 
INFO 2018-08-17 13:32:38 OpenGL_Initialize
INFO 2018-08-17 13:32:38 DC: 0000000000010E23
INFO 2018-08-17 13:32:39 GLC: 0000000000010000
INFO 2018-08-17 13:32:39 GL_VENDOR: NVIDIA Corporation
INFO 2018-08-17 13:32:39 GL_RENDERER: GeForce GTX 750 Ti/PCIe/SSE2
INFO 2018-08-17 13:32:39 GL_VERSION: 4.6.0 NVIDIA 398.36
INFO 2018-08-17 13:32:39 GLEW Init OK
INFO 2018-08-17 13:32:39 
INFO 2018-08-17 13:32:39 OpenCL_Initialize
INFO 2018-08-17 13:32:39 Platforms: 2
INFO 2018-08-17 13:32:39 Platform: 0
INFO 2018-08-17 13:32:39   Vendor:     Intel(R) Corporation
INFO 2018-08-17 13:32:39   Name:       Intel(R) OpenCL
INFO 2018-08-17 13:32:39   Version:    OpenCL 2.1 
INFO 2018-08-17 13:32:39   Profile:    FULL_PROFILE
INFO 2018-08-17 13:32:39   Extensions: cl_khr_icd cl_khr_global_int32_base_atomics cl_khr_global_int32_extended_atomics cl_khr_local_int32_base_atomics cl_khr_local_int32_extended_atomics cl_khr_byte_addressable_store cl_khr_depth_images cl_khr_3d_image_writes cl_intel_exec_by_local_thread cl_khr_spir cl_khr_dx9_media_sharing cl_intel_dx9_media_sharing cl_khr_d3d11_sharing cl_khr_gl_sharing cl_khr_fp64 cl_khr_image2d_from_buffer
INFO 2018-08-17 13:32:39 
INFO 2018-08-17 13:32:39   Devices: 1
INFO 2018-08-17 13:32:39   Device: 0
INFO 2018-08-17 13:32:39     Type:            CPU
INFO 2018-08-17 13:32:39     Vendor:          Intel(R) Corporation
INFO 2018-08-17 13:32:39     Name:            Intel(R) Core(TM) i7-7700 CPU @ 3.60GHz
INFO 2018-08-17 13:32:39     Profile:         FULL_PROFILE
INFO 2018-08-17 13:32:39     Version:         OpenCL 2.1 (Build 2)
INFO 2018-08-17 13:32:39     C version:       OpenCL C 2.0 
INFO 2018-08-17 13:32:39     Extensions:      cl_khr_icd cl_khr_global_int32_base_atomics cl_khr_global_int32_extended_atomics cl_khr_local_int32_base_atomics cl_khr_local_int32_extended_atomics cl_khr_byte_addressable_store cl_khr_depth_images cl_khr_3d_image_writes cl_intel_exec_by_local_thread cl_khr_spir cl_khr_dx9_media_sharing cl_intel_dx9_media_sharing cl_khr_d3d11_sharing cl_khr_gl_sharing cl_khr_fp64 cl_khr_image2d_from_buffer 
INFO 2018-08-17 13:32:39     Driver version:  7.5.0.2
INFO 2018-08-17 13:32:39     Available:       Yes
INFO 2018-08-17 13:32:39     Compiler:        Yes
INFO 2018-08-17 13:32:39     Image support:   Yes
INFO 2018-08-17 13:32:39     Unified memory:  Yes
INFO 2018-08-17 13:32:39     Vendor ID:       32902
INFO 2018-08-17 13:32:39     Compute units:   8
INFO 2018-08-17 13:32:39     Work dimensions: 3
INFO 2018-08-17 13:32:39     Clock Frequency: 3600
INFO 2018-08-17 13:32:39     Image reads:     480
INFO 2018-08-17 13:32:39     Image writes:    480
INFO 2018-08-17 13:32:39     Samplers:        480
INFO 2018-08-17 13:32:39     Workgroup size:  8192
INFO 2018-08-17 13:32:39     Image width:     16384
INFO 2018-08-17 13:32:39     Image height:    16384
INFO 2018-08-17 13:32:39     Parameter size:  3840
INFO 2018-08-17 13:32:39     Maximum alloc:   4270834688
INFO 2018-08-17 13:32:39     Memory size:     17083338752
INFO 2018-08-17 13:32:39     Local memory:    32768
INFO 2018-08-17 13:32:39     Work item sizes: 8192, 8192, 8192
INFO 2018-08-17 13:32:39     Out of order Q:  Yes
INFO 2018-08-17 13:32:39     Profiling Q:     Yes
WARN 2018-08-17 13:32:39 Device type not supported
WARN 2018-08-17 13:32:39 Device is not compatible.
INFO 2018-08-17 13:32:39 
INFO 2018-08-17 13:32:39 Platform: 1
INFO 2018-08-17 13:32:39   Vendor:     NVIDIA Corporation
INFO 2018-08-17 13:32:39   Name:       NVIDIA CUDA
INFO 2018-08-17 13:32:39   Version:    OpenCL 1.2 CUDA 9.2.156
INFO 2018-08-17 13:32:39   Profile:    FULL_PROFILE
INFO 2018-08-17 13:32:39   Extensions: cl_khr_global_int32_base_atomics cl_khr_global_int32_extended_atomics cl_khr_local_int32_base_atomics cl_khr_local_int32_extended_atomics cl_khr_fp64 cl_khr_byte_addressable_store cl_khr_icd cl_khr_gl_sharing cl_nv_compiler_options cl_nv_device_attribute_query cl_nv_pragma_unroll cl_nv_d3d10_sharing cl_khr_d3d10_sharing cl_nv_d3d11_sharing cl_nv_copy_opts cl_nv_create_buffer
INFO 2018-08-17 13:32:39 
INFO 2018-08-17 13:32:39   Devices: 1
INFO 2018-08-17 13:32:39   Device: 0
INFO 2018-08-17 13:32:39     Type:            GPU
INFO 2018-08-17 13:32:39     Vendor:          NVIDIA Corporation
INFO 2018-08-17 13:32:39     Name:            GeForce GTX 750 Ti
INFO 2018-08-17 13:32:39     Profile:         FULL_PROFILE
INFO 2018-08-17 13:32:39     Version:         OpenCL 1.2 CUDA
INFO 2018-08-17 13:32:39     C version:       OpenCL C 1.2 
INFO 2018-08-17 13:32:39     Extensions:      cl_khr_global_int32_base_atomics cl_khr_global_int32_extended_atomics cl_khr_local_int32_base_atomics cl_khr_local_int32_extended_atomics cl_khr_fp64 cl_khr_byte_addressable_store cl_khr_icd cl_khr_gl_sharing cl_nv_compiler_options cl_nv_device_attribute_query cl_nv_pragma_unroll cl_nv_d3d10_sharing cl_khr_d3d10_sharing cl_nv_d3d11_sharing cl_nv_copy_opts cl_nv_create_buffer
INFO 2018-08-17 13:32:39     Driver version:  398.36
INFO 2018-08-17 13:32:39     Available:       Yes
INFO 2018-08-17 13:32:39     Compiler:        Yes
INFO 2018-08-17 13:32:39     Image support:   Yes
INFO 2018-08-17 13:32:39     Unified memory:  No
INFO 2018-08-17 13:32:39     Vendor ID:       4318
INFO 2018-08-17 13:32:39     Compute units:   5
INFO 2018-08-17 13:32:39     Work dimensions: 3
INFO 2018-08-17 13:32:39     Clock Frequency: 1084
INFO 2018-08-17 13:32:39     Image reads:     256
INFO 2018-08-17 13:32:39     Image writes:    16
INFO 2018-08-17 13:32:39     Samplers:        32
INFO 2018-08-17 13:32:39     Workgroup size:  1024
INFO 2018-08-17 13:32:39     Image width:     16384
INFO 2018-08-17 13:32:39     Image height:    16384
INFO 2018-08-17 13:32:39     Parameter size:  4352
INFO 2018-08-17 13:32:39     Maximum alloc:   536870912
INFO 2018-08-17 13:32:39     Memory size:     2147483648
INFO 2018-08-17 13:32:39     Local memory:    49152
INFO 2018-08-17 13:32:39     Work item sizes: 1024, 1024, 64
INFO 2018-08-17 13:32:39     Out of order Q:  Yes
INFO 2018-08-17 13:32:39     Profiling Q:     Yes
INFO 2018-08-17 13:32:39     NV compute (maj):5
INFO 2018-08-17 13:32:39     NV compute (min):0
INFO 2018-08-17 13:32:39     NV warp size:    32
INFO 2018-08-17 13:32:39     NV overlap:      Yes
INFO 2018-08-17 13:32:39     NV integ. mem:   No
INFO 2018-08-17 13:32:39 Device is compatible.

(I'll spare everyone the actual OpenCL compilation messages.)

Comments

Kinvermark wrote on 8/13/2018, 5:20 PM

I like to render to a lossless intermediate (MagicYUV) then encode to h264 in Handbrake. This avoids the generational loss (and extensive render time) you get from the HEVC render. It is also reliable.

As for troubleshooting the GPU issues, that's tough (and not uncommon). If you have gone through the "troubleshooting render crashes" page, I haven't got anything to add, but others might, so please post all your details the per the FAQ instructions on the first page.

Lee_Thompson wrote on 8/13/2018, 5:40 PM

I like to render to a lossless intermediate (MagicYUV) then encode to h264 in Handbrake. This avoids the generational loss (and extensive render time) you get from the HEVC render. It is also reliable.

As for troubleshooting the GPU issues, that's tough (and not uncommon). If you have gone through the "troubleshooting render crashes" page, I haven't got anything to add, but others might, so please post all your details the per the FAQ instructions on the first page.

I've updated the original post with more detail as per the various FAQs.

I probably can't do the MagicYUV, as this project is rather large (22 x 44 min) (no, it's not all one .veg file).

Lee_Thompson wrote on 8/17/2018, 12:03 AM

Nothing? Really?

fr0sty wrote on 8/17/2018, 12:18 AM

Common causes of this issue can be:

1. Format compatibility issues.. most of these have been ironed out, but it would help to know the exact format of your source footage... its resolution, bitrate, bit depth, codec used, or camera used to record it.

2. GPU driver issues... I've fixed this same problem with a simple GPU driver update.

3. Sometimes you have to disable the internal GPU in the bios, if you have not already.

If that doesn't work, try opening preferences menu while holding shift, going to the "internal" tab, searching for "so4", changing both on second line to FALSE.

If that doesn't help, set it back to TRUE, then file a support ticket with Magix.

Lee_Thompson wrote on 8/17/2018, 11:58 AM

@fr0sty

Tried changing Enable Hardware Decoding for SO4 to false but same result, this time it randomly stopped at frame 9031 (doing another attempt now but I'm sure it'll freeze somewhere again).

Source footage is also AVC/AAC (1920x1080 CABAC 14.2 Mb/s 30fps).

I don't think it's a source issue since other codecs (HVEC etc) work fine and the AVC encoders worked when it was on the Intel GPU. (I would think the nVidia would be more compatible with Vegas.)

nVidia driver is as up to date as it's possible to be, I'm not going to put a beta driver on a production machine.

The Intel GPU is completely disabled (BIOS etc).

(I can live with my HVEC intermediate workaround but it really bugs me that what was working now isn't.)

fr0sty wrote on 8/17/2018, 12:26 PM

I've had format issues cause this same problem, which is why I asked. I would recommend using a format other than HEVC until you get this worked out. File a support ticket with Magix and see if they can help,. they're usually good about it. In the mean time, Render out ProRes (AKA MAgix Intermediate Codec) or XAVC-I, I'm sure there's formats others here can recommend as well... they will render faster, and they are higher quality so you won't lose as much quality in the generation loss.

Does it do the same when you have the encoder set to NVENC as it does when you set it to Mainconcept (CPU only)?

Julius_ wrote on 8/17/2018, 1:35 PM

Have the dynamic ram set to 0 and turn off GPU..I get this problem of freezing when rendering,,,,unless I do that.

Musicvid wrote on 8/17/2018, 3:34 PM

I'm sure I'm missing something here; have you tried this?

https://www.vegascreativesoftware.info/us/forum/avc-xavc-s-issues-in-vp15-try-disabling-so4compoundplug-dll--108345/

Lee_Thompson wrote on 8/17/2018, 9:40 PM

I'm sure I'm missing something here; have you tried this?

https://www.vegascreativesoftware.info/us/forum/avc-xavc-s-issues-in-vp15-try-disabling-so4compoundplug-dll--108345/

I haven't tried that since it's a decoder (since my source is avc) not an encoder but worth a shot (although since HVEC etc work fine, I don't think it's a source decoding issue). I'm doing an HVEC render right now so I won't be able to try it for a bit.

Lee_Thompson wrote on 8/17/2018, 9:42 PM

I've had format issues cause this same problem, which is why I asked. I would recommend using a format other than HEVC until you get this worked out. File a support ticket with Magix and see if they can help,. they're usually good about it. In the mean time, Render out ProRes (AKA MAgix Intermediate Codec) or XAVC-I, I'm sure there's formats others here can recommend as well... they will render faster, and they are higher quality so you won't lose as much quality in the generation loss.

Does it do the same when you have the encoder set to NVENC as it does when you set it to Mainconcept (CPU only)?

HVEC rendering works fine, AVC doesn't.

Yeah NVEncoder actually freezes usually sooner oddly enough. I've tried with hardware acceleration on and off and there's no difference. Other than it will freeze at some random frame usually between 10% and 30%.

The weird thing is, no changes were made to the Vegas install, just disabled the Intel GPU and enabled the nVidia.

Lee_Thompson wrote on 8/17/2018, 9:48 PM

Have the dynamic ram set to 0 and turn off GPU..I get this problem of freezing when rendering,,,,unless I do that.

That GPU setting, as far as I understand it, is for the editor, not the renderer. While I could turn that off for the main project, my VFX sub-projects that isn't an option since they require a GPU.

I could give the dynamic ram setting a try.

Musicvid wrote on 8/17/2018, 9:50 PM

I'm sure I'm missing something here; have you tried this?

https://www.vegascreativesoftware.info/us/forum/avc-xavc-s-issues-in-vp15-try-disabling-so4compoundplug-dll--108345/

I haven't tried that since it's a decoder not an encoder but worth a shot. I'm doing an HVEC render right now so I won't be able to try it for a bit.

You see, a CODEC is a COmpresser-DECompresser.

Hope it solves your problem, but if not, thanks for giving it at least a fair chance.

Lee_Thompson wrote on 8/25/2018, 1:10 AM

I'm sure I'm missing something here; have you tried this?

https://www.vegascreativesoftware.info/us/forum/avc-xavc-s-issues-in-vp15-try-disabling-so4compoundplug-dll--108345/

I haven't tried that since it's a decoder not an encoder but worth a shot. I'm doing an HVEC render right now so I won't be able to try it for a bit.

You see, a CODEC is a COmpresser-DECompresser.

This is true, now that crunch time is over I'll give it a whirl.

UPDATE: It's not done yet but I haven't seen frame numbers this high in awhile for AVC/MP4 (48000).

UPDATE 2: It has now finished two renders, thanks all. (Not secure exactly what the combination was. I suspect it was the so4compound dll.