Dean
thanks a lot. Well this machine's got 1GB of memory and i've got the virtual memory set to go up to 3GB. Also it's a fairly beefy machin
P4 2.6GH
Radeon 9800 Pr
XP Hom
OK, i'll try and break it up and see in perf mon/task monitor how memory utilization is going and post back here
----- Dean Rowe [MS] wrote: ----
I suspect you're problems are being caused by the fact that the highe
profile will produce a video of a higher resolution. The 2.1Mbps setting
uses a frame size of 640x480, whereas the profile for 48kbps is jus
160x120. This means that we're going to use up more memory during th
rendering of the timeline, roughly 16 times as much if you count the numbe
of pixels i.e. (640 x 480) / (160 x 120). So although you may have a lot o
memory at the start of publish we'll start using it as the publish proceeds
We are planning to improve how MovieMaker uses memory in the future in case
like this when you have a lot of still images, but of course that doesn'
help you today. Here are a few suggestions in the meantime
1) Buy more memory :-
2) You could split the timeline into 2 with 300 images in each, render the
out to seperate files and then use MovieMaker to stitch them together
3) If you are only interested in photos, then Photostory may be a goo
alternative to MovieMaker for this kind of scenario. It's pretty cool
Here's the link if you want to check it out
http://www.microsoft.com/windows/plus/dme/photo.as
Hope this helps
Dean Row
This posting is provided "as is" with no warranties, and confers no rights
pvaman said:
I've brought in a bunch of images (say 600), i have no trouble saving as
movie as long as the bit rate is set to something like 50kpbs. Set it t
2.1Mbps and it 'has trouble saving'