Re: Windows Movie maker taking too long to save project
> "Karanth" <Karanth@discussions.microsoft.com> wrote in message
> news:4E9803AE-660B-4FF3-B30F-4E5FCEE9EF9F@microsoft.com...
>> Windows Movie maker taking >10hrs to save a video of 45 minutes.
>> Cannot figure out the problem. Any help
>> --
>> Thanks
>
> I went thru similar a while ago.
> You have more patience than I did.
> I think consensus here was that WMM was not designed to handle that
> much data.
> I think for 9.95 hours of your 10 hours it was in never, neverland.
> ( I had no disk activity nor CPU time being used while mine was
> hanging.)
It does look that way when it's reading/writing and managing hte
pagefile or offputting a lot of the activity to the graphics card for
manipulation, whose cpu you don't get to see as a rule, plus a few other
things I've probably forgotten. Of course, it could have been hung
too<g>. Video rendering is one of the most machine intensive processes
you can run on a computer; it involves just about every resource the
computer has and still wants more. You have to keep in mind that it's
writing many megs large temporary files during the renders.
Another important thing a lot of people miss is that you often have
to do a defrag between renders. Rendering really fragments a hard drive
after as few as one rendering operation if it was more than say ten
minutes of video. Each successive render will get slower than the last
one due to the fragmentation of the drive. For near an hour and up to
two hours, the most I do, I have to defrag between each rendering
session. Fortunately I use a second disk drive for those operations so
it doesn't slow down other things on the system drive. You fragment the
system drive by just turning the stupid computer on, so it's fairly
important to offload as much of the rendering as possible toanother
drive. Preferably a second physical hard drive, but even just a
partitioned drive helps some.
I only use WMM for quickie stuff; for the bigger stuff I use Ulead's
apps. It takes a pretty competent machine to handle video rendering.
>
> After losing all of my work a few times, what I do now is set to
> autosave every X minutes, and even then while saving mine times out -
> I have to let it sit. OR kill process, reopen a while later and finds
> "unfinished" program and rebuilds.
> I DO like the process vs. store-bought apps - when it works, but
> wouldn't bet any money on it working 100% on any given day.
>
> I know no help - just wanted you to know " not your Pc/config" it is
> the app.