|
|
I've just spent hours on a wild goose chase with the error message "Not enough system memory".
Running Power Director 8.00.3022 on XP SP3, I am trying to create a quick 10 minute clip. Just a video track, 4 PiP's on one track, 8 titles, a background music track and a narrative.
Nothing elaborate. What caught me right at the beginning was that after putting together the video track, I could not manipulate the PiP elements. As soon as I touched them, PowerDirector would freeze. No message, just "not responding". No mentioning in the XP event viewer either.
Playing the finished clip gave me a "Not enough system memory" error, which I ignored, as it played the next time. After restarting Power Director and the PC a few times I managed to finish the video editing.
Producing failed. But I did not know why. So I selected a low res format and noticed it crashed with a Not enough .... error.
I installed PowerDirector on my laptop, copied everything across and the very same, identical thing happened. Not enough system memory. I now put the video camera in front of the screen and tried producing various formats.
That's when I noticed that it always crashed at 6:02 with a Not enough .... error. I moved some scenes around and now it crashed at 6:11. So I deleted the video scene at 6:11 and it went through without a hitch.
So none of the crashes had anything to do with system resources but an mp4 file of 3 minutes and 11MB that PowerDirector simply did not like. The file came off YouTube, a standard file like I've used them endless times before.
So it seems that a file rendering crash has an inaccurate failure message attached.
Oh and after deleting the clip I was also able to edit the PiP parameters of the one that caused the freezing of PowerDirector. Strange.
But I hope this helps some others who are baffled by the behaviour of PowerDirector.
|
|
|
Wow! Now that is what I call a detailed work-around.
Thanks a stack for this info. I will remember this and apply next time I have this problem. Better than fiddling with adjustments when removing the clip completely!!!!
|
|
|
Because I am trying to make up my mind which package to buy I am trying out PowerDirector 8 trial.
Yes, it crashes occasionally. Yes it has problems with loading media. Yes, it sometimes doesn't load. Yes, it has irritating shortfalls. But overall, when it works, it's fun to work with.
After spending a couple of days putting together a 10-minute clip, I wanted to output an mp4 file to watch the finished product. It always got stuck after 1 minute. After reading here, I pinpointed the culprit, a short clip, removed it, spent another day adjusting the remainder clips and audio and now it went through all the way.
My questions:
How can I determine what is wrong with this clip, which was produced by the clip-detect function within PowerDirector?
How can I avoid future hiccups such as this?
How can I identify future rogue clips that will prevent an output file from being created?
Thanks for any pointers.
StopS
|
|
|
