I had just finised printing the multiple AVIs rendered from a veg-full-o'-stills and decided to try the whole nested original project again because...well, I have no idea why I wanted to try again.

Anyway, I opened vegas and it was sitting there empty while I cleaned up some other stuff and I get this system message that my virtual memory was low but not ot worry since Windows was going to make it all good for me.

I'd gotten this message previously while Vegas was doing something memory-intensive, but since there was nothing going on at this time, I found it curious.

So I opened Task Manager, poked around, found I could have it display Virtual Memory, so I did. As I watched, Virtual memory climbed up to over a million kb--still with nothing whatsoever going on in Vegas.

This seemed like a good omen so I quickly loaded my big Veg-full-o'-stills and set the whole, hour-long thing to rendering. (keeping in mind that I'd tried this same thing a week or 2 ago as Task Manager showed Mem Usage steadily creep up to over 900,000 KB and I'd lock up Repeatedly.)

this time, Mem Use goes up to about 750,000, then levels out and by the end of the render (!!!!!!!!) it was down around 500,000. The Virtual memory was still up over a million kb.

since I 'd never watched virtual memory during a render, I don't know if this is germaine, but Vegas rendering this whole project is sure as hell new.

I may be grasping at straws, but I figured I'd report it here in case it means anything to those familiar with Virtual memory.

best to all