Support for Apple M1 Processor

Shooting in macro mode, techniques, tips & tricks
Post Reply
NikonZ
Posts: 1
Joined: 21.11.2021 23:29

Support for Apple M1 Processor

Post by NikonZ »

I recently upgraded my laptop to an Apple Macbook Pro with the M1 PRO processor. Helicon Focus seems to work, but it is incredibly SLOW. Definately slower than my old 2012 Intel based MBP. Since I have one of the faster laptop currently being made I expected the performance of Helicon Focus to improve, not degrade. I was wondering if there are any plans to make Helicon Focus M1 compatible?
User avatar
Catherine
Posts: 818
Joined: 29.04.2019 22:38

Re: Support for Apple M1 Processor

Post by Catherine »

It's very odd for your M1 Pro system to be slower than a 2012 MBP, I'm inclined to say this can't be (certainly not unless there's a malfunction of some kind). Did you actually compare the speed using the same images, or are you comparing your current work to the MBP speed you remember from a while ago? In the latter case it's likely that your images were smaller and did require fewer CPU cycles to process, but either way Helicon Focus shouldn't be slow on your new system. First of all, please run the benchmark (menu - Preferences - Performance) and let us know the score you get. And then, get the Helicon Focus 8 beta which does support M1 and M1 Pro, and turn on OpenCL acceleration. But before that, it might be interesting to see the non-OpenCL benchmark score from the version 8, too. I certainly hope it's faster.

https://www.heliconsoft.com/downloads/H ... s8Beta.dmg
RCinNJ
Posts: 5
Joined: 07.11.2021 20:49

Re: Support for Apple M1 Processor

Post by RCinNJ »

I'm not the original poster but seeing this I did what you asked and the results do not look very good to me-- unless shorter is better. I recently upgraded to a new MacBook Pro 16" with the M1 Processor, 10 cores, 32 GB of Ram. New to HeliconFocus, but I did recently purchase a license. It was very slow on my old MacBook Pro and I was hoping for a big improvement. It is faster, but not that fast. However, I had nothing to compare it to. A score of 212 doesn't seem that good to me.

I attempted to attach a .pdf of the results but I get the message this is an unsupported file format!? What is supported?

I had posted another question some days ago, that has not been answered yet, about getting a message that "The cache folder could not be created" and asked what I should do to create one. I don't know if performant would improve if I can solve this.
User avatar
Catherine
Posts: 818
Joined: 29.04.2019 22:38

Re: Support for Apple M1 Processor

Post by Catherine »

Try running the benchmark on a cold computer, I mean literally - turn it off and let it cool down and then turn it on and run the benchmark (try it first thing in the morning, for example). And don't open any other applications. The score is low either because the hardware warmed up and reduced the operating frequency (in order to stay cool), or because other applications are consuming some of the resources.

We've allowed attaching PDF files (previously, image files and archives were supported). And I've replied to your previous post, sorry it's a late reply - forum is not the best way to get tech support quickly (the best way is sending a bug report from the software itself, or using the contact form on our website).
Phil_Soon
Posts: 1
Joined: 08.06.2021 19:45

Re: Support for Apple M1 Processor

Post by Phil_Soon »

I was getting very slow stacking performance from my M1 Mac Mini when I exported from LR as DNG. But when exporting as TIFF the speed change is night and day.
Here’s my figures: 48 NIKON Z5 NEF files, each file approx 27MB
Exported to Helicon Focus as DNG, rendering time - 3mins 54.09sec
Exported to Helicon Focus as TIFF, rendering time - 16.10sec. That about 14x faster. I ran the tests again after a reboot of the computer and the results are consistent regardless of whether I start the test with TIFF or DNG.
So if I want to only work in raw then I have to export as DNG to be able to save the output as DNG and have to put up with the performance penalty?
User avatar
Catherine
Posts: 818
Joined: 29.04.2019 22:38

Re: Support for Apple M1 Processor

Post by Catherine »

You can only save the result as DNG (which is a raw format) if all the sources are in raw format. But you don't have to export your photos to DNG using some other software, you can directly open NEF files in Helicon Focus.
Raw processing is always slower, but 14x difference seems a bit too drastic. Make sure that parallel image loading is enabled (preferences - Performance), and that both the source folder (where the source images are) and the cache folder are on an SSD drive. If you're loading from HDD, from network, from a slow thumb drive etc. - the slow media speed will limit how fast the input files can be read and decoded.
Post Reply