Loading a different clip in Vegas -16GB,

Adding PI & opening it 30GB

Letting the clip loop play in PI (no emitters added) raised the RAM a bit 😉

Closing PI (still no emitters added) the RAM returned to 16GB

@Former user VP21 seems to be handling the "keeping the RAM" issue now.

@Reyfox ..

Ok... I watched the video. I haven't done what you did.... playing in the loop the video over and over in PI. I'll give it a shot and report back.

@Former user, I just did 7 passes of a UHD 4K 23.97P video that has 1238 frames in PI.

Opening Vegas project: 13.4GB

Open PI Browser: 24GB

1st play: 22GB

2nd play: 21.8Gb

3rd Play: 16.5GB

4th play:16.7GB

5th play: 16.9GB

6th and 7th play: 8.8GB

Exit PI (cancel) back to VP: 6.4GB

Delete fx in Video Event FX: 14.2GB

Close Video Event FX window: 13.4GB

Vegas finally settles down to 12.4GB

Not seeing the continual rise in RAM and Vegas holding on to it.

@Reyfox hmm 👍 I tried it on a small UHD file about 300frames, it stopped rising once it loop played once, & I tried with a larger file, the RAM rose but went away when returning to Vegas, 🤷‍♂️

For instance this is just 165frames, Vegas was already holding a little RAM from previous stuff before applying this vid + PI but it was only at 22GB, adding the file didn't really show in the RAM & opening PI only raised it to 30GB-ish, playing the clip rose it o 36GB but it stopped at that, smaller file but why it didn't continue to rise with each loop play I dunno.

A short UHD clip maxed out at 36GB

I use different types of media, the video above is a ProRes created by Vegas, they tend to be my 'go-to' files as they work best in Vegas, the picture below is an mp4, again created in Vegas. So I'll need to go through them & see if there's any difference between them,

This was interesting, rather then just switching windows from PI to Google for instance & letting PI continue playing in the background, I minimized the PI window, RAM immediately levelled off then continued rising after Maximising the PI window. Again the RAM disappeared when closing PI & returning to Vegas. 🤷‍♂️

@Former user Well, this is Continuum 2024, and VP21. Not sure what the difference to what would happen before with 2023.5 and VP20.

I'm good with it so far.

UPDATE -- not all is 100% well in Kansas.. welp, at least not with PI (Continuum 17.05) and Vegas 21.315

Created a new project, 1080p60. Added 65 titles, each with a PI effect on them, fade-in, transition out, tiny amount of pan/crop.

• Rendering without the PI effect: memory not significantly climbing during the render
• Rendering WITH the PI effect; memory use goes up about 1+ GB per title and it isn't released until Vegas is closed. With 32 GB of RAM and 65 titles -- well.. yup. No render for bonzo 😱

Tried with/without different video card use/settings in Vegas, with/without legacy decoding, with/without "enable OpenCL" in PI preferences menu -- nothing appears to affect this memory climbing behavior.

I realize this is 10-minutes long and probably not particularly exciting to watch, but I made a video demonstrating the problem. (Next time I promise to let Kermit D. Frog narrate)

I also copied a few of those title events into a Vegas 20 project and observed the render and RAM.. also seems to spike up continually, so this may not be a new VP21 problem -- wonder if a PI update is causing this?

@RedRob-CandlelightProdctns Hi, just did a quick test, forgot to change to 59.94 & every event is a duplicate so the same PI is on each. + no transitions,. RAM didn't change... I must say that is unexpected from past PI tests, (I'm Former User above)

I have Direct (Classic) as the Composite........?

I think you said something about it doesn't matter what PI is on each but I'll do it again later @ 59.94 with a different PI on each & a transition. Can you show a little more about your PI setup so we're the same 👍

@RedRob-CandlelightProdctns Hi, yep RAM increased,

• I created a FHD 59.94 project with 9 text events with a different PI emitter on each.
• Playing the timeline increased RAM to 44% before I got bored, playback was slow. (I have 256GB of RAM, 44% of 256 = 112.64)
• So I saved the project, closed Vegas to clear the RAM, reopened Vegas + that project, RAM started at 18%, I didn't play the timeline so as not to increase the RAM.
• Rendered using Magix AVC, RAM went up to 56% before I stopped render which was about 3/4 of the way through, 56% of 256 - 143.36 😱😂

Maybe you guys should post in the BorisFX forum about this?

@Reyfox 2 yrs ago https://forum.borisfx.com/t/pi-ram-usage/14377

@Gid maybe they need an update?

@Reyfox Poking with a stick 😏

@Gid always! Sometimes "we" forget things and need to be reminded.

@RedRob-CandlelightProdctns Hi, yep RAM increased,

• I created a FHD 59.94 project with 9 text events with a different PI emitter on each.
• Playing the timeline increased RAM to 44% before I got bored, playback was slow. (I have 256GB of RAM, 44% of 256 = 112.64)
• So I saved the project, closed Vegas to clear the RAM, reopened Vegas + that project, RAM started at 18%, I didn't play the timeline so as not to increase the RAM.
• Rendered using Magix AVC, RAM went up to 56% before I stopped render which was about 3/4 of the way through, 56% of 256 - 143.36 😱😂

I need to edit this but I can't, it's not % but actual GB of RAM, just me being dozy, either way I have seen PI use humongous amount as shown in my much earlier pics.

@Gid this is the type of information that Boris needs to help solve the RAM issue.

@Reyfox 👍 I wasn't going to remove information, I was just being a bit gormless & mixing up this no' (green blob under it) as percentage when the part of my brain that was asleep knew it was the actual RAM amount ie in GB 🤦‍♂️

@RedRob-CandlelightProdctns has posted on the Boris forum, I don't think he shared a link to this thread. Alan_Lorence has replied but I'm not sure what to make of it " For instance on my 32GB mac I only get “out of System Memory” error messages when PI is using 170GB+ of RAM (recently seen with a terrible memory leak while debugging)." .. I don't understand how you can get 170GB showing on a 32GB PC..🤯🤷‍♂️

Hey @Gidi Since you mentioned the missing cross-link to the Boris thread, here it is (same one you posted on earlier).

https://forum.borisfx.com/t/pi-ram-usage/14377