The model is Asus GTX 1650 Super 4Gb, but the same thing is happening with Gigabyte GeForce RTX 4060 Ti 8Gb

So NVIDIA GPUs, that's helpful to know. I have a RTX 4060 system here, too. Any more clues you can share? Can you share a screenshot of your render template?

Also mediaInfo for the main media you use? https://www.vegascreativesoftware.info/us/forum/faq-how-to-post-mediainfo-and-vegas-pro-file-properties--104561/

Do either of the test projects in my signature render okay using MagixAVC with NVENC?

Thank You, RogerS!

I should say that the source files came from a Sony a7s3 camera. The reason for the upgrade from Vegas19 to Vegas22 was that the old software didn't decode 4k 100p files from the new camera.

I realised, from more tests, that the problem apear when appllying a LUT filter to the hole project.

Without the LUT shared GPU memory remain constant at a low level and the render succeed.

In Vegas 19 it works fine eather way. That's the curiosity.

This is my render template:

I will test the projects from your signature in the next few days and post the results.

Could you share MediaInfo (or even better a sample file via a storage site like Google Drive)? I'm surprised VP 19 didn't open the file from an a7sIII- what settings did you use?

The LUT filter was just a LUT Fx (not color grading panel) and set on the output video bus (fx next to the preview window)? I can try to replicate with your render settings. If the file type doesn't matter and it's only a LUT issue that's helpful to know, too.

This is info of the file from Vegas 22.

Link to the file: https://drive.google.com/file/d/1ZYdIt1Cn7qs5q3L2vLbX9yTZIFtW8-3O/view?usp=drive_link

and camera settings:

LUT filter was set on the output video bus, yes.

I believe the file type doesn't matter and it is a LUT filter in combination with Vegas 22 issue. Something is change in the new software since Vegas 19 works fine with the same settings and hardware.

Thank you very much. I tried to crash it with the VP 20 "ad project" adding a LUT to it and it gets to 7.4GB/8GB of VRAM but completes. Let me add this file of yours and see if I can crash it.

How much VRAM (GPU) and RAM do you have? 16GB is for your system? I have 8GB VRAM on the 4060 and 48GB on the system overall.

But yes, VP 19 and 22 are very different as the video engine has been partially rebuilt since build 300 of VP 21. Decoding is far faster (especially with NVIDIA!) but there are some glitches and it's possible there's a memory leak.

Are you rendering in 8-bit full or 32-bit full mode?

Also in your properties it says this 8-bit AVC file is opening with so4compound which is strange . Do you have "enable legacy AVC decoding" checked in preferences/ file io? If so that's the old decoder from VP 19. Try unchecking it. In VP 19 it's an even older decoder (compoundplug) that doesn't use GPU acceleration.

General
Complete name                  : C0425.MP4
Format                         : XAVC
Codec ID                       : XAVC (XAVC/mp42/iso6)
File size                      : 384 MiB
Duration                       : 13 s 440 ms
Overall bit rate mode          : Variable
Overall bit rate               : 240 Mb/s
Frame rate                     : 100.000 FPS
Encoded date                   : 2024-08-24 15:22:06 UTC
Tagged date                    : 2024-08-24 15:22:06 UTC

Video
ID                             : 1
Format                         : AVC
Format/Info                    : Advanced Video Codec
Format profile                 : High@L6
Format settings                : CABAC / 2 Ref Frames
Format settings, CABAC         : Yes
Format settings, Reference fra : 2 frames
Format settings, Slice count   : 8 slices per frame
Codec ID                       : avc1
Codec ID/Info                  : Advanced Video Coding
Duration                       : 13 s 440 ms
Bit rate mode                  : Variable
Bit rate                       : 189 Mb/s
Maximum bit rate               : 204 Mb/s
Width                          : 3 840 pixels
Height                         : 2 160 pixels
Display aspect ratio           : 16:9
Frame rate mode                : Constant
Frame rate                     : 100.000 FPS
Color space                    : YUV
Chroma subsampling             : 4:2:0
Bit depth                      : 8 bits
Scan type                      : Progressive
Bits/(Pixel*Frame)             : 0.227
Stream size                    : 302 MiB (79%)
Encoded date                   : 2024-08-24 15:22:06 UTC
Tagged date                    : 2024-08-24 15:22:06 UTC
Color range                    : Full
Metas                          : 3
Codec configuration box        : avcC

Audio
ID                             : 2
Format                         : PCM
Format settings                : Big / Signed
Codec ID                       : twos
Duration                       : 13 s 440 ms
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                    : 2.46 MiB (1%)
Encoded date                   : 2024-08-24 15:22:06 UTC
Tagged date                    : 2024-08-24 15:22:06 UTC

Other
ID                             : 3
Type                           : meta
Format                         : Sony Real Time Metadata
Codec ID                       : rtmd
Duration                       : 13 s 440 ms
Bit rate mode                  : Constant
Time code of first frame       : 02:40:54:72
Encoded date                   : 2024-08-24 15:22:06 UTC
Tagged date                    : 2024-08-24 15:22:06 UTC
TransferCharacteristics_FirstF : 0E06040101010508
ColorPrimaries_FirstFrame      : BT.709
MatrixCoefficients_FirstFrame  : BT.709
IrisFNumber_FirstFrame         : 4.000338
FocusPositionFromImagePlane_Fi : 3.748 m
LensZoom35mmStillCameraEquival : 122.800 mm
LensZoomActualFocalLength_Firs : 105.000 mm
FocusRingPosition_FirstFrame   : 87.9913%
ZoomRingPosition_FirstFrame    : 99.9985%
AutoExposureMode_FirstFrame    : Manual
AutoFocusSensingAreaSetting_Fi : Full Screen Sensing Auto
ImageSensorDimensionEffectiveW : 32.256 mm
ImageSensorDimensionEffectiveH : 18.144 mm
CaptureFrameRate_FirstFrame    : 100.000 fps
ShutterSpeed_Angle_FirstFrame  : 355.0°
ShutterSpeed_Time_FirstFrame   : 1/101 s
CameraMasterGainAdjustment_Fir : 26.00 dB
ISOSensitivity_FirstFrame      : 12800
ElectricalExtenderMagnificatio : 100%
AutoWhiteBalanceMode_FirstFram : Automatic
CameraAttributes_FirstFrame    : ILCE-7SM3 3797372
ExposureIndexofPhotoMeter_Firs : 12800

Thank you, RogerS!

My project is two hours long and the crush occurs when the 16GB of Shared GPU memory is full (at about 15-20% renderred). So i believe with the smaller projects it will work.

I have 32 Gb DDR5 on the system and the video card installed now (GTX 1650 Super) 4GB.

I took the VP 20 sample ad, added your video to it, put a LUT on the output bus and went into 32-bit full mode. It used most of my ram but didn't crash. Maybe others with less ram and VRAM can try the same thing and see if they can replicate the crash.

I'm rendering in 8-bit full.

Oh, indeed i had "enable legacy AVC decoding" checked in both VP19 and VP22. After unchecking it, VP19 can decode the 100p file frum a7s3. The render is still going fine with no increasing of Shared GPU mem. Thank you very much!.

The problem remain in VP22. It renders about 15% from a two hour project and it crushes when shared GPU mem is full.

Maybe others with less ram and VRAM can try the same thing and see if they can replicate the crash.

For me on laptop from signature not possible to replicate that crash, look

Yes, because in my case the project is two hour long and the crash apear at 15-17%of rendering time, when the Shared GPU mem is full. Until then everything is ok. So, if anyone try to replicate the crush, shoud have a long enough project wich brings virtual memory to full.

Thank you, j-v!