I have read that thread and for me the rendering just works if I don't edit anything. So the memory issue is only while editing, which is the thing you do most of the time. I will check the settings if I can disable gpu preview rendering. But that defeats a bit of the upgrade purpose. VP22 should be better in use with more GPU pergomance while editing.

In the other thread there was discussion of enabling the legacy (old) decoder in options/preferences/ file io . I'd see if that works before disabling the GPU in preferences/ video.

Of course VEGAS should be able to use the GPU fully for media decoding and the timeline (fx) while editing.

Do you have any other info about when the memory leak occurs? Does it matter what type of media you use (if it matters can you share MediaInfo for it)? https://www.vegascreativesoftware.info/us/forum/faq-how-to-post-mediainfo-and-vegas-pro-file-properties--104561/

@Solmea you mention a Nikon 8min file that causes issue, would it be possible for you to share it?

I've had GPU RAM reach almost all of the 12GB that I have, but never had any issues during playback or rendering.

Now system RAM creeping up to almost all the 32GB has caused some issues where I had to shut down everything running except Vegas.

Wow, the manual on the z30 is remarkably deficient. Only info on settings for video seems to be frame size and bitrate with the 4k format only being described as UHD. I guess the only way to learn more is to try them all and look at the clips with MediaInfo. Fwiw, I'm not having any problems editing 4k hevc 4:2:0 10-bit clips on a Xeon with 5700xt gpu with the 24.11.1 Amd driver. I do optimize the driver's pixel and sync settings for video editing specific to my 4k monitor so you might want to look at that too.

@Solmea you mention a Nikon 8min file that causes issue, would it be possible for you to share it?

I've had GPU RAM reach almost all of the 12GB that I have, but never had any issues during playback or rendering.

Now system RAM creeping up to almost all the 32GB has caused some issues where I had to shut down everything running except Vegas.

I will have a look tonight if I can strip the case down to one movie file only.. this project I tested with was with two video streams... I will get back on that and send you a direct message with a link.

@Solmea thanks!

Wow, the manual on the z30 is remarkably deficient. Only info on settings for video seems to be frame size and bitrate with the 4k format only being described as UHD. I guess the only way to learn more is to try them all and look at the clips with MediaInfo. Fwiw, I'm not having any problems editing 4k hevc 4:2:0 10-bit clips on a Xeon with 5700xt gpu with the 24.11.1 Amd driver. I do optimize the driver's pixel and sync settings for video editing specific to my 4k monitor so you might want to look at that too.

I don't exactly get what you mean with this... I recorded video with the Z30 in 4k25fps in the best quality mode. And I render fullHD 25fps video... and the project I work in is also fullHD 25fps. So I have the fps in sync. But I will spend some time tonight to create a full report and post a website link to with some graphs of the task manager gpu memory.

In the other thread there was discussion of enabling the legacy (old) decoder in options/preferences/ file io . I'd see if that works before disabling the GPU in preferences/ video.

Of course VEGAS should be able to use the GPU fully for media decoding and the timeline (fx) while editing.

Do you have any other info about when the memory leak occurs? Does it matter what type of media you use (if it matters can you share MediaInfo for it)? https://www.vegascreativesoftware.info/us/forum/faq-how-to-post-mediainfo-and-vegas-pro-file-properties--104561/

I will try the old decoder tonight to see if it makes a difference. Thanks

General Media Info:

Complete name                            : G:\36-Golden Stars.MOV
Format                                   : MPEG-4
Format profile                           : QuickTime
Codec ID                                 : qt   2016.09 (qt  /niko)
File size                                : 2.19 GiB
Duration                                 : 2 min 29 s
Overall bit rate                         : 126 Mb/s
Frame rate                               : 25.000 FPS
Encoded date                             : 2024-07-06 17:32:25 UTC
Tagged date                              : 2024-07-06 17:32:25 UTC

Video
ID                                       : 1
Format                                   : AVC
Format/Info                              : Advanced Video Codec
Format profile                           : High@L5.1
Format settings                          : 1 Ref Frames
Format settings, CABAC                   : No
Format settings, Reference frames        : 1 frame
Format settings, GOP                     : M=1, N=12
Codec ID                                 : avc1
Codec ID/Info                            : Advanced Video Coding
Duration                                 : 2 min 29 s
Bit rate                                 : 124 Mb/s
Width                                    : 3 840 pixels
Height                                   : 2 160 pixels
Display aspect ratio                     : 16:9
Frame rate mode                          : Constant
Frame rate                               : 25.000 FPS
Color space                              : YUV
Chroma subsampling                       : 4:2:0
Bit depth                                : 8 bits
Scan type                                : Progressive
Bits/(Pixel*Frame)                       : 0.599
Stream size                              : 2.16 GiB (99%)
Language                                 : English
Encoded date                             : 2024-07-06 17:32:25 UTC
Tagged date                              : 2024-07-06 17:32:25 UTC
Color range                              : Full
Color primaries                          : BT.709
Transfer characteristics                 : BT.709
Matrix coefficients                      : BT.709
Codec configuration box                  : avcC

Audio
ID                                       : 2
Format                                   : PCM
Format settings                          : Little / Signed
Codec ID                                 : sowt
Duration                                 : 2 min 29 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                              : 27.4 MiB (1%)
Language                                 : English
Encoded date                             : 2024-07-06 17:32:25 UTC
Tagged date                              : 2024-07-06 17:32:25 UTC

VEGAS file properties:
General
  Name: 36-Golden Stars.MOV
  Folder: G:\
  Type: AVC
  Size: 2,30 GB (2.351.043.533 bytes)
  Created: zaterdag 6 juli 2024, 21:10:28
  Modified: zaterdag 6 juli 2024, 18:32:25
  Accessed: maandag 2 december 2024, 21:51:00
  Attributes: Archive

Media information
  Stream format: MPEG-4
  Video stream #1
    Video format: AVC
    Resolution: 3840 x 2160 px
    Aspect ratio: 16:9
    Color depth: 8 bit
    Frame rate: 25.000 fps
    Scan type: Progressive
    Bit rate: 124244261 bps
  Audio stream #1
    Audio format: PCM
    Sampling rate: 48000 Hz
    Channels: 2 channels
    Bit rate mode: Constant
    Bit rate: 1536000 bps

Streams
  Video: 00:02:29,400, 25,000 fps progressive, 3840x2160x32, AVC
  Audio: 00:02:29,400, 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 22.0\FileIO Plug-Ins\so4compoundplug
  Format: AVC
  Version: Version 22.0 (Build 194)
  Company: MAGIX Computer Products Intl. Co.

Alright here is the info of a file I used to test with, it is not the 8 min video, but this one also crashes Vegas after I switch from the other video after playback to this one. Nevertheless both videos are done with the Nikon Z30.

While playing in the 'Video Preview' the VRAM use is growing to whopping 7.4Gb. But is pretty stable... Then generating the video also works nicely... (memory around 6.5Gb). Then if I open a new project the used memory does not drop. When I start playing the new project (no edits yet, just imported vegas 21 project files) then the memory creeps up from 6.4Gb to 8Gb and this time Vegas did catch the problem and send in a bug report. Most of the time Vegas is too late and simply crashes.

I think Yesterday I also had a You Tube video running which also requires GPU VRAM for playback. So probably that caused me to crash my system with only playback of one video.

@RogerS I did enable the Options -> Preferences -> File I/O -> Enable legacy AVC decoding. With that the VRAM memory use stays below 6Gb. I now opened the project which I also tested yesterday with two videos and memory use is 7.3/8.0 Gb but that is with Best(Auto) preview quality.. Switching to another project doesn't release any VRAM still 7.3Gb ot 7.4Gb.

Funny fact... when starting to render (I have 'Show video in Preview Window' disabled). Then the memory use drops from 7.4Gb to 4.4Gb.

I will be back with any updates if there are any. This legacy option makes VP22 more workable.

Update: after disabling the legacy option , playback of the 8 min video now creeps up to 7.8Gb and stays there. And when playing it through to the end it stopped playing at 7 minutes.Ending in a Vegas crash. Needed to kill the task in the Task Manager :-(

Thanks, it seems like a memory leak with the MxCompound decoder and this GPU.

When you start to render I believe it stops using the GPU to accelerate the preview (to avoid resource conflicts) so the vram drop makes sense.

Hopefully the VEGAS engineers and beta testers using AMD systems can use this to improve VP 22 in the next patch. In the meantime I'd probably stick with 21.208 (or legacy AVC in 22 if that remains stable).

@Solmea sent me the video clip. I was able to play it back without any problems with Preview set to Best>Full. I also split the clip into several parts, added cross dissolves of various lengths, and still performance was great.

As for GPU memory. My system was already using 2.1GB before starting Vegas. Dropping the video on the timeline, 3.0-3.1GB of GPU RAM is now used. Playback, GPU RAM increased to 9.8GB. Mind you, 2.1GB was already being used before starting Vegas Pro 22 B194. Even adding another instance of the video clip above, using Pan/Crop to zoom in and reduce the opacity, no RAM increase and playback was still 25fps.

Opening in VP21, GPU RAM had a slight increase to 10GB during timeline playback. With VP19, GPU RAM reached 6.9GB, rendering 5.7GB.

Rendering was fast using AMD VCE at the project settings and GPU RAM didn't increase. I found no real rendering speed difference between VP19, 21 and 22 using AMD VCE, about 69fps.

Insightful testing. I wonder if there's a significant difference whether the GPU is 8GB (OP) or 12GB (it should just cache out of system ram and be slower) but here it seems to cause stability issues which it shouldn't.

Thanks, it seems like a memory leak with the MxCompound decoder and this GPU.

When you start to render I believe it stops using the GPU to accelerate the preview (to avoid resource conflicts) so the vram drop makes sense.

Hopefully the VEGAS engineers and beta testers using AMD systems can use this to improve VP 22 in the next patch. In the meantime I'd probably stick with 21.208 (or legacy AVC in 22 if that remains stable).

I guess I will try the legacy option for some time and see if I am happy enough with that.. Otherwise I still have the VP21-208 as fallback. Oh and good to know: Reyfox tested a source file I send him in a direct message and on his system with a 12Gb VRAM card it used 9.7Gb. With a base use of 2.1Gb VRAM on his system it also typically used 7.6Gb of RAM. That means that apparently this much VRAM is required for 4k footage.

Do I need to report this issue specifically to help out the devs somewehere else?
 

If you set Dynamic Ram Preview to 0 maybe it will stop crashing due to there being more VRAM available for you project and less for caching. Shouldn't be happening though, should use your system ram if it runs out of VRAM.

Note this can affect timeline playback