After the image was automatically aligned (rotated) and cropped (of course, because we do not need black edges…), I want to crop the image manually. But our problem is: there seems to be no option in OPL Elite to restrict the crop tool within the image itself – it should not be possible to mark areas outside the images to avoid “black edges”.
New screenshots of an example image
[damned; I can’t insert more than one screenshot – oh, no, and I can’t insert more than 2 links …
[quote=“mwsilvers, post:13, topic:7955”]
do not understand what you want it to do that is not addressed by the information we provided.[/quote]
I can’t see how this is so difficult to understand. If I wan’t something smaller than the maximal crop given by the auto option as soon as I manually change the crop rectangle auto is turned off and I have to manually (try) to avoid black slivers. webaschtl complains about the same thing.
Up at the top. If You have not used up your votes it should say “Vote”. Click on that button. In my case I’ve used up my votes - so it says “Limit”. Please see screen shot just below.
While fixing this may be helpful for some people, personally I won’t vote for it. In all honesty I believe there many other more critical things that DXO needs to address with their very limited resources. The priority for this one should be very low in my opinion. Sorry.
If the starting point is at the border of the black slivers, how hard can it be to resize in the direction of image content? There’s ten other people in the world who voted for this so Mark and I must be missing something.
I for one sometimes crop outside of the box as:
when I’m shooting sports and need just a bit more content so I fill with grass or building or sky.
often I shoot at night and might add some black.
You have won the gold award for the most trivial interface enhancement request attracting the greatest amount of attention.
I agree that both performance and interface issues should be addressed, but I think that this issue is relatively trivial compared to many other things that are in the pipeline. As it is, DXO is slow to implement changes and I would not want them to get bogged down on less critical requests. I’ve found that after rotating an image using the horizon, tool and using auto in the crop tool to constrain the image borders, it is relatively easy to manually crop the image further and keep it within the boundaries of the image without black slivers. Its a simple workaround. There are other issues with PhotoLab that do not have simple workarounds and these should be addressed first, in my opinion.
I sometimes wonder if people posting here even use the program. For starters for fixed aspect ratios the auto option only crops landscape or portrait orientation according to the image aspect. Given a trapezoid perspective corrected landscape image auto gives a less than maximal rectangle at the bottom. If I want a portrait crop I am out of luck and neither of the corners bound by the image extent are typically where I want them to be anyway. So back to zooming in and carefully dragging one or two corners to the image edge as ever.
It is not like it is a show stopping lack of feature. It is a feature I would welcome and use. I also don’t see it being very much work to implement, much of the edge and limit calculation must already be there for auto mode and an extra ‘Manual Bound’ option in the crop drop down is a trivial UI change.
Any software update requires discussion and prioritization, analysis, coding, unit testing, (testing of the local functional change in a test bed). Also required is system testing to see how the change may impact other functionality in the software as a whole, performance impact, end user beta testing, documentaion, and roll out. That can be a lot of work. And, they have to do it twice, once for the Mac and once more for the PC.
All functional changes have the potential for a very significant amount of effort. The question often is whether there is enough benefit for all that time and expense. If you believe making this change would only take a day or two, that is not the case. And even if it was, their small development team might be unable to focus on more critical fixes while working on this. A change that requires six weeks of coding or two days of coding will often require a similar amount of effort for all the other non coding tasks.
Software developers need to make tough decisions about which possible enhancements they will address. End users are often left not understanding why a seemingly simple change is ignored.
Less words and more illustration and examples. Your computer does have a screenshot function.
Your condescending attitude is totally out of place. I process at least fifty files in PhotoLab per week for publication. Over 1000 files/week go through FastRawViewer for culling, I’m only counting finished processed images. Again gold medal here for whingeing.
Well that’s a good illustration of your issue. webaschtl, Mark (mwsilvers) and I all create screenshots when we face a PhotoLab issue. Any good reason you should be given a pass?
– oh, no, and I can’t insert more than 2 links … 
