If you have Windows XP, you can check your values by bringing up Task Manager. Do a Ctrl/Alt/Delete.
I'm working on a short clip (about 12 minutes) that was of very low quality with lots of noise and artifacts. While the Median filter does a decent job of removing almost all of it, the rendering process is incredibly slow using the default DVD template. I started yesterday, twenty hours into the render it is only 31% of the way through, so it looks like it is going to take around 65 hours to render 12 minutes on a comparatively fast AMD 1900+ with 512 RAM PC. I have several other filters applied also, but only a single video and audio track.
Just got me wondering how hard Vegas Video was working.
By looking in Task Manager you can get some idea. Right now there have been 16,358,813,204 bytes read. So by the time it is finished it will have read somewhere in the neighborhood of 48 billion bytes! So obviously a lot of pixels are being moved around. What struck me was what seems like a extremely high number of Page Faults. So far 1,132,168! This term as it applies here is different than the old blue screen errors which resulted in a system crash. According to Microsoft, the term just means an interrupt occured when Vegas attempted to make a read or write to a Virtual Memory location that was marked not present. This is what I find strange.
Looking under the Performance Tab in Task Manager I see the Commit Charge has peaked at only 365396, the total is just 272716 with the limit at 1280468. Under Physical Memory total is 523760 with available at 202800 and system cache at 32400. Numbers are not extact, since I'm reading them in real time and they keep changing sligly.
My question is with ample resources, why are there so many page faults (trips out to the hard drive) which seems to be contributing to slowing things way down.
Also wondering if SoFo can comment on if disabling the preview window prior to doing a complex render with lots of filters or those that are very slow has any signifcant impact on how long it takes.
I'm working on a short clip (about 12 minutes) that was of very low quality with lots of noise and artifacts. While the Median filter does a decent job of removing almost all of it, the rendering process is incredibly slow using the default DVD template. I started yesterday, twenty hours into the render it is only 31% of the way through, so it looks like it is going to take around 65 hours to render 12 minutes on a comparatively fast AMD 1900+ with 512 RAM PC. I have several other filters applied also, but only a single video and audio track.
Just got me wondering how hard Vegas Video was working.
By looking in Task Manager you can get some idea. Right now there have been 16,358,813,204 bytes read. So by the time it is finished it will have read somewhere in the neighborhood of 48 billion bytes! So obviously a lot of pixels are being moved around. What struck me was what seems like a extremely high number of Page Faults. So far 1,132,168! This term as it applies here is different than the old blue screen errors which resulted in a system crash. According to Microsoft, the term just means an interrupt occured when Vegas attempted to make a read or write to a Virtual Memory location that was marked not present. This is what I find strange.
Looking under the Performance Tab in Task Manager I see the Commit Charge has peaked at only 365396, the total is just 272716 with the limit at 1280468. Under Physical Memory total is 523760 with available at 202800 and system cache at 32400. Numbers are not extact, since I'm reading them in real time and they keep changing sligly.
My question is with ample resources, why are there so many page faults (trips out to the hard drive) which seems to be contributing to slowing things way down.
Also wondering if SoFo can comment on if disabling the preview window prior to doing a complex render with lots of filters or those that are very slow has any signifcant impact on how long it takes.