Crop and sizing not working correctly

[Eric]

Okay issue #2 for the night. I am setting my crop to constrain 8x12 @ 300dpi. I'm getting files that are 13 3/4 x 9 1/8 wen opened in CS. I also have the set to limit 1.5 megs but all my uploads are coming up WAY over that. Up to 3.4 meg.  I really have no clue why this isn't working.

[Kirk Baker]

Okay issue #2 for the night. I am setting my crop to constrain 8x12 @ 300dpi. I'm getting files that are 13 3/4 x 9 1/8 wen opened in CS. I also have the set to limit 1.5 megs but all my uploads are coming up WAY over that. Up to 3.4 meg.  I really have no clue why this isn't working.

Please post a screen shot of your settings.

Use the 'Attachments and other options' link when you're composing your reply to this message and there you'll be able to upload your JPEG format screenshot.

Thanks,

-Kirk

[Eric]

Kirk I'll do that but it would appear that when PM5 installed it seriously 'broke' 4.6.9 as I can't FTP out of the old version. Hitting the send button does nothing and when I try to u/l to photoshelter from 4.6.9 now I get a mile long error msg pointing to ruby folders.

[Eric]

Is this what you need?

[attachment deleted by admin]

[Hayo Baan]

Try lowering minimum quality slider; that's the one causing the larger files. PM won't generate files of worse quality than that, even if the file size is too big. You can even set it to 0 as PM will then generate the highest possible quality while still retaining the file size limit you specified!

Hope this helps,
Hayo

[Eric]

Okay I'll try that to see if it fixes the file size... any idea why it won't constrain the crops though?

[Eric]

Nope..... Moving the slider to Zero setting the file size limit to 1.9 meg cropping to 8x12 @ 300 dpi resulted in a file that was 960kb  1442 x 962

[Eric]

Just to make sure I wasn't going nuts I opened the file in CS. Cropped it 8x12 @ 300dpi and saved it at level 9. Got a perfect 1.9meg file. So the math is doable.

[Kirk Baker]

Eric,

You're not telling PM to scale to inches.  You're telling it to scale to 100% of the cropped size.  Try changing the scaling to the middle choice (change the popup to inches afterwards) and then set the inches at 12 (your largest dimension).  Set the JPEG quality to 0, and limit to 1.9 MB.

As for your 4.6.9 issue, we have PM 4.6.x and PM 5 residing on the same systems all the time with no issues (though I haven't specifically tried the Photoshelter uploader).  The Photoshelter folks have taken over development of the Photoshelter uploader template so you'd have to take up the issue with them.

-Kirk

[Eric]

Kirk that fixed the cropping issue! Thank you!!!

The uploading is broken for both the standard FTP (I hit send but nothing happens) as well as the PS upload which gives back a huge error.  I'm going to spend the day working with PM5 to make sure that there aren't any other 'issues' before I go live with it tomorrow. Friday is a potential Ivy League title game so I don't have the luxury of not being able to file from the venue. Without 4.6.9 as a backup I have to make sure that everything in 5 is I would need/expect it to work.

Thanks again!

[Kirk Baker]

Eric,

Kirk that fixed the cropping issue! Thank you!!!

The uploading is broken for both the standard FTP (I hit send but nothing happens) as well as the PS upload which gives back a huge error.  I'm going to spend the day working with PM5 to make sure that there aren't any other 'issues' before I go live with it tomorrow. Friday is a potential Ivy League title game so I don't have the luxury of not being able to file from the venue. Without 4.6.9 as a backup I have to make sure that everything in 5 is I would need/expect it to work.

Thanks again!

If I had to guess what is going wrong is that the settings files (they're the only thing that is shared between the two versions) are incompatible and once they're updated by PM5, PM 4.6.9 is having trouble loading them.

Removing the connection settings files and then re-creating them in PM 4.6.9 should resolve the problem (if my hunch is right) and as long as you stick with PM 4.6.x, the problem won't return.

-Kirk

[Eric]

Thanks I'll look into that.... but in reality this is working 100% now so I may not need to revert to 4.6.9