Error while capturing

[FletcherImages]

I've not been having any issues until this morning. This error message started showing up. I meet or exceed all of the stated requirements in this error message. A little help please.

[Catherine]

It's not an error in Helicon Focus itself; Windows has refused to either create the file or write the data to it. We don't know why, but usually it's one of the listed possibilities.
How exactly were you saving, was it a "Save as" dialog where you literally navigated to the target folder? Or was it "Save all" or auto-save in the batch mode? Is it possible that the indicated folder ("Hekicon Remote") doesn't actually exist?

[dusteddaily]

Hi Catherine...

I'm getting the same error when capturing a focus stack to any location (Nikon Z8 tethered to Mac Mini). Everything was working fine on a shoot yesterday but today I have to create a new folder for each stack.

This is working temporarily, but helicon remote is starting the file naming counter from _001 for each new stack, so I'll have to rename all of the files before importing to Lightroom to avoid file name conflicts.

Could it be that Helicon is trying to write file _001 to the chosen folder instead of picking up the counter number from the image of the last stack and advancing by 1?

[Catherine]

Hi,

I'm not sure I understand the problem. Did you get the same "Failed to save" message, created the folder manually, and then it saves there, but numeration is not what you wanted?
In that case it's a Mac thing, check System Preferences - Privacy & Security - Files and Folders, check if Helicon Remote has all the permissions. Maybe give it "Full disk access" too, even though it shouldn't be required.

[dusteddaily]

Yes, the same failed to save message if I try to save all images from each stack to the same folder. If I turn on "create new folder for the new stacks" then images save, but each stack starts with _001, _002 etc.

What I'd like it do, and it has been doing until this morning, is to keep writing files to the same folder, but using sequential file names/numbers. So the first image, first stack of the day would start with _001, and then each subsequent stack would start with the file number +1 of the last image of the previous stack. ie. the last file name might be 20250618_036 and when I start a new stack the beginning file name would be 20250618_037.

Helicon Remote has Privacy & Security > Files and Folders access to Desktop, Documents and Removable Drives which should allow it to write to the volumes I'm using.

[Catherine]

Sounds like it's not a problem with the permissions. Please reproduce the saving error and send a bug report: menu - Help - Report a bug.

[dusteddaily]

ok, I tried to recreate the error but the issue seems to have resolved itself. (???)

I turned off "create new folder for the new stacks", quit and restarted Remote and now the file naming continues where the last stack left off.

Thanks for your help Catherine. I hope this helps anyone getting the same error.