Sure. With Jpeg images 6.6 is only about 10% slower than 6.5.2 with jpeg. With DNG 6.6 is about 1000% slower than 6.5.2. See graph below. The left part is 6.6 rendering 33 x 20MP Jpeg images. Notice the system CPU usage (red). On the right, it shows 6.5.2 rendering that same stack (i ran it twice to...

Nope both behave pretty much the same - 10 seconds between images, whereas 6.5.2 takes 3 seconds. This is with DNG in DNG out.

I see there are supposedly some multi CPU performance enhancements in 6.6.0 - but it killed performance for me on my 6 core Xeon Mac Pro. CPU runs 1000% (most of that is kernel time). It takes approximately 10 times as long to render a DNG stack. During this time my mac is very unresponsive. Screen ...

I have 6.3 and tried to save as a DNG image (from Canon RAW). It pops up the JPEG compression dialog and saves the file with a dng extension but the file itself is a small JPEG file. This is on Mac OS X 10.10.

Yup drag & drop does not work for me either in 6.3.0 - worked fine in 6.2.2. Yosemite.

It only seems to be doing this if the target file already exists. It asks to overwrite the file but then writes the temp file and leaves the current file intact.

Just downloaded 6.2.2 - seems much better, it actually stacks images again. However, when I save my output as TIFF it now writes a file with Untitled.tif_temp and does not rename it back.

Could be. Though I have 64GB and it crashes between the second and third attempts usually.

Makes no difference - it still crashes. And I deleted it from the Terminal so nothing was hidden.

I went back to 6.0. It is the only one that does not crash for me on Mac Pro after trashing my preferences. Every single release since crashes. I might get one render off, but the second stack will cause a crash.

I moved all files in ~/Library/Preferences/com.helicon* to the trash.

The latest beta from your site. I fixed it by deleting my helicon focus preferences file - seems like using migration assistant to transfer the data from my previous mac messed something up, once the preference file was deleted helicon focus just started working again.

I just got a new 6 core Mac Pro 2013 and Helicon Focus keeps on crashing after rendering a stack of 39 16-bit TIFF files in Method 4 with everything set to defaults. This used to work fine on my MacBook Pro Retina 15". Process: HeliconFocus [2410] Path: /Applications/HeliconFocus.app/Contents/M...

Any updates? This makes using the software very hard as exporting 30 - 40 TIFF files is hard when I have to manually type in unique file names.

Not sure if this helps, but Helicon Focus is open, and I always drag / drop files replacing the previous ones. I regularly switch modes - Mode A / B / C, every time export (Save...) as TIFF. For every 20 times that I export an image, one or two would have a proper file name. I cannot see any correla...