Entering pixels in crop box does not adapt according to orientation
When in crop mode ('c' tool) and you right click in the crop are, a properties box pops up where you can select the aspect ratio and you get to set the width and height in pixels (or another unit). However, there's a bug (in my opinion), because if 2x3 is selected aspect ratio and even though the current crop orientation is landscape, entering a number like 2560 in the first box would change the crop orientation to portrait and set the second box to 1707. If I put 2560 in the second box, the first box gets updated to 3840.
I had to create 3x2 custom aspect ratio in order to be able to type in desired longest side in the pixels box and have it applied in landscape orientation. Nevertheless, I would be happier if I didn't have to do this, because I have to switch between 2x3 and 3x2 which is the same aspect ratio...
-
Just drag the crop (by a corner or an edge) to the opposite orientation and the preset ratio will adjust as required.
0 -
Pavel, thanks thats right so I don't need the custom definition. Still, I have to change aspect ratios just for the sake of entering the pixels. I don't understand why it does not tend to the current orientation. This behavior is not consistent with what it displays the first time when you open props (where it ignores the definition).
SFA, thanks, but I know that already. The issue I describe is with entering pixel values for longest side / shortest side in the crop properties box. If you want to see what I mean, open a photo of yours that is in landscape orientation. Then select c tool and right click in image area to bring the box. There make sure it says 2x3 as aspect ratio. Then type some other number in the first box and watch the orientation flip to portrait.
0 -
My use case more precisely is to crop wildlife images. But rather than some arbitrary size e.g. 1041x694, I go with standard screen resolutions (1280, 1680, 1920, 2560) in the case of images where the subject is rather small.
0 -
I don't think one can conflate the ratio definition with an orientation assumption.
Much depends on the concept of the Process Recipe definition. That is the primary definition and the ratio just offers some constraint to the proportions of the crop (and visual advice about how well the results match the apparent wishes of the definition as far as dimensions are concerned) rather than selection and orientation.
My personal feeling is that with the possible variations of functional approach available according to the definition of the Process Recipe. Much will depend on how that definition fits with the ratio constraint and the dimensions of the source file. Whether the file is currently oriented in portrait or landscape mode (in human terms) or already has some form of rotation applied is not of concern to the program's decisions until further instruction arrive.
However I do agree that it can seem a little weird at times. Just not in a way that I personally find bothersome given all of the instructions and constraints available available within the output and export processing commands.
0
Post is closed for comments.
Comments
4 comments