I've been using ZenPhotoPress plug-in for WordPress. And now I'm also making some calls myself by simply inserting code something like this:

`http://www.stanats.com/gal01/zp-core/i.php?a=first-month&i=47.jpg&s=250`

I've noticed, however, that the images called by ZenPhotoPress are sharper than the ones I'm calling directly.

For example, compare the pic above to one called by ZenPhotoPress:
`http://www.stanats.com/gal01/cache/first-month/47.jpg_200_cw200_ch150_cy20.jpg`

How is ZenPhotoPress sharpening the images and iss there a way to sharpen the images I'm calling?

Not familiar with ZenphotoPress but with the recent nightly build there is an option on the admin to set the amount of sharpening.

sorry... i'm not quite sure what you mean. i've uploaded the most recent nightly. where would i find this option?

and can it be applied to specific images?

That is on the admin option's image tab. And no, it's only a general option.

okay, thanks. i am familiar with this setting, but now i see that we have greater control over the parameters, which is excellent.

so here's a follow up question:

i have it set to sharpen thumbs, but not the main image. is it possible, when calling an image, to designate it as a thumb instead of a main image? basically, since i'm pulling smaller versions of my images into a blog, if there was some way to make ZP think those images were thumbs (even though i am using different size parameters at different times), then they would get sharpened like thumbs. that would work great i think.

Yes, you can set the parameter `t` to TRUE if you call via url (there is also a similar parameter for some customimage functions).

YES! Awesome. That works great.

It does beg an interesting question, however.

If I call it the old way first (without setting t=TRUE), then a cached image is created that is not sharpened. Then all calls to that image with the same s/w/h/cw/ch/cx/cy parameter settings access the same cached image (whether t=TRUE or not).

If I delete that cached image, then first call it the new way (with t=TRUE), then the cached image that is created IS sharpened. And all subsequent calls (with t=TRUE or not) access the sharpened image in the cache.

In other words, there is nothing in the nomenclature for cached images that indicates whether the cached image is sharpened or not, or perhaps more accurately, whether the image is a thumb or not. I think this is true for the q (quality) parameter as well.