Looks like no one’s replied in a while. To start the conversation again, simply ask a new question.

Prevent "scale image: fit within" from upscaling image on export?

I exported a bunch of images of different sizes using an export preset with "Size to: Fit Within (Pixels):" a 960x960 square and I was surprised that some of the images that I'd manually scaled (using "Edit with Gimp") to 720px[1] were UPSCALED to 960px.


This was not what I expected: since upscaling an image can never result in an image of better quality I couldn't image why anyone would want to do such a thing (at least until I came on here and discovered that apparently people want to do this to satisfy stupid stock agency requirements for minimum file sizes!)


Is it possible to create an export preset which will only ever *reduce* the size of an image to fit within the specified rectangle - never *increase* it? Or the reverse, for those who have to deal with the stock agencies?



--------

[1] If I have a photo that is slightly out-of-focus but otherwise really nice I will sometimes manually scale to 720x or so and then use Wavelet Sharpen to produce a good-enough-for-Facebook image. After all, why throw away a great shot that's only going to be seen at a small size anyway?

Aperture 3, Mac OS X (10.6.8)

Posted on Nov 2, 2011 4:17 AM

Reply
10 replies

Nov 2, 2011 5:30 AM in response to cpcallen

I cannot offer a solution but a work aroud:

What I do in a situation like this, is to create two smart albums:

  • one album of images not to be scaled, to be exported with export preset: original size
  • one album of images to be scaled , to be exported with export preset: fit within


To sort the images I use a smart album with the rules


Album of Images to be scaled:

Add Rule : EXIF -> Pixel width is greater than ..... and EXIF -> Pixel height is greater than ...


Album of Images not to be scaled:

Add Rule : EXIF -> Pixel width is less or equal than ..... or EXIF -> Pixel height is less or equal than ...


Regards

Léonie

Nov 2, 2011 6:14 AM in response to léonie

Leonie,


Doesn't the EXIF pixel width and height look at the original (masters) dimensions? So if you crop in Aperture will this still work?


I've always used the Aperture pixel size as it seems to take the dimensions from the version and not the master but if i'm wrong using the EXIF setting would better as there are more options for comparison.

Nov 2, 2011 8:01 AM in response to Frank Caggiano

Frank,

you are perfectly right, the EXIF will use the dimensions of the masters, so cropped images will be assigned to the wrong album. Thanks for pointing that out.

But with the Aperture pixel size you can only compare exact values in a rule, so you would need many rules to express "less than" or "greater than". we would need to write an Apple Script to parse the Aperture pixel size, and so far I did not need that.

Regards

Léonie

Nov 2, 2011 8:05 AM in response to cpcallen

But my 720px image already fit within 960x960, so no scaling was required. At very least this option is mislabled.


I think the "scale to fit" option is meant to be read as "scale to a size that will fit best into ...", so it will scale the image to fill the space given, but the name is ambigious, to say the least.

Nov 2, 2011 9:22 AM in response to léonie

Yeah it' a shame that the options in the Aperture section of the filter are so limited. It would be nice to be able to do comparisons as in the EXIF section.


Might be time for some Aperture feedback.


An AppleScript setup as a service could work and potentially give even greater control over the filtering but I keep holding out hope that the next version of Apertue will go over to a true database system and allow all the types of searches you can do in a database on the Aperture library.


regards

Nov 2, 2011 9:44 AM in response to Frank Caggiano

+1 all 'round.


I'm pretty sure the one time I needed to do something similar I was able to use the Rule "Aperture" with the settings "File size" as a proxy/binning-fork for images below a certain dimension.


It's quite silly (imho) to have numeric metadata without making operators available for that metadata.

It's seems silly to have filtering without full boolean operators, but it may be that with huge datasets the hardware simply can't handle the queries.


Sound to just flit in and opine -- on a deadline 😉 .

Nov 2, 2011 9:58 AM in response to Frank Caggiano

I keep holding out hope that the next version of Apertue will go over to a true database system and allow all the types of searches you can do in a database on the Aperture library.

A true database interface would make things much more elegant and easy, I would love to be able to use complex relational or logical expression to query Aperture. But I am afraid that Apple might be turning Aperture into a general multimedia information system, with data mining gimmicks, like "retrieve similar images by showing an example" . They started down this road with faces - I find "Places" much more useful.

Prevent "scale image: fit within" from upscaling image on export?

Welcome to Apple Support Community
A forum where Apple customers help each other with their products. Get started with your Apple ID.