Service Pack has not fixed this for me.

... it seems there may be some new behavior in its interaction between dpi and picture dimensions ...
wds937 wrote:... it seems there may be some new behavior in its interaction between dpi and picture dimensions ...
I have had a little more time to play with this, and it looks as though the behavior is the same as it was in X4 prior to SP1.
For example, one of my tests was with a photo I had cropped to 6" x 4" at 300 dpi, using PSP X4 (prior to SP1). I verified in Windows Explorer and other non-PSP applications that this photo is still 6" x 4" at 300 dpi. Opening this photo in PSP X4 (after SP1) shows it to be 25" x 16.667" at 72 dpi. Doing the math shows I haven't really lost anything, from a total pixels perspective, but anything that relies on the dpi setting will be incorrect. Opening this same photo in PSP X3 and earlier (back to PSP 8 ) works correctly.
39_Steps wrote:. . . .I just bought and installed PSP X4 yesterday (Nov 2011) without a trial, so I'm trying to get used to black on black (never happen) while reading the posts on this forum.
The "72 dpi" issue came up on the PhotoImpact forum around the time of the release of PI X3, IIRC. I delved into it because numbers interest me more than pictures. Seems like Adobe didn't necessarily get the dpi right in its metadata (whatever right is when refering to dpi), but PhotoImpact might just erase the metadata containing dpi if you weren't careful.
PSP X4 users with dpi concerns might want to search the PhotoImpact forum on the subject, circa 2008.


LeviFiction wrote:The inch size is calculated, not reported. That's how some products report in cm or mm. So it is not resizing. It is reporting and saving the incorrect dpi(ppi) value. This is an annoyance but it doesn't change the actual image itself and most printers or printing applications let you set the dpi(ppi) of the image you're printing and don't restrict you to what PSP says it should be so it doesn't harm anything. It's an annoyance that needs to be fixed, yes, but not much beyond that.

df wrote:SP1 has fixed this for me. Maybe SP2 (if there is an SP2) can fix this for everyone else as well?
Users browsing this forum: No registered users and 4 guests