I’ve had similar problems, but they went away when I turned off GPU acceleration of video processing. Like this:

That unfortunately does not work every time. Disabling So4compoundplug.dll can help too, but even then it still doesn't work sometimes.

You're a victim of the memory leak bug that has made 10 bit video from my GH5 pretty much unusable without time consuming workarounds. We're hoping they fix it with the next update, that hopefully is coming before too long.

@fr0sty That seems like a strange diagnosis to me. What makes you think it's that? Memory leaks generally make things slow and/or crash. Can you link to any previous discussion that provides evidence of a memory leak? (I'm not disputing it; I just can't find it)

@MikeTe What format is your source media and how was it created?

This is the exact same thing that happens to me when I try to render either in 32 bit mode, or if I am using 10 bit video from my GH5 and do not have so4 disabled (which doing so breaks compatibility with the files, which makes me have to rewrap them as mxf, which takes a while and the editing performance of the resulting file is really bad). Throughout the process of trying to figure out my issues, it was said many times that a memory leak was the cause of the problem. It may be 2 separate problems, one that causes these symptoms and the other being a memory leak (I was getting low on memory crashes a lot as well while trying to figure out what the issue was), but I recognized that jumpy video immediately when I saw it.

This is the exact same thing that happens to me when I try to render either in 32 bit mode, or if I am using 10 bit video from my GH5 and do not have so4 disabled (which doing so breaks compatibility with the files, which makes me have to rewrap them as mxf, which takes a while and the editing performance of the resulting file is really bad). Throughout the process of trying to figure out my issues, it was said many times that a memory leak was the cause of the problem. It may be 2 separate problems, one that causes these symptoms and the other being a memory leak (I was getting low on memory crashes a lot as well while trying to figure out what the issue was), but I recognized that jumpy video immediately when I saw it.

There was a serious "resource leak" that was fixed in VP15 build 321. Has anyone provided any actual evidence (e.g. a Resource Monitor memory graph) that there is still a memory leak in build 321? I'm not sure that a "low on memory crash" means there's a memory leak unless that happens after a system is left untouched for some time.

Maybe Frostys referring to this testing of his project? where it crashes using so4.. dll, its caused by running out of memory. To be finally fixed in the next update, he was told. I observed the memory usage going through the roof and crashing, not finishing the render on my desktop, although ok on laptop.

https://www.vegascreativesoftware.info/us/forum/vegas-pro-15-update-4-build-321-general-discussion--110655/?page=4

See his post ...

“If anyone would like to try to replicate the issue I was having, this is the project and all dependent media. It's a big file, though, so only bother with it if you have some time and bandwidth to spare. The project should be set to QFHD 4K 23.97 32 bit (video levels) best quality with resample disabled. When you try to render out a 4K file (I've tested ProRes XQ, Magix AVC), GPU on or not, the frames start to get all jumbled up towards the middle of the project, eventually it will hang and go back and forth between 2 frames.

Setting it to 8 bit solves the rendering issue, but I wanted to offer this project file to see if we can get the issue fixed for those who need to use 32 bit projects.”

Thank you JN_. I do remember seeing those comments now, but the issue was really difficult to follow because it was spread over so many comments in the general thread, and I seem to recall that fr0sty's project wouldn't download for me, so I left you guys to it.

Were the exact causes and symptoms of the issue finally established? I never added it to the known issues post.

It will be interesting to see what source format @MikeTe is using. Also Mike, please let us know:

• Is GPU acceleration of video processing on or off (in Preferences > Video)?
• Is the Pixel format of your project 8-bit or 32-bit (in Project Properties)?
• Is so4compoundplug still enabled?

“Were the exact causes and symptoms of the issue finally established?” Yes, disabling the so4..dll on my PC fixed it, leaving it enabled on the laptop and it was ok, i.e. Fr0stys project.

Yes Nick, that particular thread was a little all over the place, long story short the so4 ..dll is still not fixed and probably will be in the next update, see the three quoted sections from that thread below.

Meant to say also, I’ve kept the project and will test again on PC and laptop to confirm aok with next VP15 update, and post results.

JN-

“Fixed .. Rendered out ok on PC.

I used the same nvenc render template as I previously mentioned.

I disabled the so4 ...dll on the PC and the erratic memory display in task manager disappeared, no black sections in render or on playback.

The reason I didn’t try this earlier was because it rendered out ok on the laptop with the so4 ..dll enabled.

I kinda stumbled upon it, it went like this ...

I decided to create proxies on the PC, but I kept getting an error message (without any much info) that Vegas couldn’t create the proxies.  So I disabled the dll and then Vegas created the proxies.  Then I did a render and I saw immediately it was going to work, steady mostly flat memory graph, low, around 12.2 gb, same as laptop render and no black pieces.

So the laptop doesn’t need the dll disabled but the PC does.

When auto creating the proxies, set in options, for some reason these files didn’t get proxies, so I created them individually.  P1011392.mov, P1011403.mov, P1011405.mov.

Just a note Fr0sty .. these 4 files you uploaded don’t appear to be used in the project 

P1011295.mov, P1011296.mov, P1011297.mov, P1011300.mov.”

MAGIX-Eric D

“We would still like to have you upload the project so we can take a look at this specific report, if possible. If you could, please drop us a link in your ticket to where we can download the files. Thanks.”

“Frosty ... Heard the word from Magix today that they've isolated the issue I've been having and will be fixing it in the next update, so I am going to remove my project from Google Drive. JN_, thank you for your help.”

Okay lot of comments, thanks. I'll try to answer questions. GPU acceleration is turned off. The source video is a MPEG @ 1920x1080 29.97fps (No sound). It was generated through an old version of Vegas Pro. Originally an AVI file from a Sony GL2 camera. Pixel Format is set to 32-bit floating point (full range). I don't know where to look for So4compoundplug.dll. JN_ wrote that he seen a similar effect about half way through the project. The first 30 minutes of my project are fine, the rest has the effect in the sample video. The movie is 1hr 45m long and the effect continues to the end. There are a number of still pictures in the complete video which are not affected. It's funny that the video sample was rendered separately. I marked a loop region where the effect shows up in the completed movie. It's like something happens at that point in the video rendering that messes everything up.

@MikeTe Thanks for the info. I think you have 2 alternative courses of action to try and resolve this:

1. Try setting the pixel format to 8-bit. It should make no difference (or negligible) to the final result and performance should be better.

2. Check if the MPEG file is being decoded by so4compoundplug.dll and if so, try disabling it. See this post: https://www.vegascreativesoftware.info/us/forum/avc-xavc-s-issues-in-vp15-try-disabling-so4compoundplug-dll--108345/

Please let us know if anything helps.

The MPEG file is being decoded by mcplug2.dll so the so4....dll isn't the problem. Set the pixel format to 8-bit instead of the 32-bit and render a short clip. No change. Effect still occurs. I'm not sure I understand why the effect only shows up between the 30 minute mark through to the end.

I also used MAGIX AVC/AAC MP4 using template Internet HD 1080p 29.97fps (Nvidia Nvenc). This rendered really fast and the resulting file doesn't show the effect. I rendered the entire movie like this and burned it to a Blu-ray disc using DVDA and spot checking different points on the disc looks good. I'm gonna watch the entire disc tonight.

Hmm.. for me it is triggered by 32 bit pixel format or if you use NVENC, especially when using 10 bit GH5 video. I also noticed it happened during certain points of the video, about a half hour in, the conditions to trigger it were just different for me. CPU renders usually don't exhibit that behavior, so this looks like quite a tricky bug to isolate.