Vegas 16 Freezing and malfunctioning while rendering with GPU

j-v wrote on 11/5/2018, 4:15 PM

To what codec and template do try to render with GPU, what projecttype do you use and what is the MediaINfo of your sourcefiles. Did you use special FX's?
For info how to produce the info I asked for look here under C

fr0sty wrote on 11/5/2018, 8:08 PM

I was having this issue. Updating my GTX 970 drivers earlier yesterday fixed it.

Former user wrote on 11/5/2018, 8:16 PM

Hello,

I have just upgraded to Vegas 16 and the only reason I did that was because there were promisses of working and fuctional GPU accelerated rendering. Anytime i try to render with Nvidia NVENC method - the render process ends up freezing and if not - the output will have errors like white or black flashes and frames. I am very disappointed by this because I would have stayed on Vegas 14 if it wasn't for GPU rendering. I have Intel Core i7 4790, 32GB ram and GeForce GTX 980Ti, also my project space is on SSD drive .... is there ANY possible solution to this? While rendering on CPU the render time is more than two times longer than on GPU

vp16 is the most buggy release in vegas history & update2 succeeded in making more people's software unstable to the point of being unusable which is a novel approach.

Under the Magix AVC encoding option do you see Intel QSV option?

If so, you could try encoding with that. Vegas would then use your Nvidia card for graphics processing & your intel chip for hardware rendering. I dont' know what the quality or speed is like with Intel quicksync hardware encoding on your older cpu. Maybe it would be good enough for now, while they fix their gpu problems

fr0sty wrote on 11/5/2018, 8:53 PM

Or you could just update your GPU driver...9 times out of 10 when I have NVENC render issues in Vegas, it is a driver issue.

PEchiOnlajn wrote on 11/6/2018, 12:35 AM

Hey guys,

all my drivers are up to date and my source files are .mp4 and .mov FHD 50p straight from DJI Osmo and Panasonic AG AC30. The project template is Internet HD 1080p 29.97 fps which are the output I am going for. The freeze happens at various points. No video plugins are on this, only audio plugins from iZotope (Nectar 2 - on voiceover) but when I turn it off it doesn't solve the problem. Intel QSV option is not present under encoding methods. Here are properties of both type video files.

General
Name: DJI_0021.MP4
Folder: D:\Uklid Pohoda\DJI Osmo
Type: AVC
Size: 140,44 MB (143 809 957 bytes)
Created: pátek 2. listopadu 2018, 13:46:51
Modified: pátek 2. listopadu 2018, 12:24:18
Accessed: úterý 6. listopadu 2018, 7:30:07
Attributes: Archive

Streams
Video: 00:00:28,700, 50,000 fps progressive, 1920x1080x12, AVC
Audio: 00:00:28,672, 48 000 Hz; Mono, AAC

ACID information
ACID chunk: no
Stretch chunk: no
Stretch list: no
Stretch info2: no
Beat markers: no
Detected beats: no

Other metadata
Regions/markers: no
Command markers: no

Media manager
Media tags: no

Plug-In
Name: compoundplug.dll
Folder: C:\Program Files\VEGAS\VEGAS Pro 16.0\FileIO Plug-Ins\compoundplug
Format: AVC
Version: Version 16.0 (Build 307)

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

General
Name: A2020011.MOV
Folder: D:\Uklid Pohoda\Panasonic AG AC30
Type: AVC
Size: 60,64 MB (62 094 402 bytes)
Created: pátek 2. listopadu 2018, 13:51:48
Modified: pátek 2. listopadu 2018, 11:54:00
Accessed: úterý 6. listopadu 2018, 7:30:07
Attributes: Archive

Streams
Video: 00:00:10,080, 50,000 fps progressive, 1920x1080x32, AVC
Audio: 00:00:10,080, 48 000 Hz; Stereo, PCM

Summary
[TCFM]: 9

ACID information
ACID chunk: no
Stretch chunk: no
Stretch list: no
Stretch info2: no
Beat markers: no
Detected beats: no

Other metadata
Regions/markers: no
Command markers: no

Media manager
Media tags: no

Plug-In
Name: so4compoundplug.dll
Folder: C:\Program Files\VEGAS\VEGAS Pro 16.0\FileIO Plug-Ins\so4compoundplug
Format: AVC
Version: Version 1.0 (Build 8532)
Company: MAGIX Computer Products Intl. Co.

j-v wrote on 11/6/2018, 1:51 AM

Thanks for the info.
Which driverversion actually are installed for the Geforce and you did not answered my question about the rendertemplate you use.

PEchiOnlajn wrote on 11/6/2018, 4:21 AM

Thanks for the info.
Which driverversion actually are installed for the Geforce and you did not answered my question about the rendertemplate you use.

Official NVIDIA drivers 416.34 and im using or at least trying to use "Internet HD 1080p 29.97 fps (NVIDIA NVENC)" render template - without any edits. If i use the non NVIDIA ENC template it will render successfully but at twice the time....

j-v wrote on 11/6/2018, 5:00 AM

Driver is indeed the latest, but you did not tell which codec you are using and as you can see there are more than one template with that name

I'm using both without any problem with the same drivers as you on my laptop from signature, but I know that sometimes with some users the Magix HEVC can give some troubles during rendering.

PEchiOnlajn wrote on 11/6/2018, 5:15 AM

Driver is indeed the latest, but you did not tell which codec you are using and as you can see there are more than one template with that name

I'm using both without any problem with the same drivers as you on my laptop from signature, but I know that sometimes with some users the Magix HEVC can give some troubles during rendering.

AVC always freezes, HEVC has errors (skipping frames, random white or black frames)

Former user wrote on 11/6/2018, 5:47 AM

I dont' think you've said, Have you tried disabling so4compoundplug.dll?

It is clear you don't have GPU processing issues as you can use GPU video processing when using software encode, but maybe NVDEC hardware decoding to NVENC hardware encoding is causing the problem with your setup. Just search for so4compoundplug.dll in this forum to find out how to disable it if you don't know.

jyoungl6 wrote on 11/6/2018, 8:25 AM

Over the weekend I purchased and installed a GTX 2070 on my system, replacing a GTX 1050Ti. I updated drivers and immediately started having similar problems where rendering would stop halfway in the process, hanging Vegas. All I could do was kill Vegas with task manager. I disabled so4compoundplug.dll and now everything is working well so far.

Why does Magix even distribute so4compoundplug.dll? It seems to cause nothing but problems.

Vegas 16 Suite, GTX 2070, Windows 10 Pro

Kinvermark wrote on 11/6/2018, 10:39 AM

It is the new decoder, and I am sure it has many advantages, including (I guess) QSV, NVENC, VCE, and 10 bit camera formats. They made an internal preference and blacklist to handle wayward (I.e. incompatible / non-standard) footage, so that seems a good compromise to me. Eventually all the kinks will get ironed out an we will have the benefit of a better hardware accelerated platform going forward.

PS Hope you didn't follow the advice to rename the dll; just handle via internal preferences or blacklist.

PEchiOnlajn wrote on 11/6/2018, 11:02 AM

Strangely enough - no luck, when disabling it in internal settings ... same behaviour but im struggling to find the blacklist way to do it. Everywhere i look they only show the internal settings way.

PEchiOnlajn wrote on 11/6/2018, 11:50 AM

I even just got more trouble - while using an MP4 and MOV source files i can get to final render but i just got a M2T source files from a friends camera and no matter what output settings or what settings whatsoever it always freezes .... i really feel like i want a refund for this one - i had no such trouble in vegas 14

PEchiOnlajn wrote on 11/6/2018, 11:53 AM

IT ONLY works well when i uncheck "allow legacy gpu rendering" in preferences and disable graphic acceleration in video tab ..... i really .. really feel like i been ripped off ....

Former user wrote on 11/6/2018, 3:32 PM

On the assumption you can't get a refund, and that you can't use your gpu, you should look into using Intel quicksync as video processor and encoder. You need the drivers & needs to be turned on in bios. I"m not familiar with the IGPU of these older intels, except to know they were improved quite a bit with 500 & 600 series. I have intel 520 graphics & it's a big improvement over no gpu when using VP15.

I have no used VP16, it looks to be an abomination.

ngjb wrote on 11/6/2018, 5:00 PM

If you want a refund you have to request it within 14 days by email or through the Magix site. I gave up with Vegas pro 16 after a few hours and uninstalled it. It kept crashing after I hit the render button. I put a single 17 second HDV clip on the timeline that worked all the way back to Sony Vegas 6 as the sole media in the test project and tried to render it and it still crashed. I was expecting an improvement over Vegas 14, which am using, but Vegas 16 was running much slower and is horribly unstable. I equested a refund and was informed that I should see a credit in a few days. I disputed the charges and sent the email from Magix as proof just in case the credit doesn't come through. I checked my Magix account and they removed Vegas 16 and left 14 alone. I imagine things will stabilize by Vegas 19-20. Until then, I'm sticking with Vegas 14.

PEchiOnlajn wrote on 11/8/2018, 2:34 AM

Do you guys think i should get that refund ? Or is there a possibility that they will release a upgraded V16 that will work ?

fr0sty wrote on 11/8/2018, 6:53 AM

If you want a refund you have to request it within 14 days by email or through the Magix site. I gave up with Vegas pro 16 after a few hours and uninstalled it. It kept crashing after I hit the render button. I put a single 17 second HDV clip on the timeline that worked all the way back to Sony Vegas 6 as the sole media in the test project and tried to render it and it still crashed. I was expecting an improvement over Vegas 14, which am using, but Vegas 16 was running much slower and is horribly unstable. I equested a refund and was informed that I should see a credit in a few days. I disputed the charges and sent the email from Magix as proof just in case the credit doesn't come through. I checked my Magix account and they removed Vegas 16 and left 14 alone. I imagine things will stabilize by Vegas 19-20. Until then, I'm sticking with Vegas 14.

Funny how different hardware configs can affect a user's experience. 14 was by far the worst version ever released of Vegas Pro for me. It was responsible for me losing a couple of my biggest clients (I lost another to 15 as well) due to constant crashing, not to mention flat out incompatibility with the formats I was shooting in, forcing me to either shoot lower quality formats or convert to intermediates. 16, while far from perfect, has been the most stable version of Vegas I've ever used, at least since 12.

fr0sty wrote on 11/8/2018, 6:58 AM

IT ONLY works well when i uncheck "allow legacy gpu rendering" in preferences and disable graphic acceleration in video tab ..... i really .. really feel like i been ripped off ....

Sounds to me like there is a problem with your GPU/drivers, I'm using the same exact series, only it's a 970, and it works fine for me. It only working on legacy sounds like you are only able to use openCL, not NVENC/CUDA, which support was added for in Vegas 15 (another reason I hated 14, my Nvidia GPU didn't work AT ALL. Not even supported). I am, with my GTX 970 and the latest drivers, able to render both using timeline GPU acceleration as well as NVENC at the same time, and I can also use GPU accelerated plugins like Neat Video without issue. I did have issues in 16 before I updated my GPU drivers, a week or so ago.

I'd keep digging and make sure your GPU accel is working properly in other apps as well.

Here's my 970 rendering using GPU in both Vegas Pro 15 and 16.

PEchiOnlajn wrote on 11/8/2018, 7:38 AM

i guess im done with it, even now when i render video with gpu off it still has errors and bad frames in it ... when i do it in vegas 14 the video is clean and nice ...... where do i find an email or where do i contact MAGIX for a refund? i spent days trying to figure it out but it just doesn't work ....

OldSmoke wrote on 11/8/2018, 10:37 AM

IT ONLY works well when i uncheck "allow legacy gpu rendering" in preferences and disable graphic acceleration in video tab ..... i really .. really feel like i been ripped off ....

Sounds to me like there is a problem with your GPU/drivers, I'm using the same exact series, only it's a 970, and it works fine for me. It only working on legacy sounds like you are only able to use openCL, not NVENC/CUDA, which support was added for in Vegas 15 (another reason I hated 14, my Nvidia GPU didn't work AT ALL. Not even supported). I am, with my GTX 970 and the latest drivers, able to render both using timeline GPU acceleration as well as NVENC at the same time, and I can also use GPU accelerated plugins like Neat Video without issue. I did have issues in 16 before I updated my GPU drivers, a week or so ago.

I'd keep digging and make sure your GPU accel is working properly in other apps as well.

Here's my 970 rendering using GPU in both Vegas Pro 15 and 16.

It could also be an issue with the RAM.

PEchiOnlajn wrote on 11/8/2018, 11:15 AM

Wouldnt that be a problem in all versions though ? In vegas 14 im good on first try, no lags no problems no nothing .. flawless ....

vkmast wrote on 11/8/2018, 11:20 AM

where do i find an email or where do i contact MAGIX for a refund?

Search refund on this forum.