AfterShot Pro - Wishlist for future versions

[th_schroeder]

I would like to have the option to save xmp-files in a subfolder. The reason is that I would like go back to folders with older images some of which I have already edited with Bibble 5. Some of these edits I am happy with and I don't want to touch them anymore. But others I want to redo especially those that need highlight recovery.

I don't want ASP to read the xmp-files generated by Bibble 5, since this can create a mess. Instead, I want to start from scratch on these images. I think that separating xmp-files created by Bibble 5 and ASP by having ASP saving its xmp-files in a subfolder would easily solve this problem.

Thanks,

Thomas

[binoyte]

@ th_schroeder
Have look a that : http://forum.corel.com/EN/viewtopic.php?f=95&t=46740

[Artem]

I wish I had lens correction preinstalled profile for Canon S95.

[nyukuri]

I hope to see gradient layers/masks one day

[EOS]

I hope to see gradient layers/masks one day

a (small) solution is gradfilter plugin:
http://digitalarts.mindsocket.com.au/bi ... dgrad.html

[nyukuri]

I do have Grad filter. What I need/want are gradient layers that allow applying GRADUALLY any tool: sharpening, noise reduction, exposure, etc etc...

[nyukuri]

Many users use the "expose to the right" (ETTR) technique for better N/S ratio and generally better image quality.
RAW images are lightly overexposed (+0.3 to +1.0 EV) but without clipping the highlights. In the raw converter this overexposure is then corrected with the "exposure" tool and, if necessary, with highlight recovery. The histogram is then finally spread out to fill the whole possible tonal range. The result are much better images than if the photo was exposed "correctly" in the camera.

Until today, no manufacturer has implemented a simple automatic procedure, applying exactly these steps!

THIS IS WHERE ASP COULD STEP IN AND BE THE FIRST SOFTWARE SOLUTION FOR AUTOMATICALLY HANDLING "ETTR"!!!

1. an overexposed image is imported
2. ASP reads the EXIF information (exposure bias +1 EV) and corrects it AUTOMATICALLY with the "exposure tool" (decrease exposure by 1.00 EV)
3. the histogram is then spread out AUTOMATICALLY so that the image data takes advantage of the full available range (similar to AutoLevels), moving the White Point, just avoiding clipping
DONE!

This could be implemented as a single checkbox "ETTR" inthe exposure tool.

a) if the checkbox is left UNCHECKED the image is not altered by the described procedure and left overexposed, assuming that this is what the photographer intended
b) BUT IF the checkbox "ETTR" (Expose to the right) is ENABLED, ASP would follow and apply the steps described above!!!

two additional sliders may be helpful, one for the exposure correction for fine tuning (but this slider is set automatically according to EXIF information) and a second slider for the strength of spreading the histogram: from 0 (no spreading out) to 100 (maximum spread out)

[nyukuri]

The user may not remember how the image looked like at a certain point in the history but he may well remember that "last tuesday the image was right" and seeing this in the history allows him to quickly return to that state of the image!

since the history function in the catalogs saves all changes even of older sessions, it would be nice to save the steps together with the Date! This will allow to "remember" more easily changes that were applied long time ago and to return to them, based on the date. Let's assume a history like the following:

Initial settings
Adjust crop
Select crop size
Contrast = 13
Mids = -21
Luminance = 32
Noise Ninja Off
Noise Ninja On

Adding the date/time like in the following table would look like this:

2011 Dec 10 : Initial settings
2012 Mar 4 : Adjust crop
2012 Mar 4 : Select crop size
2012 Jun 15 : Contrast = 13
Tuesday : Mids = -21
Wednesday : Luminance = 32
Today 21:40 : Noise Ninja Off
Today 21:44 : Noise Ninja On

- For changes from the same day it would give the time ("Today 21:40")
- For changes within the last week it would simply give the week day ("Tuesday")
- For changes older than the last week it would give the date (Year, Month, Day)

[andreas]

Something like GradFilter for other tools: Create a region on a layer with large feather area and use your tools. Or do you think of something else?

Andreas

[nyukuri]

@Andreas
Thats exactly what I am thinking of Thank you!

[nyukuri]

Right now ASP does not have any form of navigator view. This could be implemented the following way:
1. The navigator view would NOT have its own window or Tab on any panel
2. Instead, the navigator view would be ON THE TUMBNAIL OF THE ACTIVE IMAGE IN "STANDARD VIEW" (F7)
3. For that, when using "Standard view" (F7) so that the active image and its tumbnail are shown, ASP would simply draw a red rectangle on the tumbnail, corresponding to the actual zoom
4. Navigation (moving the red rectangle) on the tumbnail could be made possible through a hotkey plus mouse click
5. Right now, in Standard view, it is possible that the tumbnail of the currently active image is not seen, due to scrolling. If the navigator is implemented, this would need to cause an "autoscroll" so that the tumbnail of the active image is always seen.

Advantages:
- no additional window necessary that would clutter the screen
- quick visual info of zoom and its position on the image always available

positive side effect:
- tumbnail of the active window always visible through autoscrolling

[nyukuri]

As of now, the "History view" has its own window, which unfortunately cannot be easily left toggled on because it always covers partly the image, partly the tool panels...
The "History" function should have its own Tab on the left panel. This way it could be pinned to be always visible but without covering the image or panels!

[nyukuri]

As of now, the "Layer" function has its own window, which unfortunately always covers partly the image and/or the tools panel.
1. "Layers" should have its own TAB on the tools panel!
2. similar to the "Filter" function, which indicates through a green symbol when the filter is toggled on, ASP should visibly show if Layers are used by turning the Layer symbol green as well. This will help the user to be better aware if there are layers and on which layer he is currently working.

[kaymann]

As of now, the "Layer" function has its own window, which unfortunately always covers partly the image and/or the tools panel.
1. "Layers" should have its own TAB on the tools panel!
2. similar to the "Filter" function, which indicates through a green symbol when the filter is toggled on, ASP should visibly show if Layers are used by turning the Layer symbol green as well. This well help the user to be better aware if there are layers and on which layer he is currently working.

+1

[nyukuri]

Some EXIF really needed for the Metadata Browser are:

1. Exposure Bias
2. 35 mm Focal Length
3. Resolution (in Megapixels, Width x Height)
4. Orientation

Less important, but still helpful:
5. Width
6. Height

THANK YOU VERY MUCH!!!