Smart Album based on cropped size?

Antony Foster

• November 07, 2019 23:35

Any advice on creating a Smart Album based on the post cropped image size?

The existing Height and Width search criteria seem to use the original image size.

0

• 

  SFA

  • November 08, 2019 04:33

  There is not really a cropped size.
  
  There is a ratio for a crop and some sizes suggested by the definition of an associated process recipes but there can be many process recipes that will produce different file sizes for different outputs but with the same ratio for the image.
  
  If you have produced an output file it should be possible to filter and select on the dimensions of that file.
  
  HTH.
  
  Grant

  0
• 

  SFA

  • November 08, 2019 04:33

  There is not really a cropped size.
  
  There is a ratio for a crop and some sizes suggested by the definition of an associated process recipes but there can be many process recipes that will produce different file sizes for different outputs but with the same ratio for the image.
  
  If you have produced an output file it should be possible to filter and select on the dimensions of that file.
  
  HTH.
  
  Grant

  0
• 

  Antony Foster

  • November 09, 2019 21:22

  Thanks Grant.
  
  

  [quote="SFA" wrote:
  There is not really a cropped size.

  
  
  I was sloppy with my language. When I said "size" I should have said the available pixels without upscaling.
  
  I'm trying to create a smart album that only contains images that have enough available pixels to be printed at a specified physical size at 300px/in

  0
• 

  SFA

  • November 10, 2019 03:33

  [quote="mainlyfine" wrote:
  Thanks Grant.
  
  

  [quote="SFA" wrote:
  There is not really a cropped size.

  
  
  I was sloppy with my language. When I said "size" I should have said the available pixels without upscaling.
  
  I'm trying to create a smart album that only contains images that have enough available pixels to be printed at a specified physical size at 300px/in

  
  
  Ah, OK.
  
  Bear in mind that C1 will upscale - quite well in my experiments - up to 250%. However I do appreciate that you explicitly excluded the upscaling option.
  
  You would be able to do something with images processed to output but I don't think the information is readily and instantly available as a calculation based on the original image but taking into account any or all of the variants you may have options for using the Process Recipes.
  
  If you always knew that the images were likely to be at or very close to the original file size (i.e. you could ignore the crop for the purpose of selecting suitable files) then the original file size might be enough. But I suspect that may not be the case that you are describing, it certainly would not be for me.
  
  The only thing I can think of that might be at least a visual aid is that if you set up an Output Process recipe setting the given pixel dimensions and size required and select that as the active recipe as you scroll through the prospective images the images you should see some advisory indicators for any that would not 'fit' for some reason.
  
  The process summary would show them but also the labels on the crop outline assuming that you have them set to be displayed.
  
  Given 5000 possible content qualifying images that might not be very practical but scroll through a more manageable number - perhaps 50 or so - would probably be OK?
  
  There's nothing else I can think of at the moment. Sorry.
  
  
  Grant

  0

Post is closed for comments.