[sbozkus]

(06-10-2015, 09:31 AM)Gary Wrote:

(06-09-2015, 06:03 PM)sbozkus Wrote: Petr, Gary's response was for me.

Gary, I believe you have enough explanation here to differentiate that; it's not the RAM it's not user's Windows. But it really points to how your standalone SW handles memory operations.
Hope that helps.

Hi Sbozkus

Yes and sorry I've got mixed up when Petr was replying to my reply to you. The problem is the code that runs during standalone for saving files is exactly the same code as runs when in the plug-in so I don't see how it could be due to a different way we are handling memory. In fact when run as a plug-in there is generally less memory available to Portrait Pro due to Photoshop using many resources including memory. When run as a plug-in the Portrait Pro code always saves a TIFF file. Can you try that to see if it works?

thanks
Gary

When it fails; it'll fail for any save option (tiff or jpg or png). At that time your standalone SW will freeze till you close it down with it's "X" corner.
If you restart and try again; it'll also fail.
But (as I mentioned before) if you fire your Photoshop and invoke PP plugin for same exact photo; it'll save every single time.
So although you may think that the code is exactly the same; obviously some form of difference do exist.