Page 1 of 1

Updated OSX 14.0 No OpenCL and crash

Posted: 26.09.2023 22:54
by kentam
Is that any beta can fix this?

Many thanks.

Re: Updated OSX 14.0 No OpenCL and crash

Posted: 27.09.2023 01:13
by Catherine
It will disable OpenCL automatically and no longer crash after a restart. So there no problem with using Helicon Focus, it will just be a bit slower because OpenCL acceleration doesn't work.

We can't update Helicon Focus right now because the developer tools we need also don't function on macOS 14, it will likely be fixed tomorrow.

Re: Updated OSX 14.0 No OpenCL and crash

Posted: 27.09.2023 16:19
by koenkooi
Thanks for getting on this so quickly! I haven't even upgraded yet :)

Re: Updated OSX 14.0 No OpenCL and crash

Posted: 29.09.2023 10:57
by Catherine
Helicon Focus has been updated for macOS 14.0: https://www.heliconsoft.com/downloads/HeliconFocus.dmg

Re: Updated OSX 14.0 No OpenCL and crash

Posted: 02.10.2023 20:58
by shutterbug
Hello!

I'm having some trouble with crashes and errors.
For example I get occasional errors like this:

"The save file operation failed.
The save file operation failed to connect to the open and save panel service."

Or:

"Exeption"

I've created error logs (attached zip)
EDIT: this is with the latest version 8.2.8. you linked

Re: Updated OSX 14.0 No OpenCL and crash

Posted: 03.10.2023 00:06
by Catherine
Hello,

Sorry about the issues, and thanks for the error logs, they're useful, but we also need to understand how the errors occur and how to reproduce them.

1. "The save file operation failed." - there is no such message in Helicon Focus, it's displayed by some other software. Please take a screenshot the next time it occurs and send it to [email protected]. Also, send a bug report from Helicon Focus after this message pops up.
2. "Exception" - please send a bug report after getting this message.
3. The crashes occur when a dialog is shown (or is being brought up). That is, when there is some kind of secondary window over the main Helicon Focus window. Which dialog(s) trigger the error? Do you see any patterns behind the crashes, something that could help us reproduce these crashes?