Thomas Kyhn Rovsing Hjørnet
Cph, DK.
- Total activity 2379
- Last activity
- Member since
- Following 0 users
- Followed by 0 users
- Votes 584
- Subscriptions 431
Comments
Recent activity by Thomas Kyhn Rovsing Hjørnet-
SFA, Yes, the road slopes a little. This shouldn't make any difference though. I believe I was facing the building directly more or less from the middle of what you see in the photo. No distortion ...
-
Another example. The flat surface of a building, one-point perspective, requiring very little correction, yet the horizontals are off. The adjustment points are lined up with the lines in the wa...
-
Thanks for the elaboration, SFA. It's obvious that there's a tradeoff, various sorts of distortion will result from keystone correction and part of the image will be lost. I don't imagine anyone wo...
-
I don't quite get the point about the 3rd dimension. Regardless of the appearance/illusion of 3-dimensionality in an image, the image is still 2-dimensional. Apart from barrel/pincushion distortion...
-
Spencer: I see your point regarding auto adjustment. It's a long time since I've used it in Lightroom as I rarely got vertical verticals nor horizontal horizontals, but perhaps it's been improved s...
-
Considering the current, rather rudimentary state of Capture One's keystone function, I would imagine that auto keystone is quite far off. As far as Lightroom's keystone tool is concerned, I would ...
-
I'm sure it's possible to get used to using the sliders, but I doubt that it's faster than using adjustment points with a properly working keystone tool. If only the actual malfunction was fixed, I...
-
As Spencer suggested above, a loupe function would make keystone adjustments a lot easier. As it is, you need to first place the adjustment points roughly where you want them, then zoom in on each ...
-
The two kinds of keystone malfunction that I've come across are with simultaneous vertical and horizontal adjustments and with vertical adjustments. In the fist case, the four-sided figure formed b...
-
I don't know anything about the details. As I understand, the 13.1.2 update was supposed to fix the issue, which it didn't. Hopefully, the next update will.