J
James
Sometimes WMM2 just stops responding. What would cause
this?
this?
You are using an out of date browser. It may not display this or other websites correctly.
You should upgrade or use an alternative browser.
You should upgrade or use an alternative browser.
P
PapaJohn \(MVP\)
Lots of times, it seems to stop responding because you can't do anything...
but it's doing some background process and isn't' really frozen. It just
isn't good about telling you what it's doing. Time will resolve it....
sometimes minutes to finish whatever it's working on. Giving it more
commands during this time will only make the situation worse, and might
cause it to freeze up.
But sometimes it hangs or freezes because of a codec or hardware
acceleration issue. Check the Problem Solving > Acceleration and Codecs page
of my website.
And at times it's hard to know which thing it is.... resolve any
codec/acceleration issue and then assume it's busy, at least for a couple
minutes.
And save and backup your work often if you have such issues.
--
PapaJohn
Movie Maker 2 - www.papajohn.org
Photo Story 2 - www.photostory.papajohn.org
..
but it's doing some background process and isn't' really frozen. It just
isn't good about telling you what it's doing. Time will resolve it....
sometimes minutes to finish whatever it's working on. Giving it more
commands during this time will only make the situation worse, and might
cause it to freeze up.
But sometimes it hangs or freezes because of a codec or hardware
acceleration issue. Check the Problem Solving > Acceleration and Codecs page
of my website.
And at times it's hard to know which thing it is.... resolve any
codec/acceleration issue and then assume it's busy, at least for a couple
minutes.
And save and backup your work often if you have such issues.
--
PapaJohn
Movie Maker 2 - www.papajohn.org
Photo Story 2 - www.photostory.papajohn.org
..
G
Graham Hughes, MVP Digital Media
If it's still open and running, just not responding, it could be that the
auto save function is turned on and is saving your work periodically. You
can turn this off. Does it start working again after a while? Also it may
help with more ram, but with no pc specs hard to say. Do regular hdd
maintainance, like defrag.
Graham
auto save function is turned on and is saving your work periodically. You
can turn this off. Does it start working again after a while? Also it may
help with more ram, but with no pc specs hard to say. Do regular hdd
maintainance, like defrag.
Graham
J
Just D
Hi,
I don't believe you. IPIV-3200HT, 1 BGytes RAM - is it too poor machine to
run this ... maker?-) It dies, it freezes up, it can refuse working any
moment... By the way, if I restrict any access from this WMM2 to a second
processor, it works a little bit better. If I use the whole power, it
returns that it can't read some memory address etc. The machine is ok, trust
me. I'm not a chicken as well, but a professional. The hard drive is 60
GBytes, defragmented, 7200 rpm, I think it's not so bad, the linear speed is
about 36 MBytes/sec and upper.
Any reason, trust me here. This applicatino has a lot of bugs and should be
debugged before we can use it efficiently. The idea is very nice, I like it
even more than other editors, but the code is wet yet. Anything can kill
this application, beginning from a "bad" from its point of view codec to a
weather on the Mars. We don't have any choice although yet.
Thanks,
Just D.
"Graham Hughes, MVP Digital Media"
I don't believe you. IPIV-3200HT, 1 BGytes RAM - is it too poor machine to
run this ... maker?-) It dies, it freezes up, it can refuse working any
moment... By the way, if I restrict any access from this WMM2 to a second
processor, it works a little bit better. If I use the whole power, it
returns that it can't read some memory address etc. The machine is ok, trust
me. I'm not a chicken as well, but a professional. The hard drive is 60
GBytes, defragmented, 7200 rpm, I think it's not so bad, the linear speed is
about 36 MBytes/sec and upper.
Any reason, trust me here. This applicatino has a lot of bugs and should be
debugged before we can use it efficiently. The idea is very nice, I like it
even more than other editors, but the code is wet yet. Anything can kill
this application, beginning from a "bad" from its point of view codec to a
weather on the Mars. We don't have any choice although yet.
Thanks,
Just D.
"Graham Hughes, MVP Digital Media"
J
John Kelly
Hello there,
I seem to remember reading somewhere that Movie Maker was NOT written with
multiple processors in mind. Therefore if you run it on such a machine you
have the risk of threads completing and being lost before they can be used.
In addition, I see you referring to your machine as HT. Hyper Threading
machines are known to have problems with programs that were not written
with that technology in mind. I did a search but without the name of the
manufacturer I can not find the machine you refer to (IPIV-3200HT). A few
weeks back I was with a chap who was telling me he had a dual processor
motherboard. In fact all he had was a HT enabled motherboard and
processor...he had been conned.
The error "can not read a memory address" indicates a conflict with memory
address in terms of threads completing and being destroyed, or, you are
running a memory program to free up memory (I have not yet seen one that
can always identify whether RAM should be cleared or not), or you have a
bad memory block. I used to run FreeMemPro until I got into video editing.
It screwed up every large project I worked on. I do not currently run it
and have never had the error message you refer to since.
I have 1.5GB of RAM which as far as Movie Maker is concerned is a total
overkill. Movie Maker never uses more than 540MB of ram on my system.
Of the two main video editing program I use, Movie Maker is the simplest in
terms of complexity of transition or effects and runs much quicker than
MovieDV 6 (A far more complex program) It has not been at all uncommon to
witness either program taking up to a day to complete a compiling of video
file.
If you are using the XP utility to defragment your system the bad news is
that it only defragment's files...it does NOT defragment the drive. This is
evidenced by observing the resulting graph at the end of its defrag run.
The out come is small pockets of free space on the drive thereby making the
heads work harder when jumping from one free sector to the next. If your
hard drive does not have a largish internal ram set, you end up with a
potential bottleneck. The drive I use for video capture and editing has its
own Ultra/ATA PCI card and has an internal DDR RAM set of 8MB. My other
drives have 4MB and once in a while caused glitches in the capture editing
process. That's why I took the steps of buying a faster hard drive and a
PCI card just for the one drive.
It is in any case a bad idea to run any video editor with just one drive as
the program will always be demanding access to the location the file is
being written to whilst the OS will be demanding access at the same time to
its system files, temporary files and the page file. This causes an obvious
conflict that will potentially slow the process down by up to 50% or more
(Depends greatly on which process is being used at any one time)
You mention the speed of your hard drive. I have just had a look at the box
that held my newest drive (Still not thrown it out) Its external transfer
rate is 133MB/s. Therefore the internal rate must be at least that fast.
This would indicate the speed you mention of 36MB/s is a bit slow in
comparison and that alone might cause problems.
At the end of the day, Movie Maker 2 is worth a hell of a lot more than
what we all paid for it, which was nothing. At that price, it is very much
better than most if not all of its rival programs.
--
Best Wishes.....John Kelly
www.the-kellys.org
www.the-kellys.co.uk
All material gained from other sources is duly acknowledged. No Value is
obtained by publishing in any format other peoples work
I seem to remember reading somewhere that Movie Maker was NOT written with
multiple processors in mind. Therefore if you run it on such a machine you
have the risk of threads completing and being lost before they can be used.
In addition, I see you referring to your machine as HT. Hyper Threading
machines are known to have problems with programs that were not written
with that technology in mind. I did a search but without the name of the
manufacturer I can not find the machine you refer to (IPIV-3200HT). A few
weeks back I was with a chap who was telling me he had a dual processor
motherboard. In fact all he had was a HT enabled motherboard and
processor...he had been conned.
The error "can not read a memory address" indicates a conflict with memory
address in terms of threads completing and being destroyed, or, you are
running a memory program to free up memory (I have not yet seen one that
can always identify whether RAM should be cleared or not), or you have a
bad memory block. I used to run FreeMemPro until I got into video editing.
It screwed up every large project I worked on. I do not currently run it
and have never had the error message you refer to since.
I have 1.5GB of RAM which as far as Movie Maker is concerned is a total
overkill. Movie Maker never uses more than 540MB of ram on my system.
Of the two main video editing program I use, Movie Maker is the simplest in
terms of complexity of transition or effects and runs much quicker than
MovieDV 6 (A far more complex program) It has not been at all uncommon to
witness either program taking up to a day to complete a compiling of video
file.
If you are using the XP utility to defragment your system the bad news is
that it only defragment's files...it does NOT defragment the drive. This is
evidenced by observing the resulting graph at the end of its defrag run.
The out come is small pockets of free space on the drive thereby making the
heads work harder when jumping from one free sector to the next. If your
hard drive does not have a largish internal ram set, you end up with a
potential bottleneck. The drive I use for video capture and editing has its
own Ultra/ATA PCI card and has an internal DDR RAM set of 8MB. My other
drives have 4MB and once in a while caused glitches in the capture editing
process. That's why I took the steps of buying a faster hard drive and a
PCI card just for the one drive.
It is in any case a bad idea to run any video editor with just one drive as
the program will always be demanding access to the location the file is
being written to whilst the OS will be demanding access at the same time to
its system files, temporary files and the page file. This causes an obvious
conflict that will potentially slow the process down by up to 50% or more
(Depends greatly on which process is being used at any one time)
You mention the speed of your hard drive. I have just had a look at the box
that held my newest drive (Still not thrown it out) Its external transfer
rate is 133MB/s. Therefore the internal rate must be at least that fast.
This would indicate the speed you mention of 36MB/s is a bit slow in
comparison and that alone might cause problems.
At the end of the day, Movie Maker 2 is worth a hell of a lot more than
what we all paid for it, which was nothing. At that price, it is very much
better than most if not all of its rival programs.
--
Best Wishes.....John Kelly
www.the-kellys.org
www.the-kellys.co.uk
All material gained from other sources is duly acknowledged. No Value is
obtained by publishing in any format other peoples work
G
Guest
I have been experimenting with the Movie Maker 2 and have had it lock up
from time to time. The bigger the project, the slower the Movie Maker
responds. If you edit the beginning of the timeline, the longer it takes for
it to shift everything for the changes you made. Especially if you are mixing
photos with videos and different quality of videos. I've learned to live with
the lockups and constantly save the project as I'm working on it. Changing
the autosave time helps but is built in for a reason and will restore the
project if a problems occurs. The program never stops amazing me and has
taught me a lot about video editing. I've had my best end results by
disconnecting my DSL connection and not asking the program to download codec
automatically and then save the movie to my computer. Sometimes I will lock
up just because of the fact it's trying to get a codec and can't get it in
time for the next needed codec. It does help to have seperate hard drives for
your project data and you operating system. I use ATA 133 PCI RAID 0 just for
fast data for making movies. So basically, it's a program limited by your
resources and patients.
from time to time. The bigger the project, the slower the Movie Maker
responds. If you edit the beginning of the timeline, the longer it takes for
it to shift everything for the changes you made. Especially if you are mixing
photos with videos and different quality of videos. I've learned to live with
the lockups and constantly save the project as I'm working on it. Changing
the autosave time helps but is built in for a reason and will restore the
project if a problems occurs. The program never stops amazing me and has
taught me a lot about video editing. I've had my best end results by
disconnecting my DSL connection and not asking the program to download codec
automatically and then save the movie to my computer. Sometimes I will lock
up just because of the fact it's trying to get a codec and can't get it in
time for the next needed codec. It does help to have seperate hard drives for
your project data and you operating system. I use ATA 133 PCI RAID 0 just for
fast data for making movies. So basically, it's a program limited by your
resources and patients.
G
Guest
Graham Hughes said:If it's still open and running, just not responding, it could be that the
auto save function is turned on and is saving your work periodically. You
can turn this off. Does it start working again after a while? Also it may
help with more ram, but with no pc specs hard to say. Do regular hdd
maintainance, like defrag.
Graham