Both my raw converter (darktable) and Hugin are capable of lens correction - but doing it in both would be incorrect. My 1st question is the place of lens correction in the workflow.
- I apply -1EV correction (compared to the Sunny-16 rule) in manual mode in camera to avoid clipping highlights;
- in the raw developer, I set the same white balance for all images, and correct exposure by the same amount, avoiding clipping (no curves or other processing);
- I export as 16-bit TIFFs
- stich the TIFFs in Hugin
- import the result into darktable for further processing (curves etc.)
Q1: At which step should lens corrections be applied? In the raw developer (I use darktable, that, in turn, uses lensfun), or should I just let Hugin take care of it? If in the raw developer, how will Hugin know it does not need to perform the lens correction?
Q2: Also, even with the steps described above, Hugin will sometimes give me more options to save the results (including fused and merged-fused output). Since all my input has the same exposure, why does that happen?
Note: I use Hugin in a very simplistic manner, using the assistant-based simple interface.