K
Kenneth Hayashida
Given the number of problems reported in this community
newsgroup, I'm a bit irritated that I downloaded and
updated to the "new" version of MovieMaker.
The older version permitted me to do at least basic
editing and to output the film to an AVI file for burning
to DVD.
Here's what we've seen today.
After spending six hours as a family attempting to get a
home video into the WindowsXP Media Center box and edit
it to DVD, we have had MovieMaker crash at every attempt
to run it in the last four hours.
I genuinely believe that the code is defective. I do not
have DIVX installed, updated our box's anti-viral library
and scanned the application and directories, yet I find
that the application (even after shutting down) is
consuming 40+ Megs of system RAM. Using the three finger
salute, I accessed the processes tab and found that
although the Movie Maker application was no longer
running, the RAM was allocating increasing amounts of
space to Movie Maker.
When we ran MovieMaker, we ended up seeing the
application work for a few seconds, freeze upon play back
of the initial selection, and then fail.
There is a major problem with this application and I wish
I never used it. I would have been better off just using
the 1.0 version.
MSFT needs to fix the problems with this application.
newsgroup, I'm a bit irritated that I downloaded and
updated to the "new" version of MovieMaker.
The older version permitted me to do at least basic
editing and to output the film to an AVI file for burning
to DVD.
Here's what we've seen today.
After spending six hours as a family attempting to get a
home video into the WindowsXP Media Center box and edit
it to DVD, we have had MovieMaker crash at every attempt
to run it in the last four hours.
I genuinely believe that the code is defective. I do not
have DIVX installed, updated our box's anti-viral library
and scanned the application and directories, yet I find
that the application (even after shutting down) is
consuming 40+ Megs of system RAM. Using the three finger
salute, I accessed the processes tab and found that
although the Movie Maker application was no longer
running, the RAM was allocating increasing amounts of
space to Movie Maker.
When we ran MovieMaker, we ended up seeing the
application work for a few seconds, freeze upon play back
of the initial selection, and then fail.
There is a major problem with this application and I wish
I never used it. I would have been better off just using
the 1.0 version.
MSFT needs to fix the problems with this application.