I encountered this issue yesterday for the first time - after going wild with 65 small (1-5 frame each) adjustment events pasted on top of a main adjustment event to fix some specific issues that could not be key-framed or ducked away. The memory error arose about 75% through render. Many adjustment events is apparently a no-no. The video is only 9 minutes, which I had successfully rendered several times with only 5-6 adjustment events. So perhaps the issue is related not only to length of project, but number of adjustment events on the timeline?
Should I also file a bug report on this?
details: VP21 b208 on Win10. 32GB ram. Ram preview 15%. I was using Neat Video in adjustment events on one track (denoise plus dust and scratch removal), and color grading adjustment events on another track. The small adjustment events had the same Neat Video but with dust and scratch removal disabled, where fast-moving hands were disappearing -- (Neat Video does not support keyframe automation)).
@andyrpsmith @RogerS @j-v @Former user
I think i have found what is the problem. I have add adjusment event true all video (55min); then i receive mention problem when render.
Now i have remowe adjustment event and render is normal and i export whole video.
This is cool feature and i like it a lot but i dont know why cause such a problem !?
Can this be reported for fix ?
i was going to post the exact same problem today. its really been bothering me i am glad you found a temporary solution for it i really like the adjustment event feature i use it on almost every project i hope its fixed in the next update.
VEGAS has adjustment events and adjustment tracks. The problem I saw posts about is with events (which is new to 21).
The problem still exists in Vegas Pro 21 Build 300