Installing and Updating
There are two classes of differences:
1. how you are permitted to use the product, and
2. what technical features are provided.
Very briefly, Professional Edition is required for uses beyond personal satisfaction and educational instruction. If you're selling many images or using the software as part of your job or to support a business, museum, or funded project, then you need Professional Edition. Professional Edition also provides access to the software's most advanced technical features and extended access to our support staff.
Prosumer Edition is our flagship product for non-professional users. It includes all the technical features from Professional Edition, but at a reduced price for advanced consumers.
Here is a full list of the features that require Prosumer Edition or Professional Edition. (We call these the “advanced Pro-only features” for short.)
Personal Edition is our entry-level product. It contains all the features that many people ever need, plus free trials of the Pro-only features. Trials of Pro-only features cover a 30-day period that starts when each feature is first used. To continue using a Pro-only feature after its trial period has expired, you can upgrade to Prosumer Edition for just the difference in license prices, by contacting email@example.com .
Menu items are labeled (Pro) if you need a Professional Edition or Prosumer Edition license to use them beyond a 30-day trial. Each of these “Pro-only” features has a separate trial period that begins when that feature is used for the first time. After first use, you can keep using the feature for another 30 calendar days. If you don't have a Professional or Prosumer license when the trial period expires, the feature becomes disabled and appears gray in the menu. If you get tired of looking at those grayed-out items, go to Options > Preferences > Look & Feel, and select the option to “Hide unlicensed features after trial period has expired”.
Please see "What are the differences between Personal, Prosumer, and Professional?" for a list of all the Pro-only features.
Yes, updates are free. We've been issuing free updates ever since Zerene Stacker was first sold, back in 2009. We have no plans to change that policy. It's so much simpler and more pleasant when everybody can just use the same current version.
No, it's the same price. Zerene Stacker supports 64-bit mode in all editions including Student and Personal.
No, your same license still works, even if you're going from 32-bits to 64-bits. Just download and install the appropriate version for your new computer, and re-install your old license key.
No, you can mix-and-match however you like, as long as you stay within the total number of computers allowed by the license.
The software is only available by download, but it's easy to make your own CD. Each download is just a single file that is also suitable for offline installation. Just use any machine that is connected to the Internet to download the version you need. Burn it to CD or thumbdrive on that machine, then carry the CD or thumbdrive to your offline machine and install the software there. Your license key can be transferred the same way. Just write the email to a text file, burn that to CD or thumbdrive, move it to the offline machine, and install the key.
A related issue: when running the software on a machine that is not connected to the Internet, it's best to clear the two checkboxes at Options > Preferences > Updates & Stats. That will prevent the software from attempting to contact zerenesystems.com, which would otherwise produce a warning message when the access failed.
We've posted the license terms HERE.
License terms can also be reviewed at any time inside the software, at Help > About Zerene Stacker > “Show license terms”.
The latest regular release of Zerene Stacker is always posted on our Downloads page. There is one separate file for each type of computer. Choose the appropriate one and download it. For Windows, the downloaded file is a classic Windows installer. Just run it, and it will walk you through the installation process. For Macintosh and Linux, the downloaded file is a self-contained bundle that does not need to be “installed”. Just put it anywhere you like, typically either on your Desktop or in your Applications folder.
The first time you run Zerene Stacker, it will go through a short process of configuring memory allocation based on what type of computer you have and how much physical memory it has installed. After this is done, the program will automatically restart and then you'll be ready to process images.
Licenses get installed using copy/paste at Options > Registration while Zerene Stacker is running. Just be sure to include the whole license key including all the equal signs ==== and everything between them. For detailed instructions, see HERE. If you're currently running an expired trial, then pay particular attention to step 5 because a browser window may be covering up part of Zerene Stacker that you need to install the license.
Just visit one of those pages and download the appropriate version for your type of computer.
Then install the download as if you were installing the program for the first time.
On Windows, installing the new version will automatically replace the old version.
On Macintosh and Linux, you will have to manually move the old version to trash, and move or rename the new version to replace it. Otherwise both versions will continue to be available, and you will run whichever one you happen to click on. On Mac, when trashing out the old version, do NOT allow any third party uninstaller or cleanup applications like “AppCleaner” to run. In their enthusiasm to eliminate files that they think are not used, they're likely to also delete files you really do need, like your license key and Zerene Stacker configuration files.
Yes, this works fine. On Windows, just tell the installer to put the second version in a program folder and Start Menu folder that are different from the first version. On Mac and Linux, the versions are simply distinguished by name and location, which you must specify manually.
There is no limit to the number of versions that you can have installed simultaneously. Each version is self contained and will operate independently except that they share a single folder that contains your license key, program configuration (Options > Preferences settings), and log files.
If you're using the Lightroom plugin, then Lightroom will access whatever version of ZS was last used to create the plugin scripts, at Options > Plugins… > Lightroom.
Yes, our beta test channel provides early notification and access to new features as they are developed. The way it works is simple. The latest public beta version is always posted on our Beta Testing Downloads page. Versions that are downloaded from there have build numbers that end in “_beta”. Whenever you're running such a version, you will receive notifications of new updates and announcements for the beta channel, instead of the regular release channel. You can move back and forth between beta and regular release channels whenever you want, just by downloading and installing the appropriate version of Zerene Stacker.
Yes. Zerene Stacker will work with any camera. That's because it does not attempt to talk directly with your camera. It just processes the image files that the camera creates. You can tether your camera to a computer so that Zerene Stacker can immediately access the captured images, but in that case it will be some other piece of software that's talking with the camera. Our Tutorials section includes discussion of several commonly used software packages for tethering.
The input and output formats are JPEG and TIFF, the latter in either 8- or 16-bit RGB. In general the most reliable TIFF format is uncompressed; some compressed formats such as 16-bit ZIP are not readable. A few other formats such as PNG and BMP can be read but not written.
To process raw files takes two separate steps. First you convert the raw files to some RGB format, typically TIFF, and then you stack the TIFF files.
For highest quality, we recommend converting raw files to 16-bit TIFF using your favorite raw converter and whatever settings make it work the best. After stacking the 16-bit TIFFs, tell Zerene Stacker to save its output also as 16-bit TIFF.
Because 16-bit TIFF files are lossless and have more bits per pixel than are captured by current cameras, this process retains all of the image quality intrinsic to the raw formats.
Zerene Systems does not provide raw converters. You can download those separately, or use software provided by your camera manufacturer.
If you use Lightroom, then be aware that there's a Lightroom plugin for Zerene Stacker that handles raw conversion automatically. When using Lightroom with the plugin, processing raw files is just a matter of selecting them and doing an Export to Zerene Stacker. See Working with Lightroom for more details about this "Pro-only" feature.
A longer explanation is that no stacking software really works directly with raw files.
The structure of data in a typical raw image file, one value per photosite with color implied by a mosaic Bayer filter pattern, is fundamentally incompatible with the image alignment process that is required for stacking.
Some stacking software deals with this aspect by accepting raw files at the level of the user interface, then converting them to some RGB format, typically TIFF, in a background process that is easy to overlook and may be difficult to optimize.
Zerene Stacker goes the other route, exposing the conversion process and encouraging users to deal with it as what we think it really is: a key part of the overall workflow that needs to have some attention paid to it in order to get best results.
By default, whatever color profile is used by the input files is also copied through to output files that are saved as JPEG or TIFF. However, color profile is ignored in Zerene Stacker's own screen displays unless the option is set to “Use input file profiles for ZS screen displays” (at Options > Preferences > Color Management). This advanced Pro-only feature is set off by default in the trial version. As a result, stacks using a wide-gamut profile such as ProPhotoRGB may appear significantly different when displayed by Zerene Stacker than when displayed by Photoshop or similar tool. On some computers Zerene Stacker will also ignore the color profile of your monitor, so that even sRGB images look different than shown in Photoshop. These differences may be worrisome if you don't know what's causing them, but the key thing to remember is that the color profile will be correct in the output file.
Note: there is an optional setting at Options > Preferences > Color Management that can cause color profiles to be omitted from output files. If you're having trouble with profiles, check there to be sure that the Output option is selected to “Copy profile from input”.
You need to use File > Save Output Images(s). That will give you a choice of TIFF or JPEG, with options appropriate for each format (compression quality for JPEG, 8- versus 16-bit for TIFF).
It's a common mistake to use File > Save Project and then notice that what gets saved are .zsj and .zsy files that can't be used by anything besides Zerene Stacker. File > Save Project is for tasks like coming back tomorrow to retouch an image that you generated today. It stores images in lossless formats and keeps track of alignment information so that you can resume work immediately, with no expensive computation. See Saving Work In A "Project" for more discussion about that.
Saving EXIF and other metadata is controlled by the setting at Options > Preferences > Image Saving > “Copy metadata from source images to saved output images”. This is a “Pro-only” feature, which means that it's available for long-term use only with Prosumer or Professional licenses. If you're using Prosumer Edition or Professional Edition, then this feature is selected by default. If you have only a lower level license, such as trial, Student, or Personal, then you can run the feature as a 30-day free trial by explicitly selecting it.
First, be reassured that your output images have the same number of pixels as your input images. You haven't lost anything and all your original lovely detail is still there.
The troublesome output images don't actually say 72 ppi. What's happening is that Zerene Stacker has produced an output image that does not have a ppi specification at all, and whatever tool you're using to look at the image has assigned its own default interpretation of “72 ppi”. Ppi is not meaningful for screen images, and for prints ppi is implied by the combination of print size and pixel count. If you really do need some particular setting for ppi inside the image file because that's how a requirement happens to be specified, then just pull the file into Photoshop, do an Image > Image Size… with the checkmark removed on “Resample Image”, then save the result to a new file.
There is an option to preserve the ppi setting, by selecting Options > Preferences > Image Saving > “Copy metadata from source images to saved output images”, before doing File > Save Output Image(s). This Pro-only option will also save all other EXIF metadata such as camera & lens type, exposure settings, GPS location, and so on. Note that “Copy metadata…” is automatically selected by default when you are running the Lightroom plug-in, so if you're running the trial version with default settings, you may notice a difference between going through Lightroom and launching Zerene Stacker separately.
In most cases, no. Typically you'll shoot a stack either by controlling focus manually, or by using a camera control device such as CamRanger, or by tethering your camera and using a program like ControlMyNikon or ControlMyCanon. In all those cases, Zerene Stacker does not participate in the capture process. The only time that Zerene Stacker gets involved in controlling the shooting of a stack is when you're using a StackShot rail and you've chosen to use Zerene Stacker's own Stackshot control panel for that.
Yes, it surely does. This question is often asked by people who are worried about focusing by using the big ring on their macro lens. In that case it's clear that magnification changes along with focus. But it turns out that there are magnification changes almost all the time due to perspective, no matter how you focus. The software doesn't care what the cause is for magnification changes; it just corrects for all of them.
For DMap, it's definitely best if the frames are processed in order, either front-to-back or back-to-front. If they're out of order, then the result may still look OK at first glance but it's almost certainly degraded. Often there will be obvious artifacts like nasty halos.
PMax itself does not care about order, but going from one end straight to the other is still the safe way to get good alignment. Sometimes when source frames are processed out of order, enough error accumulates in the alignment process that two frames, focused at nearly the same depth but far apart in the stack order, end up aligned slightly differently. When that happens, you get artifacts like “echoes”.
Front-to-back versus back-to-front makes no difference in most cases. The visibility methods currently used by Zerene Stacker are symmetric with respect to depth order. They produce the same image quality and artifacts no matter which way the stack is processed. The default behavior is to start processing at the narrow end of the stack, meaning whichever end appears to have a smaller FOV based on comparing first and last frames. That choice reduces or eliminates edge streaking and in some cases can slightly improve the quality of alignment. Options are provided to process the stack in a specific order if desired, but those are to control framing, not image quality.
One exception occurs if your subject is liable to move away while you're shooting. In that case you should start at whichever end you consider most important, so that if the subject does leave you may still have something useful to work with.
If you're shooting very small subjects such as details of insects and flowers, then a high precision screw-driven focus rail is very helpful and sometimes required.
However, you don't need a focus rail for many applications, and in fact for larger subjects you'll probably get better results by stepping focus with the ring on your lens. See HERE for more discussion on that point.
Lenses with auto-focus capability can usually be controlled very precisely by software if you tether your camera to a computer. See the Tutorials Index for suggestions regarding software to do that.
There are several good ways to figure out what aperture setting and step size to use.
If you're going to be shooting a lot of stacks under similar conditions, then one very good method has four major steps:
The above procedure is very reliable and automatically incorporates your own criteria and the requirements of your own application. Both of those can make large differences in determining which aperture setting and step size are best for what you're doing. However, this experimental method obviously takes a fair amount of effort.
As a shortcut, you can skip steps 3 and 4, and rely instead on the tables that we've provided HERE. They basically rely on computation to determine for you a step size that will prevent focus banding, once you have determined the magnification and aperture setting that you want to work at. Similar tables that provide focus distances for landscape and other large scale work can be found HERE.
By the way, it turns out that the classic tables and formulas for DOF are not so good for focus stacking with modern cameras and display software. They worked OK for shooting single pictures with film and prints, but now the numbers that they produce are often too large. If you rely on the old values, you're very likely to see focus banding when you zoom in to look at “actual pixels” and full camera resolution.
The memory requirement is determined by image size as measured by pixel count. The recommended setting is at least 100 MB for each 1 megapixel, so 12 megapixel images need 1200 MB, 24 megapixel images need 2400 MB, and so on. Somewhat smaller settings can be used, down to a minimum of roughly 75 MB for each 1 megapixel, but this may make stacking run a little slower. Larger settings, up to about 200 MB for each 1 megapixel, may make some operations run faster.
Note that the memory requirement depends on pixel count and not on input file size or number of frames in the stack. There is no significant difference in memory requirement between processing JPEG and TIFF images, and the memory requirement does not increase with deeper stacks.
In most cases it is counterproductive to allocate much more memory than described above, because this will just cause more contention with other processes in your computer.
Drag-and-drop is usually the quickest and easiest method. You don't have to use Add Files at all. Just open another window showing your operating system's file chooser, either Windows Explorer or Macintosh Finder. Select files there, then press and hold the mouse button while dragging the selected files onto the Input Files panel of Zerene Stacker. Release the mouse button to drop the files into Zerene Stacker. This method is more powerful and flexible than Add Files because you can use all the display options provided by your operating system, including tables of thumbnails or popping up another image viewer if you need to take a closer look at some image before deciding to add it to Zerene Stacker.
Streaked edges usually happen when some source images are centered differently from others. The streaks appear in areas that are outside the frame of at least one image.
What happens is that the software picks one frame, either the first or last, to use as a master. Then each succeeding frame essentially gets registered against the first using a rotate/shift/scale approach based on comparing the image content. If it happens that a later frame ends up not covering the whole area covered by the first frame, then the software fills in the missing edge strips with copies of the closest available pixel. As a result, any detail that appears along the edge of the frame gets smeared from wherever registration puts it clear out to the edge of the frame. That produces streaks like the ones you see. Sometimes the streaks do not propagate clear through to the output because they are overwhelmed by stronger real detail in other frames. But when the filled-in streaks are the strongest available “detail”, then they propagate to the output and produce the effect you see.
Streaked edges are common for stacks that are shot handheld. They can also happen with a focus rail if the camera is pointed a little bit to the left or right, or tipped up or down, or if the rail is mounted on a tripod that sags when the camera is moved. Shooting through some stereo microscopes can also produce this effect, because with those scopes the camera is essentially shooting what one eye sees, and that's pointed a little bit left or right to produce the stereo effect.
Streaked edges can also occur when the subject moves slightly within the frame, such as a flower that slowly wilts while the stack is being shot. From the standpoint of the software, there's really no difference between the subject moving around the frame, and the frame moving around the subject.
For some hints about how to investigate what's going on, see How can I detect movement in my stack?
Edge streaks can also be caused by forcing a stack to be processed starting at the “wide” end, meaning whichever end of the stack has the widest field of view. In this case the streaks are likely to appear on all four edges, and may extend from the edge of the image to the edge of the narrowest field of view. With standard settings, Zerene Stacker automatically determines which is the narrow end of the stack and starts there, which completely prevents edge streaks with a well aligned stack. However, it can be forced to start at either end by de-selecting Options > Preferences > “Automatic order”. Normally we recommend to leave “Automatic order” selected, and set things up when the stack is shot so that everything you care about is contained even within the narrowest frame. See the tutorial HERE for more information on that point.
There are three reasons that output images can have different colors from the input: 1) brightness adjustment, 2) PMax, and 3) “Retain extended dynamic range” when saving. “Brightness adjustment” refers to Zerene Stacker's attempt to correct for uneven exposure between various input images. That feature is turned on by default, but you can turn it off by un-checking Brightness at Options > Preferences > Alignment. “PMax” refers to the PMax stacking method, which often makes slight changes in brightness, contrast, and saturation as a side effect of doing its focus stacking. This behavior is an unavoidable side effect of PMax and should be considered as one of the tradeoffs of PMax versus DMap. “Retain extended dynamic range” when saving causes the range of internal pixel values to be compressed if necessary to fit within the 0-255 range of image files. Internally the range can exceed 0-255 as a result of PMax, brightness adjustment, or even just pixel interpolation during alignment.
Color/brightness/contrast changes can be completely avoided by using the DMap stacking method, with Brightness adjustment turned off at Options > Preferences > Alignment, and “Retain extended dynamic range” turned off at Options > Preferences > Image Saving or in the file save dialog.
Sometimes images look fine in Photoshop, Lightroom, or some other image viewer, but suddenly look noisy when you load them into Zerene Stacker. If you look closer, you discover that the noise appears when the images are viewed at some reduced scale like “Fit window”, but at 100% the images look the same in Zerene Stacker as they do in the other programs.
The reason this happens is that the other programs “anti-alias” their screen displays by averaging together lots of image pixels to make each screen pixel, and Zerene Stacker doesn't bother to do that.
The effect can be worrisome when you first notice it. However, the screen display appearance does not affect the quality of output image files, so once you realize what's going on, the worry goes away.
The best settings at Options > Preferences > Alignment depend on what you're doing.
The default settings are to correct for every common issue:
However, in many cases one or more of those issues is ruled out by hardware when the stack is shot. If you're using a focus rail or a microscope, then it's unlikely that there's any rotation to deal with. If you're using continuous illumination instead of flash, then it's probably quite consistent from frame to frame. In some microscopy work, none of these issues are important.
The basic guideline is to turn off any alignment option that you don't need. That will make the alignment process go faster. In some cases, particularly at high magnification such as through a microscope, turning off unnecessary options will also give a better result image. This issue is discussed in a lot more detail in the forum thread at http://www.photomacrography.net/forum/viewtopic.php?p=79878#79878.
The percentages at Options > Preferences > Alignment are limits and are measured with respect to the master frame. Most of the time they can be left at the default values, which are fairly large. Once in a while, typically with handheld work, it's necessary to increase the limits to allow correct alignment. Rarely, it's also necessary to reduce the limits to keep the software from wandering off and latching onto some bogus alignment. Typically this happens only if the image contains some strong repeating pattern like a regular grid.
PMax is a “pyramid” method. It is very good at finding and preserving detail even in low contrast or slightly blurred areas. It's also very good at handling overlapping structures like mats of hair and crisscrossing bristles, nicely avoiding the loss-of-detail halos typical of other stacking programs. But PMax tends to increase noise and contrast, it can alter colors somewhat, and it's liable to produce fuzzy “inversion halos” around strongly contrasting objects.
DMap is a “depth map” method. It does a better job keeping the original smoothness and colors, but it's not as good at finding and preserving detail.
The two methods complement each other. Some types of subjects look good when they are processed automatically by PMax, but not by DMap. Other subjects are just the opposite. For particularly challenging subjects like bugs and flowers shot through microscope objectives, neither method is ideal by itself. In that case the best results are obtained by using human judgment and the retouching tool to combine the best aspects of both algorithms.
For further discussion of these issues, see “DMap versus PMax” on the Zerene Stacker: How To Use It page.
First, note that there's a tutorial specifically on “How To Use DMap”. Visit the Tutorials index page to find that.
But as a quick guideline, the best values for the “radius” parameters at Options > Preferences > DMap Settings depend on two things:
There are basically three cases:
In any case, set Smoothing Radius to half the value of Estimation Radius.
When DMap pauses for you to Set Contrast Selection, move the slider until out-of-focus background goes black in the preview image, while your subject retains most of its natural colors. What you're doing is using your human judgment to mark “can't tell” regions where you want the program to emphasize smoothness rather than getting misled by pixel noise that might look like detail but isn't.
Note: If DMap does not pause for you to Set Contrast Selection, then go to Options > Preferences > DMap settings and remove the checkmark on “Use preset contrast threshold”. The software is distributed with that option not checked, but sometimes it gets checked by accident and then the lack of pause can be very confusing!
In many cases it doesn't matter. If you have a good sharpening tool that can identify and sharpen real detail while leaving pixel noise largely unchanged, then you may get better results by running it before Zerene Stacker. That's because it improves the “signal-to-noise ratio”, which helps Zerene Stacker to make better decisions. But with sharpening filters that do not have that level of discrimination, you'll get similar results either way and it's quicker and safer to just sharpen the final result. If you do sharpen before stacking, be sure not to oversharpen because fixing that problem would require reprocessing the whole stack.
The same reasoning applies to noise reduction. If you can reduce noise while preserving real detail, then that improves the signal-to-noise ratio and it's a good thing to do before running Zerene Stacker. Just don't overdo it, again because fixing that problem would require reprocessing the whole stack.
The easiest way is to “play” the stack as it were a filmstrip. To do this, just press-and-drag within the list of input files. File selection will track the cursor, while the image shown in the source window will update to match. This makes it easy to quickly find any portion of the stack that you are interested in, and at the same time makes it easy to joggle between two or three frames to identify the exact frame where some problem turns up.
If you have already processed the stack, then you can also put a checkmark on “Show as adjusted” in the input files panel. This will show the source images as they ended up after alignment. This makes it much easier to spot movement of the subject. Of course if you are interested in seeing how stable and well aligned your setup is, you will want to leave “show as adjusted” unchecked so that you're seeing the source images before alignment.
By default, processing the stack also generates a set of highly compressed preview-quality images that can be played more quickly than the original high quality source images. For this reason, it's usually better to put off “playing” your stack until after it's been processed once, unless you have some reason up front to suspect that subject movement may be an issue.
Normally Zerene Stacker starts processing at whichever end of the stack has the narrower field of view. This is to minimize or prevent edge streaking, which otherwise may appear in edge regions that are not covered by some source image. The narrow end of the stack can be either foreground or background, depending on exactly what lens you're using and how you're doing the focus stepping. The software determines which end is narrower by comparing images in the first and last frames. Sometimes in microscopy the decision looks essentially random because it depends on the arrangement of objects in the image and how they appear to change size as they go into and out of focus.
You can stop Zerene from automatically setting the order by going to Options > Preferences > Alignment and removing the checkmark on “Automatic order”. Then you can switch the order, if desired, by using File > “Reverse order”.
Sure. First, go to Options > Preferences > Alignment and remove the checkmark on “Automatic order”. This will prevent Zerene Stacker from rearranging the stack based on its analysis of which end has a narrower field of view.
If you need to set the order very precisely, then you may also have to add the images one at a time or in small groups, using drag-and-drop or Add File(s) multiple times. Each time you drop files into the Input Files panel or click the Add button inside the Add File(s) dialog, ZS will sort the newly added files by name.
By removing the checkmark on “Automatic order” and adding files one at a time, you can set exactly any order that you want.
Probably you accidentally put a checkmark on “Retain extended dynamic range” while saving the image. Remove that checkmark at Options > Preferences > Image Saving, or when you save your next image, and the problem will go away.
As background, you need to know that the PMax stacking method often causes contrast to increase, pushing darks darker and brights brighter. If your source images are already high contrast, then the increase can internally push pixel values to “darker than black” or “brighter than white”. Such values cannot be saved in ordinary image files. By default, Zerene Stacker clips these pixels to exactly black or white when the file is saved, thus throwing away some information you might like to keep. Placing a checkmark on “Retain extended dynamic range” essentially does a “levels adjustment” that reduces contrast and possibly brightens the image, exactly enough to occupy the full range of allowed pixel values, 0-255 in an 8-bit image. This preserves all the computed pixel values so that you can apply your own levels or curves adjustment in Photoshop or any similar tool to get whatever appearance you like best. When using “Retain extended dynamic range”, it's also a good idea to use 16-bit TIFF output, so as to preserve good gradation that might be lost if the extra dynamic range were compressed into 8 bits.
Note that in previous versions of Zerene Stacker, this option was named “Retain full dynamic range”. It has been renamed to more accurately reflect its function.
UDR stands for Unrestricted Dynamic Range. As discussed in the previous FAQ, the PMax stacking method often causes contrast to increase, pushing darks darker and brights brighter. To compensate for this effect, the last step of the PMax method is a type of HDR (High Dynamic Range) local adjustment of contrast & brightness that preserves detail in overly light regions while pushing those regions back into standard bounds. By selecting the option to “Retain UDR Image”, you can preserve the image as it stood just before the HDR step. This allows you to run your own HDR methods outside Zerene Stacker, say in Photoshop. When you select “Retain UDR Image”, each run of PMax produces two Output Images, one of them with “UDR” in its name. To finish processing that image outside Zerene Stacker, you should save it as 16-bit TIFF using “Retain extended dynamic range” on the save.
As mentioned in other FAQs, the PMax method tends to accumulate noise. That's because in general it is relentless about preserving the sharpest detail at all size scales, but at the very finest scale it has trouble distinguishing between focused detail and pixel noise. The “grit suppression” option, which is selected by default, makes a small sacrifice in saving fine detail, in exchange for the benefit of getting significantly less noise in the final image. The simplest way to understand its significance is to render with PMax twice — once with and once without grit suppression selected — and then compare the results when zoomed in to 100% actual pixels.
Yes, there are several. First, turn off functionality you don't care about. This applies especially to “Cache unaligned screen images” and “Cache aligned screen images”, found at Options > Preferences > Caching & Undo. If you seldom or never want to detect movement by playing a stack as if it were a filmstrip, then remove the checkmark on “Cache unaligned screen images”. If you don't plan on retouching from source or you're prepared for frame selection to be sluggish, then remove the checkmark on “Cache aligned screen images”. Un-checking Options > Preferences > Alignment > Rotation and Brightness can help too, if your setup does not allow rotation and has stable illumination. On Mac, try un-checking the External TIFF Reader at Options > Preferences > Preprocessing; if you still get correct results, you'll get them a little faster. Also, note that there's an option at Preferences > Multiprocessing, to “Overlap I/O with computation if possible”. If you're using trial, or a Personal or Student Edition license, then that option is turned off by default. You can turn it on by explicitly selecting it and answering “Yes” to the question about “start trial?” For other options and details, see the discussion at http://www.photomacrography.net/forum/viewtopic.php?p=141699#141699.
There are several possible causes for the error message that “Image <filename> is a different size from the first image.”
We have a whole separate page about that; see Tips for Retouching.
There is no forum dedicated to just Zerene Stacker. Instead, for most users we recommend going to photomacrography.net, a strictly non-commercial web forum that covers all aspects of the photography of small things. Many of our users and the principal developer of Zerene Stacker are active participants there, and we prefer to keep our efforts concentrated in one place. Photomacrography.net has a well-earned reputation for in-depth technical information, combined with astounding images created by world-class photographers who are happy to discuss tips, techniques, and tools from all sources. On the other hand, if you're working entirely with subjects that too large to discuss at photomacrography.net, then the best source of information is to email firstname.lastname@example.org. We'll be happy to either answer your questions ourselves or point you to other resources as appropriate.
We have a separate document for that: see Working With Lightroom.
There are several keyboard and mouse shortcuts for selecting images and for adjusting image scale and brush size. Those are described HERE.
Currently there are no keyboard shortcuts for common operations such as opening and saving files.
Yes. Just go to Options > Preferences > Look & Feel, scroll down until you can see the option to “Suppress splash screen on launch”, put a checkmark on that option, and exit from Zerene Stacker. Your next launch should be quiet.
You've probably noticed that the default names are based on timestamps — good for uniqueness but not necessarily what you want for readability. You can construct your own templates to include source image numbers, processing options, and so on. This feature is documented at Options > Preferences > Image Saving; look at the Template field.
The underlying issue here is that if Zerene Stacker crashes or is aborted by the operating system while it has image files loaded, then the project and any temporary image files it was working on will be retained on disk and may consume significant space. These items are likely to be located in a folder of temporary files where they won't be obvious. Especially on Windows, orphaned projects and image files may be retained for long periods, since the operating system does not clean up temporary files very often.
To find orphaned projects, simply search your disk for folders (directories) whose name begins with “unnamedZSproj”. The full name will be something like “unnamedZSproj20090707122911640”, where the trailing digits are a timestamp (year, month, day, etc). Remove these folders and all their contents.
If you're using the Lightroom plug-in, and Zerene Stacker crashes or is aborted, then the plug-in's temporary image files will also be orphaned. These files can be located by searching your disk for folders whose name begins with “Lightroom_Export_to_ZereneStacker”. Again, the full name will be something like “Lightroom_Export_to_ZereneStacker_20140128223721”, where the trailing digits are a timestamp. Remove these folders and all their contents.
On Windows, in both cases you will have to select the option to “include hidden files and folders” so that the Windows Explorer Search function will find projects in the %TEMP% folder where they are normally placed.
The “smiling dog” image is the wing pattern of a California Dogface butterfly, Zerene eurydice. See HERE for an explanation of how the name “Zerene” came to be used for the software also.
Yes, a log file is automatically saved for each execution that encounters an unexpected problem. One log file is also saved for the last normal execution. All you need to do is locate these files in the ZereneStacker application directory as described below, then attach them to an email sent to email@example.com. The logs are ordinary text files that you can look at with any text editor if you have any concerns about their content. As an alternative to attaching the file, the content can also be copy/pasted into the body of your email.
To locate log and configuration files, proceed as follows:
Probably the ZereneStacker folder will contain several log files. To identify the proper one, consider the circumstances: If you received a popup diagnostic that said “Uh-oh – something went wrong and caused an internal error”, then the file is named something like ErrorLog<timestamp>.txt or AutoErrorLog<timestamp>.txt, where <timestamp> is a string of digits that indicate date & time. For example the file may be named ErrorLog20110508090456.txt, for a problem that occurred on 2011 May 8 at 09:04:56 am. If you did not receive such a popup, then the log file is LastNormalLog.txt.