Re: Helicon Focus 9.0.2
Re: Helicon Focus 9.0.2
is there any advantage stacking Fujifilm RAF files rather than DNG
Re: Helicon Focus 9.0.2
Not really, but you probably spent extra processing time to obtain those DNG files and importing the original files directly would avoid the extra step. In terms of the image quality the format makes no difference.
Re: Helicon Focus 9.0.2
Thanks
I would agree
RAF into Helicon. Stack. Possibly stack the stacked outputs. Was very fast.
Then import into Lightroom
Looks like a new workflow!
I would agree
RAF into Helicon. Stack. Possibly stack the stacked outputs. Was very fast.
Then import into Lightroom
Looks like a new workflow!
Re: Helicon Focus 9.0.2
Hi Helicon,
Has V9.0.2 updated the CaptureOne plugin to ARM/Silicon or is it still Intel code? Thank you
Has V9.0.2 updated the CaptureOne plugin to ARM/Silicon or is it still Intel code? Thank you
Re: Helicon Focus 9.0.2
Still the same plugin for now, Intel. We'll update it later.
Re: Helicon Focus 9.0.2
A thought about future features .... but you might say that it is present in option #%^*
I usually make the three stacks by methods A B C. Save. Reload to make a stack from them. Is it possible that a stack can be made from unsaved stacks without the two intermediate steps of save and reload?
I usually make the three stacks by methods A B C. Save. Reload to make a stack from them. Is it possible that a stack can be made from unsaved stacks without the two intermediate steps of save and reload?
Re: Helicon Focus 9.0.2
Select the results (saved or unsaved, doesn't matter) - Right-click - Stack outputs
Re: Helicon Focus 9.0.2
I think ....
RAF to Helicon 9
Stack to 3 outputs
Stack outputs
Then import to LightRoom
is the fastest I have ever worked
Thank you Thank you Thank you
RAF to Helicon 9
Stack to 3 outputs
Stack outputs
Then import to LightRoom
is the fastest I have ever worked
Thank you Thank you Thank you
Re: Helicon Focus 9.0.2
Awesome, happy to hear the new feature is helping!
Re: Helicon Focus 9.0.2
Would it be possible to adjust Stack Outputs so that only retouched images are included in the process? It would greatly improve the overall quality of the final output.
At the moment, the initial rendered photos are being used in the Stack Outputs process, which means rendering errors are also carried over into the final Stack Outputs result. If the retouched images were used instead, the source material for Stack Outputs would be of much higher quality.
Thank you. I apologize for my weaker English.
At the moment, the initial rendered photos are being used in the Stack Outputs process, which means rendering errors are also carried over into the final Stack Outputs result. If the retouched images were used instead, the source material for Stack Outputs would be of much higher quality.
Thank you. I apologize for my weaker English.
Last edited by Vlasto on 27.04.2026 23:15, edited 1 time in total.
Re: Helicon Focus 9.0.2
Select two or more results in the bottom strip - right-click - "Stack outputs". This does exactly what you ask, it adds these 2 or more selected resulting images as a stack. This does not involve the source files that went into those original results.
Re: Helicon Focus 9.0.2
I see that the right click "Stack output" from the lower bar use by default the Method B. Is it possible to have the possibility to switch to Method C too?
Enrico
Enrico
Re: Helicon Focus 9.0.2
It uses the currently selected method, which you see in the parameters panel after selecting the output, and that's the method of the last stack you clicked when selecting it.
Re: Helicon Focus 9.0.2
Having used this new facility I can say how useful it is.
But ..... does your last comment mean that you cannot change the parameters? Or method? Previously I've tended to stick with method C for my stacking of the previous stacks because I work A then B then C so C would be left in place as the last used method. (Lazy!!!!!)
But ..... does your last comment mean that you cannot change the parameters? Or method? Previously I've tended to stick with method C for my stacking of the previous stacks because I work A then B then C so C would be left in place as the last used method. (Lazy!!!!!)