Well, i got the Insufficient Memory bug too!
I got PI 12, Vista, 4 GB RAM, all the patches for Vista and the PI12 patch.
I noticed the error if i use any PATH OBJECT and i try to align it with the righ-click menu voice.
I just discovered that if i merge the shape into a single object, i can align that image.
Unfortunately u will lose some effects...
I don't understand why there's a new patch after months...
I bought PI7, then PI8, then PI12 (cause with the previous releases i got troubles with the insufficient memory 10x than with PI12), but i don't know if i'll upgrade to PI13 if this bug will remains...
Insufficent Memory in PI
-
heinz-oz
Well, I have a laptop, running XP Pro SP2, PI 10 and 12 installed, 512 MB RAM and I don't have this problem here. I also don't have it at home on my other two machines, all XP Pro SP2 but 1 GB and 2 GB respective RAM.
It can't be only PI's fault. Sure, the code may not be written in the most effective manner, making it a bit temperamental on some machines, but there must be something machine specific that's causing this also.
Often the order in which programs are installed has a bearing also.
I know this doesn't help but bashing PI for every little problem can't be too helpful either. I had no problem with PI 10, memory problems galore with PI 11 but PI 12 again runs very well for me and that on three different machines.
After installing PI 11 I began to have problems with PI 10 also. Removing PI 11 did not "repair" PI 10, the problem remained. After a lot of trying and finally rebuilding my machine, both PI versions worked side by side but PI 11 had this memory problem always. Than, one day, I realised that I forgot to install DVD MovieFactory 3. After installing that my PI 10 installation played up again. The same symptoms I had previously. Removing MF 3 fixed the issue again and an upgrade to DVD MF 4+ allowed both PI versions to work satisfactorily, except for the memory problem in PI 11. Now I'm on MF 5+ on 2 machines and still on MF 4+ on the other. PI 11 got canned because of it's terrible memory leak but PI 10 and 12 work fine on all my machines.
It can't be only PI's fault. Sure, the code may not be written in the most effective manner, making it a bit temperamental on some machines, but there must be something machine specific that's causing this also.
Often the order in which programs are installed has a bearing also.
I know this doesn't help but bashing PI for every little problem can't be too helpful either. I had no problem with PI 10, memory problems galore with PI 11 but PI 12 again runs very well for me and that on three different machines.
After installing PI 11 I began to have problems with PI 10 also. Removing PI 11 did not "repair" PI 10, the problem remained. After a lot of trying and finally rebuilding my machine, both PI versions worked side by side but PI 11 had this memory problem always. Than, one day, I realised that I forgot to install DVD MovieFactory 3. After installing that my PI 10 installation played up again. The same symptoms I had previously. Removing MF 3 fixed the issue again and an upgrade to DVD MF 4+ allowed both PI versions to work satisfactorily, except for the memory problem in PI 11. Now I'm on MF 5+ on 2 machines and still on MF 4+ on the other. PI 11 got canned because of it's terrible memory leak but PI 10 and 12 work fine on all my machines.
-
hwcowan
I just registered for this user forum because I am having similar problems with PI12. I did not enter my system data yet, but I am running a Dell Latitude D800 (laptop), 1.4Ghz Pentium M with 1Gb of memory and have about 20Gb free on my hard drive. O/S is XP Pro SP2.
Heinz, having done tech support for more years that I want to admit, I will give you some credit for "It can't be only PI's fault.", but the bottom line for me is that I just a few days ago upgraded from PI10, which was working fine for what I needed it to do, and now I can't do something as basic as resize a photo without running out of memory. When I tried Perspective Crop, the delays (hour glasses) were such as to make the product unusable.
Looking at Task Manager in XP Pro, and the process Iedit (part of PhotoImpact) is taking up a minimum of 20-40% of my CPU, and I am doing nothing and have done nothing for over 1 hour. The Pick Tool is selected. What the heck is spinning in Iedit to take up that amount of CPU?
I have work to get done, and frankly I am thinking of ditching PhotoImpact because of this.
Heinz, having done tech support for more years that I want to admit, I will give you some credit for "It can't be only PI's fault.", but the bottom line for me is that I just a few days ago upgraded from PI10, which was working fine for what I needed it to do, and now I can't do something as basic as resize a photo without running out of memory. When I tried Perspective Crop, the delays (hour glasses) were such as to make the product unusable.
Looking at Task Manager in XP Pro, and the process Iedit (part of PhotoImpact) is taking up a minimum of 20-40% of my CPU, and I am doing nothing and have done nothing for over 1 hour. The Pick Tool is selected. What the heck is spinning in Iedit to take up that amount of CPU?
I have work to get done, and frankly I am thinking of ditching PhotoImpact because of this.
-
heinz-oz
If I had your problems I would do the same 
Luckily all my PI installations must be faulty because they work as expected.
The problem, as I see it, is the multitude of hardware/software mixes out there. There is virtually no chance out there that any two of the systems used by the users on this forum are identical. Ulead programs are rather sensitive to their software/hardware environments and have proven to be virtually impossible to use on some systems while on others they work well.
They are still the best bang for your buck if they do work on your machine. If they don't... hmmm
Luckily all my PI installations must be faulty because they work as expected.The problem, as I see it, is the multitude of hardware/software mixes out there. There is virtually no chance out there that any two of the systems used by the users on this forum are identical. Ulead programs are rather sensitive to their software/hardware environments and have proven to be virtually impossible to use on some systems while on others they work well.
They are still the best bang for your buck if they do work on your machine. If they don't... hmmm
-
hwcowan
Heinz,
You are right. I spent 12 years in a homogeneous environment (UNIX) and was spoiled by the ease (yeah, right) of debugging problems, relatively so, anyway.
The Windows-with-every-hacked-machine/software-combo-under-the-sun environment is going to have unique, frustrating, and maybe unsolvable (?) problems. Maybe if I knew Windows as much as I know UNIX it would help.
I am just frustrated, but at least I didn't pay $500-$1000USD on something that doesn't want to work as opposed to $50.
I'll use the still installed PI10 until I can take time to look at this again.
(btw: PI10 Iedit still takes a chunk of the cpu, but at least it works better in other ways. Another data point.)
Thanks,
You are right. I spent 12 years in a homogeneous environment (UNIX) and was spoiled by the ease (yeah, right) of debugging problems, relatively so, anyway.
The Windows-with-every-hacked-machine/software-combo-under-the-sun environment is going to have unique, frustrating, and maybe unsolvable (?) problems. Maybe if I knew Windows as much as I know UNIX it would help.
I am just frustrated, but at least I didn't pay $500-$1000USD on something that doesn't want to work as opposed to $50.
I'll use the still installed PI10 until I can take time to look at this again.
(btw: PI10 Iedit still takes a chunk of the cpu, but at least it works better in other ways. Another data point.)
Thanks,
-
RenderWarrior
Do u mean the path object/memory issue?heinz-oz wrote:Well, I have a laptop, running XP Pro SP2, PI 10 and 12 installed, 512 MB RAM and I don't have this problem here.
Maybe it's Vista, but so, why say "Works with Vista" if there are bugs.
I'm sorry, but i don't think it's a Vista issue.
Vista is different from XP, so i think the developers needs to patch PI to correct the memory bug with this OS.
I noticed there's a coming PI X3... I bought PI12 1 month ago... do u think there would be a free upgrade or i'll have to pay the full price for the upgrade?
-
RenderWarrior
-
TomMeeks
Having used PhotoImpact since version 4, I can chime in with DEFINITE opinion that version 12 has some serious memory problems that were not found in 4-10. (I didn't even bother with Version 11)
This is a show stopper as far as I'm concerned. I might be forced to get serious about learning Photoshop.
This is a show stopper as far as I'm concerned. I might be forced to get serious about learning Photoshop.
-
iq
Possible Solution to Memeory Issues
Hi All,
I encountered this issue once, a while back, using 3d Studio. Observing that I had enough free RAM and wasn't running out of Swap space. I pondered what would cause this issue. I know when large blocks of RAM are needed (I'm sure PI needs large blocks of RAM) sometimes Swap space is allocated as a result of the RAM allocation. Surmising that the request for RAM may fail if a large enough contigeous block of Swap wasn't available I decied to defrag. Viola, problem gone. Don't know if it'll work for you all, but worth a try. The standard XP defrag won't defrag your Swap space. If you have two drives you can move the Swap to the second drive (non-system) and defrag the system disk. Then move your Swap file back and set it to a fixed size (typically 1.5 - 2 times the amount of RAM). Set the initial size and the ending size to be the same. This will prevent if from becoming fragmented again.
Hope this helps,
--IQ
I encountered this issue once, a while back, using 3d Studio. Observing that I had enough free RAM and wasn't running out of Swap space. I pondered what would cause this issue. I know when large blocks of RAM are needed (I'm sure PI needs large blocks of RAM) sometimes Swap space is allocated as a result of the RAM allocation. Surmising that the request for RAM may fail if a large enough contigeous block of Swap wasn't available I decied to defrag. Viola, problem gone. Don't know if it'll work for you all, but worth a try. The standard XP defrag won't defrag your Swap space. If you have two drives you can move the Swap to the second drive (non-system) and defrag the system disk. Then move your Swap file back and set it to a fixed size (typically 1.5 - 2 times the amount of RAM). Set the initial size and the ending size to be the same. This will prevent if from becoming fragmented again.
Hope this helps,
--IQ
-
wolverine
I've used PI11 and it is the bomb. I'm afraid to upgrade to 12 b/c I'm afraid something will go kaput. So I'm sticking with it until the next version comes out, which I hope has a better handle on working with large, large files.
In regards insufficient memory it happens on my system in two cases. The first working on and creating files where the long side of the image is greater than 30x40 inches at 300dpi. The problem is in PI's ability to utilize its file buffer seems to be the problem. Effectively the largest file, at photo quality I can work on is, 16x20 without problems.
The second instance is while creating a file and using a lot of edits. When I get the Insufficient Edit message I simply save the file and then clear the UNdo/Redo history. This frees up memory and allows you to continue working on the file. Usually, I'll save it again after I make the edit that caused the error since I work with UFO files and close the program. When I reopen PI things are back to peachy. You might want to try this the next time you get the IMWM.
In regards insufficient memory it happens on my system in two cases. The first working on and creating files where the long side of the image is greater than 30x40 inches at 300dpi. The problem is in PI's ability to utilize its file buffer seems to be the problem. Effectively the largest file, at photo quality I can work on is, 16x20 without problems.
The second instance is while creating a file and using a lot of edits. When I get the Insufficient Edit message I simply save the file and then clear the UNdo/Redo history. This frees up memory and allows you to continue working on the file. Usually, I'll save it again after I make the edit that caused the error since I work with UFO files and close the program. When I reopen PI things are back to peachy. You might want to try this the next time you get the IMWM.
-
heinz-oz
With PI 11 I got into the habit of saving a large image after each action. That was the only way not to lose any work. I also closed and re-opened PI frequently in order to free up memory locked by PI.
With PI 12 I do not have any of the issues you describe. The hardware didn't change.
PI 10 was good, PI 11 the pits but PI 12 is the best of all of them for me.
With PI 12 I do not have any of the issues you describe. The hardware didn't change.
PI 10 was good, PI 11 the pits but PI 12 is the best of all of them for me.
-
heinz-oz
You are having your wires crossed somewhere. It doesn't matter what print resolution (dpi) you work on in PI. Change your resolution to 76 dpi and watch how much the file size changeswolverine wrote:...
In regards insufficient memory it happens on my system in two cases. The first working on and creating files where the long side of the image is greater than 30x40 inches at 300dpi. The problem is in PI's ability to utilize its file buffer seems to be the problem. Effectively the largest file, at photo quality I can work on is, 16x20 without problems.
......
What matters in this respect is the file size, nothing else. Also, while in PI, your image does not have a size in inches or mm or cm or meters or whatever measurement you prefer. That aspect only comes into it when you print. The physical size of your print is in direct relation to the image size in px times px and the print resolution in dpi.
What is your image size when you have the problem and what is it when you don't? I guess what you are referring to is the image size in ppi (pixel per inch) of intended output. If you want to have a source image of 30 x 40 inches and have 300 ppi, your image size would be 9000 x 12000 pixels. That is humongous. Can you even print that large or do you have it printed by a professional?
-
wolverine
Humongous...LOL...not really.wolverine wrote:...That is humongous. Can you even print that large or do you have it printed by a professional?
The widest I can print is 26 inches by 50 feet. PI could handle that anyway. Yes, I have both a service provider and a photo lab that easily prints those dimensions.
Last edited by wolverine on Wed Nov 21, 2007 1:01 am, edited 1 time in total.
-
wolverine
You are having your wires crossed somewhere. It doesn't matter what print resolution (dpi) you work on in PI. Change your resolution to 76 dpi and watch how much the file size changesheinz-oz wrote:wolverine wrote:...
In regards insufficient memory it happens on my system in two cases. The first working on and creating files where the long side of the image is greater than 30x40 inches at 300dpi. The problem is in PI's ability to utilize its file buffer seems to be the problem. Effectively the largest file, at photo quality I can work on is, 16x20 without problems.
......
/quote]We both do because the real issue is P11 (and 10) are limited on the amount of data it can handle to do manipulations with. The file dimension do matter only in terms of the amount of data it takes to create the image. A 72 dpi file at 4x6 for example contains significantly less data than same file dimensions at 300 dpi.
-
wolverine