Hello and Merry Christmas!

The CPU model is Intel(R) Core(TM) i7-10700 CPU @ 2.90GHz, 2904 MHz, 8 core processors, 16 logical processors.

This issue has happened to me in different projects. The first one was a project where I used the same file on two additional tracks and zoomed in to simulate a multicamera setup (a very simple project but with color corrections and sharpen effects). The second one was a more complex project, but also very simple, which I have always done in Vegas Pro 17 without issues: a multicamera setup with two cameras and a composition of both together on screen (also with color corrections and sharpen effects).

I’ve attached the Mediainfo for both projects. Unfortunately, I cannot share the files due to data protection policies (it’s work-related content).

I should also mention that this is not a GPU issue, as it started happening with a GTX 1080, which I replaced with the RTX 4070 Ti I mentioned earlier.

I can always render with the CPU, but I’d like to work with the GPU as I have done so far.

Thanks!

General
Complete name                            : F:\Mis videos\C0007.MP4
Format                                   : XAVC
Codec ID                                 : XAVC (XAVC/mp42/iso2)
File size                                : 12.3 GiB
Duration                                 : 18 min 51 s
Overall bit rate mode                    : Variable
Overall bit rate                         : 93.1 Mb/s
Frame rate                               : 29.970 FPS
Encoded date                             : 2024-12-02 20:43:29 UTC
Tagged date                              : 2024-12-02 20:43:29 UTC

Video
ID                                       : 1
Format                                   : AVC
Format/Info                              : Advanced Video Codec
Format profile                           : High@L5.1
Format settings                          : CABAC / 2 Ref Frames
Format settings, CABAC                   : Yes
Format settings, Reference frames        : 2 frames
Format settings, Slice count             : 8 slices per frame
Codec ID                                 : avc1
Codec ID/Info                            : Advanced Video Coding
Duration                                 : 18 min 51 s
Bit rate mode                            : Variable
Bit rate                                 : 91.4 Mb/s
Maximum bit rate                         : 100.0 Mb/s
Width                                    : 3 840 pixels
Height                                   : 2 160 pixels
Display aspect ratio                     : 16:9
Frame rate mode                          : Constant
Frame rate                               : 29.970 (30000/1001) FPS
Color space                              : YUV
Chroma subsampling                       : 4:2:0
Bit depth                                : 8 bits
Scan type                                : Progressive
Bits/(Pixel*Frame)                       : 0.368
Stream size                              : 12.0 GiB (98%)
Encoded date                             : 2024-12-02 20:43:29 UTC
Tagged date                              : 2024-12-02 20:43:29 UTC
Color range                              : Limited
Color primaries                          : BT.709
Transfer characteristics                 : xvYCC
Matrix coefficients                      : BT.709
Metas                                    : 3
Codec configuration box                  : avcC

Audio
ID                                       : 2
Format                                   : PCM
Format settings                          : Big / Signed
Codec ID                                 : twos
Duration                                 : 18 min 51 s
Bit rate mode                            : Constant
Bit rate                                 : 1 536 kb/s
Channel(s)                               : 2 channels
Sampling rate                            : 48.0 kHz
Bit depth                                : 16 bits
Stream size                              : 207 MiB (2%)
Encoded date                             : 2024-12-02 20:43:29 UTC
Tagged date                              : 2024-12-02 20:43:29 UTC

Other
ID                                       : 3
Type                                     : meta
Format                                   : Sony Real Time Metadata
Codec ID                                 : rtmd
Duration                                 : 18 min 51 s
Bit rate mode                            : Constant
Time code of first frame                 : 00:00:00:00
Encoded date                             : 2024-12-02 20:43:29 UTC
Tagged date                              : 2024-12-02 20:43:29 UTC
IrisFNumber_FirstFrame                   : 8.000000
FocusPositionFromImagePlane_FirstFrame   : 1.360 m
AutoExposureMode_FirstFrame              : Manual
AutoFocusSensingAreaSetting_FirstFrame   : Manual
ShutterSpeed_Time_FirstFrame             : 1/80 s
CameraMasterGainAdjustment_FirstFrame    : 21.00 dB
ISOSensitivity_FirstFrame                : 1250
ElectricalExtenderMagnification_FirstFra : 100%
AutoWhiteBalanceMode_FirstFrame          : Automatic

General
Complete name                            : F:\Mis videos\MG_8281_KOtY4U.mp4
Format                                   : MPEG-4
Format profile                           : Base Media
Codec ID                                 : isom (isom/iso2/avc1/mp41)
File size                                : 8.42 GiB
Duration                                 : 25 min 37 s
Overall bit rate mode                    : Variable
Overall bit rate                         : 47.0 Mb/s
Frame rate                               : 30.000 FPS
Movie name                               : IMG_8281_KOtY4U
Performer                                : WinX HD Video Converter Deluxe
Writing application                      : Lavf58.29.100

Video
ID                                       : 1
Format                                   : AVC
Format/Info                              : Advanced Video Codec
Format profile                           : Main@L4
Format settings                          : CABAC / 3 Ref Frames
Format settings, CABAC                   : Yes
Format settings, Reference frames        : 3 frames
Codec ID                                 : avc1
Codec ID/Info                            : Advanced Video Coding
Duration                                 : 25 min 37 s
Bit rate mode                            : Variable
Bit rate                                 : 46.7 Mb/s
Maximum bit rate                         : 6 000 kb/s
Width                                    : 1 920 pixels
Height                                   : 1 080 pixels
Display aspect ratio                     : 16:9
Frame rate mode                          : Constant
Frame rate                               : 30.000 FPS
Color space                              : YUV
Chroma subsampling                       : 4:2:0
Bit depth                                : 8 bits
Scan type                                : Progressive
Bits/(Pixel*Frame)                       : 0.750
Stream size                              : 8.36 GiB (99%)
Title                                    : Core Media Video
Codec configuration box                  : avcC

Audio
ID                                       : 2
Format                                   : AAC LC
Format/Info                              : Advanced Audio Codec Low Complexity
Codec ID                                 : mp4a-40-2
Duration                                 : 25 min 37 s
Duration_LastFrame                       : -1 ms
Bit rate mode                            : Constant
Bit rate                                 : 319 kb/s
Channel(s)                               : 2 channels
Channel layout                           : L R
Sampling rate                            : 44.1 kHz
Frame rate                               : 43.066 FPS (1024 SPF)
Compression mode                         : Lossy
Stream size                              : 58.5 MiB (1%)
Title                                    : Core Media Audio
Default                                  : Yes
Alternate group                          : 1

@fortfiesta

As a diagnostic technique, to eliminate media as problem source, I would convert the media encoded by WinX HD Video Converter Deluxe to anything else in Shutter Encoder (download here). Since it's me, I would use Apple Pro Res.

Report your results.

Agree with John on the diagnostic.

If the problem is the media it possible to make non-confidential media (doesn't have to have content) the same way as the original one for testing purposes? The Sony one should be fine- looks similar to files I use, the other one I am not familiar with.

Hello again!

Thank you for you answer, @john_dennis. I’ve completed the test with the new ProRes files and attached the Mediainfo of the converted file for your reference.

Unfortunately, the issue persists. When the GPU's dedicated memory usage reaches its maximum, the system RAM starts to fill up until it also reaches its limit. Based on this behavior, I don’t believe the problem lies with the media format. Instead, it seems that the VRAM is overflowing into the system RAM, and this overflowed data is not being cleared properly.

For very simple projects, the program doesn’t crash, but I suspect that’s because the amount of information being overflowed is minimal and doesn’t reach a critical "flood" point. Of course, these are just my assumptions based on what I’m observing.

Additionally, I’ve tried switching between Studio and Game Ready drivers, but the result remains the same.

And thank you for your input @RogerS but unfortunately, I don’t have access to raw footage with the same characteristics to create non-confidential media for testing. However, I did follow the suggestion to convert the original files to ProRes (using Shutter Encoder) to see if the issue persisted. Despite this conversion, the problem remains unchanged.

Let me know if you have any additional ideas or suggestions!

Thank you again for your help and suggestions. Please let me know if you have any further ideas on how to address this issue.

P.S.: I didn’t experience these issues when using Vegas Pro 17, even with similar or more complex projects. This problem only started happening with Vegas Pro 22..

General
Complete name                            : F:\Mis videos\IMG_8281_KOtY4U_1.mov
Format                                   : MPEG-4
Format profile                           : QuickTime
Codec ID                                 : qt   0000.02 (qt  )
File size                                : 23.5 GiB
Duration                                 : 25 min 37 s
Overall bit rate mode                    : Variable
Overall bit rate                         : 131 Mb/s
Frame rate                               : 30.000 FPS
Encoded date                             : 2024-12-26 12:15:12 UTC
Tagged date                              : 2024-12-26 12:15:12 UTC
Writing application                      : Lavf61.9.100

Video
ID                                       : 1
Format                                   : ProRes
Format version                           : Version 0
Format profile                           : 422
Codec ID                                 : apcn
Duration                                 : 25 min 37 s
Bit rate mode                            : Variable
Bit rate                                 : 129 Mb/s
Width                                    : 1 920 pixels
Height                                   : 1 080 pixels
Display aspect ratio                     : 16:9
Frame rate mode                          : Variable
Frame rate                               : 30.000 FPS
Minimum frame rate                       : 15.000 FPS
Maximum frame rate                       : 30.000 FPS
Color space                              : YUV
Chroma subsampling                       : 4:2:2
Scan type                                : Progressive
Bits/(Pixel*Frame)                       : 2.081
Stream size                              : 23.2 GiB (99%)
Title                                    : Core Media Video
Writing library                          : Apple
Encoded date                             : 2024-12-26 12:15:12 UTC
Tagged date                              : 2024-12-26 12:15:12 UTC
Color primaries                          : BT.2020
Transfer characteristics                 : HLG
Matrix coefficients                      : BT.2020 non-constant

Audio
ID                                       : 2
Format                                   : PCM
Format settings                          : Little / Signed
Codec ID                                 : sowt
Duration                                 : 25 min 37 s
Bit rate mode                            : Constant
Bit rate                                 : 1 536 kb/s
Channel(s)                               : 2 channels
Channel layout                           : L R
Sampling rate                            : 48.0 kHz
Bit depth                                : 16 bits
Stream size                              : 282 MiB (1%)
Title                                    : Core Media Audio
Default                                  : Yes
Alternate group                          : 1
Encoded date                             : 2024-12-26 12:15:12 UTC
Tagged date                              : 2024-12-26 12:15:12 UTC

If the problem remains then as you say the media isn't the issue. Could I just get the .veg file to test? I can add my own media. I have NeatVideo. If there are other third party Fx in use I may not have them, though.

VP 17 and VP 22 are very different programs with big changes to the video engine and new media decoders. If we can isolate the issue the developers will have a better chance of fixing it.

Hi @RogerS,

Thank you for your response!

Unfortunately, this issue is not isolated to a single project. It happens with any project, and all of them are newly created in Vegas Pro 22—none are legacy files from Vegas Pro 17. I’m unable to share the .veg file, but I’ve attached an image of the project as an example.

Here’s a breakdown of the project structure:

• The first red track is a watermark.
• Below that, there are four tracks with different camera compositions, which I toggle on or off as needed.
• At the bottom are the voiceover and music tracks.

The project has effects applied to individual video tracks (except for the watermark) and at the media output level. These effects are limited to color corrections and sharpening—no third-party plugins are used. NeatVideo is disabled as well.

The problem seems to occur in the GPU when there are multiple layers of composition and effects applied, rather than due to any specific third-party plugin. I can render with only CPU.

I hope this explanation and the attached image help clarify the setup.

Thanks again for your help!

Does the VP 20 benchmark project in my signature render with GPU? That's also a complex multi-track GPU-heavy project. It does render here without issue.

Hi @RogerS

Thank you for your suggestion! I downloaded it and tested it as-is—it rendered perfectly with GPU acceleration enabled. I even extended the timeline and added additional effects at the end, but it still worked without any issues.

Given this, I’m now unsure what might be causing the problem in my projects. To further narrow it down, I managed to export my project without the audio files (after retesting and confirming it still doesn’t work). I’ve attached the .veg file and included the two LUTs I’ve used in the project.

Link: https://we.tl/t-A1T3tSvYHJ

Hopefully, this helps identify what’s going wrong. Thank you again for all your help!

@fortfiesta

I downloaded and rendered you whole project with Voukoder. As downloaded, I replaced one MOV file with an .mp4 file of the same name.

The "interview" section was agonizingly slow to render and even seemed to be recursive, replacing the time to completion estimate multiple times before it finished. My memory usage stayed ruler flat, however.

Personal Perception

Nothing in the included content warrants a 32bit project.

/Personal Perception

I rendered the "interview" section after changing the project setting to 8bit video levels with these results.

All done on the machine in my signature with GPU setting out of the box.

@fortfiesta

I downloaded and rendered you whole project with Voukoder. As downloaded, I replaced one MOV file with an .mp4 file of the same name.

The "interview" section was agonizingly slow to render and even seemed to be recursive, replacing the time to completion estimate multiple times before it finished. My memory usage stayed ruler flat, however.

Personal Perception

Nothing in the included content warrants a 32bit project.

/Personal Perception

I rendered the "interview" section after changing the project setting to 8bit video levels with these results.

All done on the machine in my signature with GPU setting out of the box.

Hey @john_dennis

Thank you so much for testing my project and for your detailed feedback!

I don’t have Voukoder installed at the moment, but I noticed from your signature that your machine uses Intel UHD Graphics. The issue I’m experiencing specifically occurs when working with my NVIDIA GPU and rendering using the "NV Encoder" (NVENC). I can render perfectly fine if I switch to Mainconcept AVC and disable GPU acceleration entirely. However, that’s not ideal since I’d like to make use of the GPU.

I also just tested the project after switching to 8-bit (video levels) in the project settings, as you suggested. Unfortunately, the same problem persists.

Thanks again for your insights! Let me know if you have any other ideas on how to approach this.

@fortfiesta said: "I can render perfectly fine if I switch to Mainconcept AVC and disable GPU acceleration entirely. However, that’s not ideal since I’d like to make use of the GPU." "Let me know if you have any other ideas on how to approach this."

1. Consider rendering with Voukoder and allow Voukoder to control the NVENC encoder. I don't use hardware encoders, so I've not tested that scenario.
2. Send Jensen Huang a nasty email expressing your dis-satisfaction with NVENC.
3. Don't sell your Nvidia stock until you see a significant downward trend.

Enabling HW Encoders in Voukoder.

Hey @john_dennis

It feels more like a love-hate relationship between Vegas Pro 22 and NVIDIA GPUs. Maybe they should send Mr. Huang an email instead! 😄

Jokes aside, I took your advice and installed Voukoder to test rendering with the NVENC encoder. I used the following settings:

Video Encoder (NVIDIA H.264):

• Codec: H.264 (NVIDIA NVENC)
• Encoding Mode: VBR
• Bitrate: 10,000–20,000 kbps
• Profile: High
• Level: 4.2

Audio Encoder (AAC):

• Codec: AAC
• Bitrate: 320 kbps
• Sample Rate: 48 kHz
• Channels: Stereo

Unfortunately, the issue persists. The RAM fills up to the limit during rendering until the system crashes, just like before. It’s clear that the problem lies with the GPU handling complex projects, where the VRAM floods the RAM for some reason and doesn’t release the overflow. But @RogerS test project worked.

It seems this issue is tied to how the GPU handles these types of projects with NVENC.

Thanks again!

I tested the sample project as is with MagixAVC (NVENC) and my 8GB RTX 4060 mobile (current studio driver) It took a while but completed.

It did use all system ram and nearly all of the GPU ram.

The biggest problem I see is are multiple green frames.

These random green frames have plagued me since VP 21.300 and only seem to affect NVIDIA GPU users.

Project structure wise it has more sharpen Fx than I think it needs and accentuates noise. Just at the media level and maybe one at output should be enough. This is likely seriously affecting performance.

I only found one LUT Fx (output)- is there another?

I also agree it doesn't need 32-bit mode. There's no log conversion that would really benefit from it.

I think the limited performance, high ram usage and artifacts is related to the VEGAS video engine rebuild being unfinished. Hopefully there will be a patch to 22 that will address these issues with NVIDIA GPUs.

Until then I'd stick with the workaround you found and consider simplifying the Fx (media, track, event and output may be too much for VEGAS 22 for now) for a better experience.

I haven't encoded your project but the memory leak looks to be related to your LUT on the output, and possibly LUTs anywhere else. Have you tried encoding without LUTs, at this stage I don't think it's safe to use LUTs in VP22b194

Your IMG*.mp4 files all have a GOP of 250, Vegas can't handle that, it's why if you look at GPU 3d and decode graphs in task manager when encode is at slowest the GPU usage will be unrealistically high, it's because Vegas keeps requesting new frames to be decoded from GPU and then throws them away and requests them again causing congestion with processing and decode. But that is more a symptom of a deeper problem with Vegas then the cause,

TRY: Turn LUTS off, re-encode your IMG*.mp4 files using a GOP of 25 (or similar small GOP) . In handbrake use Production Standard preset, you can also do it in shutter encoder, but a more manual process, GOP size is in advanced section.

Masking, and possibly reversing the image also causes Vegas to get slower, never use mask feathering it gets unbearably slow

I mistakenly rendered out first using CPU, then GPU.

I used my laptop, see "Signature".

Intel 11th. Gen 8 core CPU. i9-11900K

Nvidia RTX 3080 GPU

Win 10

Rendered out fully AOK using both methods. Time taken CPU/GPU 54/45 minutes.

I rendered out using default selected template at 25fps same as Project Properties.. I see that source media is 29.97/30 fps.

I noticed ( in 92%+) that the render dialog time "remaining time" sometimes goes completely to zero or close to then starts again. This needs looking at.

When loading project I get a missing file message for IMG_8283_KOtY4U.mov so replace with IMG_8283_KOtY4U.mp4.

My GPU driver is not up to date. It's 26th-September-2024 .. 32.0.15.6590.

Maybe this older driver works better?

The IMG_ ... files are as already mentioned 250 GOP. Best to change to lower GOP

The MAH ... files are ok at 15 GOP.

The audio of some files is higher than my default selected 192k. I would normally raise that to the value of the highest files audio setting in the render template so as not to lose quality.

I didn't detect anything abnormal in the video displayed section near the end, no green frames.

Hi everyone,

I’ve run 5 new tests to dig deeper into this issue:

1. I converted the GOP of all files to 25: Unfortunately, the RAM still fills up and crashes the render.
2. Using the same files with the converted GOP, I disabled the NVIDIA GeForce RTX 4070 Ti hardware decoder in File I/O: The issue persists, and the RAM still collapses.
3. With the same GOP-converted files and hardware decoding re-enabled, I rendered without the LUT on the output: It successfully rendered. GPU memory remained stable, and RAM usage didn’t spike.
4. I went back to the original files with the initial GOP settings and tried rendering without the LUT: It also successfully rendered.
5. Finally, I removed the LUT from the output and applied it instead as an event on an Adjustment Track: The GPU memory filled up again, and the RAM overflowed as a result.

I reviewed other projects, and in those that previously caused issues, I also had a LUT applied on the output. However, I have one very complex project (a music video) with extensive color grading, including three LUTs (VRAW files) and additional corrections, which renders without any issues.

At least I feel more confident knowing that avoiding LUTs on the output seems to solve the issue in most cases. Still, I’m not sure I fully understand the root cause or how to consistently prevent it. The fact that some projects with LUTs work perfectly while others don’t is a bit confusing.

Any further insights or advice would be greatly appreciated!

PD: @Former user why is not safe to use LUTs in VP22b194?

Great testing.

Does it make a difference if you apply the LUT in the color grading panel? (Input tab)

The serious memory leak issue in VP22 when using the Vegas 'LUT Filter' FX with nVidia GPU acceleration enabled was reported by at least two people on the 'VEGAS Pro 22 Build 122 General Discussion' thread (including me) and the same issue exists in build 194.

The only solutions I've found so far are to disable GPU acceleration or use a 3rd party LUT filter FX instead (e.g. '3D LUT Creator OFX Plugin' ) but that slows down the rendering speed.

 

PD: @Former user why is not safe to use LUTs in VP22b194?

There's been many reports of color grading and LUTS causing memory leaks, not sure if CGP is still an issue but LUTS are and with your project the memory leak isn't apparent at very beginning so could come as a surprise . Did changing GOP from 250 to 25 change the encoding speed and also improve timeline performance or was it still just as slow?

It's strange such a simple project has such low encoding speeds. Approximately where the cursor is I start seeing memory leak with LUT on, but no leak with LUT off.

Not sure if you're still operating in 32bit, but successful encode was 8bit project, Output LUT OFF, encode HEVC NVENC via Voukoder. All Vegas settings are default. You mentioned 2 LUTs or 2 LUT placements at one stage, I don't think that's in the project you shared, remove all LUTs. I"m used to seeing VRAM overflowing into system memory, but for your project (for me) the memory leak does not involve VRAM, it stays constant but system memory goes up until into full.