Vegas 22 Build 122 and Memory Issue

jimingo-1 wrote on 10/15/2024, 9:03 AM

In the last build I was experiencing the memory leak issue but looking through the release notes of Build 122, it appears that the memory leak issue was fixed. However, with 122 I'm having major issues that is preventing me from rendering both 8 bit and 32 bit float videos.

My media is mostly HEVC footage shot with the Sony FX3 and the same types of projects I rendered successfully in Vegas 20. Now, I can't render my projects on any of my three computers (all Intel). One of the projects I'm trying to render is an 8 bit, hour and a half long project to Magix HEVC. Failed on all three computers - I tried Main Concept, QSV and VCE and all ways failed. On one of my computers I get a Vegas error message telling me I've run out of memory while the others just stop rendering or crash. I'm currently trying to render to other formats to see if that will work but I'll have to wait and see.

Also, I'm having issues with a 32 bit float project. The one I'm trying to render is just 8 minutes in length and takes 1.5 hours to render. This is a project that would have rendered in 20 minutes in Vegas 20. It starts out rendering at normal speeds and then gradually slows to a crawl. I've tried rendering many different ways with different settings and I can't find one that works.

Was the memory leak supposed to be fixed in build 122 or are others still experiencing this as well? Also, if there are magical settings that can fix this, please let me know. For now, the only solution is to render in pieces to ProRes and stitch together but I'd rather not.

Thanks

Back to post

Comments

RedRob-CandlelightProdctns wrote on 12/3/2024, 5:23 PM

OK -- here are two videos showcasing at least ONE instance where this points to an issue with memory, some plug-ins, and the non-legacy GPU handling in Vegas. During renders (not in these demo videos) I observed similar, with memory climbing a bit faster.

VIDEO 1 -- *not* using the legacy decoding, RX470

https://vimeo.com/1035789196/84695a5243

Single 4K video, project set to 1080. Event has Neat Video on it with temporal sharpening.
In the video, we watch the memory usage during playback, toggling the event FX on and off.
Observation -- when the FX is on, memory keeps climbing during playback. When it's off, memory holds static during playback.

VIDEO 2 -- using legacy decoding, RX470

https://vimeo.com/1035790773/8bc9817327

Same project
In the video, we watch the memory usage during playback, toggling the event FX on and off.
Observation -- when the FX is turned on, memory keeps for a second then stabilizes and holds constant. When it's off, memory also holds static during playback.

RogerS wrote on 12/3/2024, 5:24 PM

10bit 422 may be less likely to show issues as AMD GPUs can't decode it. Wonder if that is a clue.

jimingo-1 wrote on 12/3/2024, 5:28 PM

RedRob, I’m in the same boat. I do get better results with with iGPU off and GPU set to AMD or Nvidia (depending on the computer I’m using) but there’s still issues and I suspect just having an Intel component brings those issues to life. Again, I could be wrong but I don’t think I’ve seen the memory issue with all non-Intel parts.

RedRob-CandlelightProdctns wrote on 12/3/2024, 5:32 PM

@RogerS

Interesting! That'd imply his GPU isn't being used for the decode and only helping with other processing and possibly the render.

My source is 4:2:0 8-bit (no judging!)

Similar disclaimer -- the samples demoing the problem (above) -- we had 7 cameras rolling so no judging the footage please ;-) By design, there are moments we wouldn't be using that camera's take.

RedRob-CandlelightProdctns wrote on 12/3/2024, 5:34 PM

@VEGASDerek Any chance this could be prioritized in the dev/fix queue? I'm happy to help however you need me to. As you well know, "memory issues" have long been a sore spot, and thankfully your team has squished many over the years! This one seems to be... well.. still there.

RogerS wrote on 12/3/2024, 5:35 PM

Yes, and thus may use less VRAM so less likely to demonstrate such issue is my guess.

I wish we had a sample project with media that runs out of ram on 8GB VRAM systems we could share with the developers.

No judgment here, it's part of the deal with live events.

RedRob-CandlelightProdctns wrote on 12/3/2024, 5:42 PM

I wish we had a sample project with media that runs out of ram on 8GB VRAM systems we could share with the developers.

Is that a not-so-subtle hint? ;-)

When you say 8GB VRAM, are you talking about GPU RAM? My GPU isn't running out.. it's overall system RAM (demonstrated in the video)

I can find a BTS clip that's short that probably, played on loop, would demonstrate the problem. If you watched my vids above, you can't get much simpler. One clip on timeline with an FX. Play. It happens.

RogerS wrote on 12/3/2024, 8:17 PM

@RedRob-CandlelightProdctns Yes, for GPU Vram as in the other thread we had the same media tested with two AMD systems, one an 8GB GPU and one 12GB and the 12 wouldn't crash. Modest amounts of system ram would also be helpful as high amounts may mask the issue. If these are two separate issues with separate causes that's also important to know (VRAM vs overall memory issue).

We really do need something to replicate and get to the bottom of this. I can't directly help not having an AMD GPU but others have a variety of systems.

EruDebu wrote on 12/3/2024, 11:27 PM

gpu stuck on 95% happens to me at least constantly with BCC light leaks OBSOLETE when rendering on 4k
also vram gets topped i have 64 system ram and 8 vram (rtx 3070)
i'm sure it can be an incompatibility with BCC obsolete plugins, but just saying in case someone is having the same issue

Reyfox wrote on 12/4/2024, 6:57 AM

@RedRob-CandlelightProdctns to see the amount of GPU RAM is being used, you have to go in Task Manager to the Performance tab, then click on the GPU. It will tell you how much dedicated GPU memory is being used from the GPU, and there should be GPU Memory which would include system RAM as a virtual GPU memory.

I will test later on. I too experienced that issue with rising system RAM where it would go all the way to the my system limit, causing everything else to screech to a halt in the past. I think @Gid was able to get his system RAM to be used on a simple clip to get over 100GB on his massive 256GB computer, but he would have to comment on it.

I'll do the same test as you did.

And out of curiosity, does this happen with only NeatVideo applied?

Reyfox wrote on 12/4/2024, 9:44 AM

@RedRob-CandlelightProdctns, after looking at your video, I am seeing the same thing with the continually rising of system RAM and a higher GPU RAM usage compared to legacy AVC decoding.

When using legacy AVC, system RAM usage levels out and doesn't increase. Without using legacy AVC, system RAM usage does NOT stop increasing. The more you play back your timeline, the RAM continues to grow.

With the clip I was working with (no effects), GPU RAM with legacy AVC was 5.1GB. With legacy AVC unchecked, 8.8GB. This is with only Vegas 22 open. No browser.