Re: Helicon Focus 9.0.2

Announcement of new releases, bugs, support, suggestions
shutterbug
Posts: 68
Joined: 17.12.2022 15:14

Re: Helicon Focus 9.0.2

Post by shutterbug »

Catherine wrote: 08.05.2026 16:27
shutterbug wrote: 08.05.2026 14:45 would your recommend lowering it to 25%?
Yes, given that this happened. What were you doing in Helicon Focus at that time? How many stacks were processed?
oh ah... about 120? (2x 60 in Method B and Method C)

Thank you, I'll do that!

EDIT: reducing it to 20% worked just fine - but the next problem was that it didn't clear the cache when disk space was running los - so then it refused to autosave the rendered images and started to give errors.
So I guess there's some issue with memory and disk space management - and both cases the cache isn't getting cleared when it gets full.

EDIT2: I just read in another thread that Adobe DNG Converter handles the file management in RAW to DNG stacking - which would explain the problems as those were all RAW files.
el48tel
Posts: 105
Joined: 22.06.2016 17:05

Re: Helicon Focus 9.0.2

Post by el48tel »

Have you tried dragging the RAW files in from file management
Let Helicon do the stacking with the option to save the output files as DNG.
Saves involving DNG conversion of the input files then deleting the DNG files.
User avatar
Catherine
Posts: 1850
Joined: 29.04.2019 23:38

Re: Helicon Focus 9.0.2

Post by Catherine »

shutterbug wrote: 11.05.2026 12:53the next problem was that it didn't clear the cache when disk space was running los - so then it refused to autosave the rendered images and started to give errors.
Please send a bug report when this happens.
shutterbug wrote: 11.05.2026 12:53 and both cases the cache isn't getting cleared when it gets full.
Maybe, but not necessarily. The 50% limit is for the cache, but there is some non-cache data that can't be removed from memory, with raw stacks it can get up to a lot when you have many stacks rendered.
User avatar
Catherine
Posts: 1850
Joined: 29.04.2019 23:38

Re: Helicon Focus 9.0.2

Post by Catherine »

Vlasto wrote: 09.05.2026 13:29 With Stack Outputs, the rendered images from the bottom panel are also moved into the stack. Could you keep the rendering method name in the stack as well, the same way it is shown in the bottom panel?
Hello, this is implemented in the new version of Helicon Focus 9.0.3, please download and try it.
Vlasto
Posts: 5
Joined: 27.04.2026 23:08

Re: Helicon Focus 9.0.2

Post by Vlasto »

Catherine wrote: 13.05.2026 11:29
Vlasto wrote: 09.05.2026 13:29 With Stack Outputs, the rendered images from the bottom panel are also moved into the stack. Could you keep the rendering method name in the stack as well, the same way it is shown in the bottom panel?
Hello, this is implemented in the new version of Helicon Focus 9.0.3, please download and try it.
Thank you, that’s exactly how I imagined it. Great.
Marc_R
Posts: 7
Joined: 06.01.2025 14:03

Re: Helicon Focus 9.0.2

Post by Marc_R »

Catherine wrote: 10.04.2026 16:43
Marc_R wrote: 10.04.2026 15:30 The request to add an option in the substack-function to render the substacks with another method / another setting is on your "to do"?
Yes

Can you provide a timeline when (if ?) this feature might be implemented?
Rendering substacks in 9.0.3 works flawless, but still there is no option to render the results with another method or other settings than those used for rendering the substacks.

I think that this option could be beneficial in some cases, e.g. just did a stack of a highly reflective mineral with substacks in method B and manually rendered these with method C. The resulting image was much better (as to my taste), had more brilliance than those stacked solely in B.
User avatar
Catherine
Posts: 1850
Joined: 29.04.2019 23:38

Re: Helicon Focus 9.0.2

Post by Catherine »

I can't say right now, but it's on the to-do list.
User avatar
Catherine
Posts: 1850
Joined: 29.04.2019 23:38

Re: Helicon Focus 9.0.2

Post by Catherine »

Some of you have encountered issues with disk space / file cache behavior on Mac, this is now fixed in the new version 9.0.4.
Post Reply