Zerene Stacker

Differences

This shows you the differences between two versions of the page.

Link to this comparison view

Both sides previous revision Previous revision
Next revision
Previous revision
stacker:docs:faqlist [2019/06/07 23:12]
rjlittlefield [Are there more FAQs?]
stacker:docs:faqlist [2024/03/03 17:26] (current)
rjlittlefield fixed TOC link for new FAQ
Line 5: Line 5:
 **Purchasing** **Purchasing**
  
 +  * [[#​do_you_have_a_free_trial|Do you have a free trial?]]
   * [[#​what_are_the_differences_between_personal_prosumer_and_professional|What are the differences between Personal, Prosumer, and Professional?​]]   * [[#​what_are_the_differences_between_personal_prosumer_and_professional|What are the differences between Personal, Prosumer, and Professional?​]]
   * [[#​i_see_some_menu_items_labeled_pro__what_does_that_mean|I see some menu items labeled (Pro). What does that mean?]]   * [[#​i_see_some_menu_items_labeled_pro__what_does_that_mean|I see some menu items labeled (Pro). What does that mean?]]
-  * [[#do_you_have_a_free_trial|Do you have a free trial?]]+  * [[#can_i_test_professional_and_prosumer_options_in_trial|Can I test Professional and Prosumer options in trial?]] 
 +  * [[#​can_the_pro_only_warnings_be_turned_off|Can the Pro-only warnings be turned off?]]
   * [[#​are_program_updates_free|Are program updates free?]]   * [[#​are_program_updates_free|Are program updates free?]]
 +  * [[#​how_do_i_learn_about_program_updates?​|How do I learn about program updates?]]
   * [[#​do_i_have_to_pay_more_to_get_64-bit_mode|Do I have to pay more to get 64-bit mode?]]   * [[#​do_i_have_to_pay_more_to_get_64-bit_mode|Do I have to pay more to get 64-bit mode?]]
   * [[##​i_m_upgrading_my_computer_do_i_have_to_buy_a_new_license|I'​m upgrading my computer. ​ Do I have to buy a new license?]]   * [[##​i_m_upgrading_my_computer_do_i_have_to_buy_a_new_license|I'​m upgrading my computer. ​ Do I have to buy a new license?]]
Line 21: Line 24:
   * [[#​how_can_i_update_the_program|How can I update the program?]]   * [[#​how_can_i_update_the_program|How can I update the program?]]
   * [[#​can_i_have_multiple_versions_installed_at_the_same_time|Can I have multiple versions installed at the same time?]]   * [[#​can_i_have_multiple_versions_installed_at_the_same_time|Can I have multiple versions installed at the same time?]]
 +  * [[#​i_upgraded_my_computer_and_now_zerene_stacker_won_t_run_what_can_i_do|I upgraded my computer and now Zerene Stacker won't run.  What can I do?]]
 +  * [[#​i_m_trying_to_re-install_my_license_key_but_it_won_t_work_what_can_i_do|I'​m trying to re-install my license key, but it won't work.  What can I do?]]
 +  * [[#​i_lost_my_license_key_what_can_i_do?​|I lost my license key.  What can I do?]]
   * [[#​do_you_have_a_beta_test_channel|Do you have a "beta test" channel?]]   * [[#​do_you_have_a_beta_test_channel|Do you have a "beta test" channel?]]
  
Line 32: Line 38:
   * [[#​is_there_some_way_to_save_exif_and_other_metadata|Is there some way to save EXIF and other metadata?]]   * [[#​is_there_some_way_to_save_exif_and_other_metadata|Is there some way to save EXIF and other metadata?]]
   * [[#​why_do_my_output_images_say_they_re_only_72_pixels_per_inch|Why do my output images say they'​re only 72 pixels per inch?]]   * [[#​why_do_my_output_images_say_they_re_only_72_pixels_per_inch|Why do my output images say they'​re only 72 pixels per inch?]]
 +  * [[#​what_exactly_is_a_project|What exactly is a project?]]
  
 **Shooting Stacks** **Shooting Stacks**
Line 39: Line 46:
   * [[#​does_it_matter_if_i_shoot_the_stack_in_order|Does it matter if I shoot the stack in order?]]   * [[#​does_it_matter_if_i_shoot_the_stack_in_order|Does it matter if I shoot the stack in order?]]
   * [[#​does_it_matter_if_i_work_front-to-back_or_back-to-front|Does it matter if I work front-to-back or back-to-front?​]]   * [[#​does_it_matter_if_i_work_front-to-back_or_back-to-front|Does it matter if I work front-to-back or back-to-front?​]]
 +  * [[#​does_it_matter_if_I_have_extra_frames_at_the_front_or_back|Does it matter if I have extra frames at the front or back?]]
   * [[#​do_i_need_a_focus_rail|Do I need a focus rail?]]   * [[#​do_i_need_a_focus_rail|Do I need a focus rail?]]
   * [[#​how_do_i_figure_out_what_aperture_setting_and_step_size_to_use|How do I figure out what aperture setting and step size to use?]]   * [[#​how_do_i_figure_out_what_aperture_setting_and_step_size_to_use|How do I figure out what aperture setting and step size to use?]]
Line 50: Line 58:
   * [[#​my_colors_changed_a_little_why_is_that|My colors changed a little. ​ Why is that?]]   * [[#​my_colors_changed_a_little_why_is_that|My colors changed a little. ​ Why is that?]]
   * [[#​why_do_my_images_look_noisy_as_soon_as_i_load_them_into_zerene_stacker|Why do my images look noisy as soon as I load them into Zerene Stacker?]]   * [[#​why_do_my_images_look_noisy_as_soon_as_i_load_them_into_zerene_stacker|Why do my images look noisy as soon as I load them into Zerene Stacker?]]
 +  * [[#​part_of_my_subject_looks_transparent_what_can_i_do|Part of my subject looks transparent. What can I do?]]
   * [[#​how_should_i_set_the_alignment_options|How should I set the Alignment options?]]   * [[#​how_should_i_set_the_alignment_options|How should I set the Alignment options?]]
   * [[#​what_do_the_percentages_mean_for_alignment_parameters|What do the percentages mean for Alignment parameters?​]]   * [[#​what_do_the_percentages_mean_for_alignment_parameters|What do the percentages mean for Alignment parameters?​]]
   * [[#​what_is_the_difference_between_pmax_and_dmap|What is the difference between PMax and DMap?]]   * [[#​what_is_the_difference_between_pmax_and_dmap|What is the difference between PMax and DMap?]]
   * [[#​how_should_i_choose_those_dmap_settings|How should I choose those DMap Settings?]]   * [[#​how_should_i_choose_those_dmap_settings|How should I choose those DMap Settings?]]
 +  * [[#​what_is_slabbing|What is "​slabbing"?​]]
   * [[#​should_i_sharpen_before_or_after_running_zerene_stacker|Should I sharpen before or after running Zerene Stacker?]]   * [[#​should_i_sharpen_before_or_after_running_zerene_stacker|Should I sharpen before or after running Zerene Stacker?]]
   * [[#​how_can_i_detect_movement_in_my_stack|How can I detect movement in my stack?]]   * [[#​how_can_i_detect_movement_in_my_stack|How can I detect movement in my stack?]]
   * [[#​why_did_the_software_reverse_the_order_of_my_images|Why did the software reverse the order of my images?]]   * [[#​why_did_the_software_reverse_the_order_of_my_images|Why did the software reverse the order of my images?]]
   * [[#​can_i_directly_control_the_order_that_images_are_processed|Can I directly control the order that images are processed?​]]   * [[#​can_i_directly_control_the_order_that_images_are_processed|Can I directly control the order that images are processed?​]]
 +  * [[#​my_stack_got_shot_out_of_order_what_can_i_do|My stack got shot out of order. ​ What can I do?]]
   * [[#​why_do_my_saved_output_images_look_washed_out|Why do my saved output images look washed out?]]   * [[#​why_do_my_saved_output_images_look_washed_out|Why do my saved output images look washed out?]]
   * [[#​what_does_retain_extended_dynamic_range_mean|What does "​Retain extended dynamic range" mean?]]   * [[#​what_does_retain_extended_dynamic_range_mean|What does "​Retain extended dynamic range" mean?]]
Line 64: Line 75:
   * [[#​are_there_settings_to_make_stacks_process_faster|Are there settings to make stacks process faster?]]   * [[#​are_there_settings_to_make_stacks_process_faster|Are there settings to make stacks process faster?]]
   * [[#​why_does_the_program_complain_that_my_images_are_different_sizes|Why does the program complain that my images are different sizes?]]   * [[#​why_does_the_program_complain_that_my_images_are_different_sizes|Why does the program complain that my images are different sizes?]]
 +  * [[#​when_do_options_preferences_values_get_saved_and_reloaded|When do Options > Preferences values get saved and reloaded?]]
 +  * [[#​how_do_i_abort_an_operation_in_progress?​|How do I abort an operation in progress?]]
  
 **Retouching** **Retouching**
  
   * [[#​what_are_some_tips_for_fast_retouching|What are some tips for fast retouching?​]]   * [[#​what_are_some_tips_for_fast_retouching|What are some tips for fast retouching?​]]
-  * [[#​what_are_the_different_brush_types_for_retouching?|What are the different brush types for retouching?​]]+  * [[#​what_are_the_different_brush_types_for_retouching|What are the different brush types for retouching?]] 
 +  * [[#​sometimes_i_see_noise_getting_added_when_I_retouch_why_is_that|Sometimes I see noise getting added when I retouch. ​ Why is that?]] 
 +  * [[#​i_did_not_save_a_project_can_i_retouch_anyway|I did not save a project. Can I retouch anyway?]]
  
 **Miscellaneous** **Miscellaneous**
  
 +  * [[#​this_program_has_a_lot_of_options_is_there_a_user_s_manual]|This program has a lot of options! ​ Is there a user's manual?]]
   * [[#​do_you_have_a_user_forum|Do you have a user forum?]]   * [[#​do_you_have_a_user_forum|Do you have a user forum?]]
   * [[#​how_does_zerene_stacker_work_with_lightroom|How does Zerene Stacker work with Lightroom?​]]   * [[#​how_does_zerene_stacker_work_with_lightroom|How does Zerene Stacker work with Lightroom?​]]
-  * [[##​are_there_any_keyboard_shortcuts|Are there any keyboard shortcuts?​]]+  * [[#​are_there_any_keyboard_shortcuts|Are there any keyboard shortcuts?​]]
   * [[#​is_there_some_way_to_turn_off_the_welcome_screen|Is there some way to turn off the welcome screen?]]   * [[#​is_there_some_way_to_turn_off_the_welcome_screen|Is there some way to turn off the welcome screen?]]
   * [[#​is_there_some_way_to_control_those_output_names|Is there some way to control those output names?]]   * [[#​is_there_some_way_to_control_those_output_names|Is there some way to control those output names?]]
Line 80: Line 96:
   * [[#​the_zerene_stacker_icon_--_what_is_it|The Zerene Stacker icon -- what is it?]]   * [[#​the_zerene_stacker_icon_--_what_is_it|The Zerene Stacker icon -- what is it?]]
   * [[#​i_need_to_report_a_problem_are_there_log_files_i_can_send_you|I need to report a problem. Are there log files I can send you?]]   * [[#​i_need_to_report_a_problem_are_there_log_files_i_can_send_you|I need to report a problem. Are there log files I can send you?]]
 +
 +===== Do you have a free trial? =====
 +
 +Yes, there is a free 30-day trial. ​
 +
 +The software downloads from [[https://​zerenesystems.com/​cms/​stacker/​softwaredownloads]] . 
 +
 +When first installed, it runs in free trial mode, which provides full functionality for 30 days from first execution. ​ After that, the software will still run but screen images are watermarked and saving images and projects is disabled. ​ At any time, installation of a purchased license key will unlock the software for permanent use.
 +
 +By default, the technical features in trial mode are identical to those that would continue to be provided by a Personal Edition license key.  Advanced features that require a Prosumer Edition or Professional Edition license key are also available, and provide a popup message letting you know that a Pro-only feature has been used.
  
 <​html><​a name="​what_are_the_differences_between_personal_and_professional"</​a></​html>​ <​html><​a name="​what_are_the_differences_between_personal_and_professional"</​a></​html>​
Line 95: Line 121:
  
   * Preserve all metadata, including EXIF, IPTC, and any Lightroom keywords that have been added by the photographer.   * Preserve all metadata, including EXIF, IPTC, and any Lightroom keywords that have been added by the photographer.
-  * Lightroom plugin+  * Lightroom plugin
 +  * Use dust and hot pixels mask while stacking, to avoid defect trails. 
 +  * Built-in capability for "​slabbing"​. 
 +  * Option to cache first-pass results in DMap, for faster re-stacking with different contrast threshold.
   * Option to honor image files' embedded color profiles in Zerene Stacker'​s own screen displays.   * Option to honor image files' embedded color profiles in Zerene Stacker'​s own screen displays.
-  * Ability to overlap ​I/O with computation for faster operation while stacking. +  * Overlap ​I/O with computation for faster operation while stacking. 
-  * Ability to reduce ​the frequency of screen updates while stacking, for faster operation with deep stacks.+  * Reduce ​the frequency of screen updates while stacking, for faster operation with deep stacks.
   * Additional brush types for retouching.   * Additional brush types for retouching.
   * Multi-step undo when retouching.   * Multi-step undo when retouching.
   * Additional interpolators for improved handling of very sharp source images.   * Additional interpolators for improved handling of very sharp source images.
-  * Integrated controller for the [[http://​www.cognisys-inc.com/​stackshot/​stackshot.php|StackShot automated rail]]  +  * Integrated controller for the StackShot automated rail. 
-  * Ability to ingest ​and stack images while they are being shot with a USB-connected camera.+  * Ingest ​and stack images while they are being shot with a USB- or wireless-connected camera.
   * When retouching, image brightness can be adjusted to facilitate working in unusually dark regions.   * When retouching, image brightness can be adjusted to facilitate working in unusually dark regions.
   * Aligned and brightness-corrected input images can be saved to external files.   * Aligned and brightness-corrected input images can be saved to external files.
 +  * Adjustment parameters can be saved to an external file for plotting or editing.
   * Pixels from each source image that were incorporated into DMap output can be saved as image files.   * Pixels from each source image that were incorporated into DMap output can be saved as image files.
   * Depth map from DMap can be saved as a TIFF file.   * Depth map from DMap can be saved as a TIFF file.
 +  * DMap contrast selection slider can be augmented by mask read from external file.
  
 **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 [[support@zerenesystems.com]] . **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 [[support@zerenesystems.com]] .
Line 119: Line 150:
 Please see [[stacker:​docs:​faqlist?&#​what_are_the_differences_between_personal_prosumer_and_professional|"​What are the differences between Personal, Prosumer, and Professional?"​]] for a list of all the Pro-only features. Please see [[stacker:​docs:​faqlist?&#​what_are_the_differences_between_personal_prosumer_and_professional|"​What are the differences between Personal, Prosumer, and Professional?"​]] for a list of all the Pro-only features.
  
-===== Do you have a free trial? =====+===== Can I test Professional and Prosumer options in trial? =====
  
-Yes, there is a free 30-day trial. ​+Yes, all of the Professional and Prosumer options are available during the free 30-day trial.
  
-The software downloads from [[https://​zerenesystems.com/​cms/​stacker/​softwaredownloads]] ​+In trial, the program'​s default settings are the same as for Personal and Student Editions 
  
-When first installedit runs in free trial mode, which provides full functionality for 30 days from first execution. ​ After that, the software will still run but screen images are watermarked and saving images and projects is disabled. ​ At any time, installation of purchased ​license key will unlock ​the software for permanent use.+Soto see exactly how Prosumer or Professional Edition ​license key would behave, you'll need to check-mark ​the following settings explicitly:
  
-By default, the technical features in trial mode are identical to those that would continue ​to be provided by a Personal Edition license key.  ​Advanced features that require a Prosumer Edition or Professional Edition license key are also available, and provide a popup message letting you know that a Pro-only ​feature has been used.+  * Options > Preferences > Image Saving > "Copy metadata from source images ​to saved output images"​ 
 +  * Options > Preferences > Color Management > "Use input file profiles for ZS screen displays"​ 
 +  * Options > Preferences > Multiprocessing > "​Overlap I/O with computation if possible"​ 
 +  * Options > Preferences > Caching & Undo > "​Enable advanced undo"​ 
 + 
 +===== Can the Pro-only warnings ​be turned off? ===== 
 + 
 +Sure -- just click "Yes, and please don't ask again" when responding to any one of them.  ​Or at any time you can go to Options > Preferences > Look & Feel, scroll down, and put checkmark on "​Silently start trials of Pro-only ​features." ​  
 + 
 +Warnings can be resumed by removing the checkmark on that "​Silently start trials"​ option.
  
 ===== Are program updates free? ===== ===== Are program updates free? =====
  
 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. ​ 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. ​
 +
 +===== How do I learn about program updates? =====
 +
 +The gold standard method is to visit the [[https://​zerenesystems.com/​cms/​stacker/​softwaredownloads|Downloads page]] and compare the Build number that is shown there against whatever is shown at Help > About Zerene Stacker in your installed version.
 +
 +With default settings and a connection to the internet, Zerene Stacker will check for important updates every time it is launched, and notify you if one is available. ​ You can also use Help > Check For Update to perform this check manually. ​ Minor updates are sometimes not announced using these methods, even though they can be seen and obtained on the Downloads page as noted above.
  
 ===== Do I have to pay more to get 64-bit mode? ===== ===== Do I have to pay more to get 64-bit mode? =====
Line 159: Line 205:
 ===== How do I download and install the program? ===== ===== How do I download and install the program? =====
  
-The latest regular release of Zerene Stacker is always posted on our [[http://​zerenesystems.com/​cms/​stacker/​softwaredownloads|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 latest regular release of Zerene Stacker is always posted on our [[http://​zerenesystems.com/​cms/​stacker/​softwaredownloads|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 move it anywhere you like, typically ​into your Applications folder.  On Mac, this move should be done using drag-and-drop inside Finder.
  
 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. 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.
Line 169: Line 215:
 ===== How can I update the program? ===== ===== How can I update the program? =====
  
-Program updates are posted as new installers, on the regular [[http://​zerenesystems.com/​cms/​stacker/​softwaredownloads|Downloads]] and [[http://​zerenesystems.com/​cms/​stacker/​softwaredownloads/​currentbeta|Beta Downloads]] pages.+Program updates are posted as new installers, on the regular [[https://​zerenesystems.com/​cms/​stacker/​softwaredownloads|Downloads]] and [[https://​zerenesystems.com/​cms/​stacker/​softwaredownloads/​currentbeta|Beta Downloads]] pages.
  
 Just visit one of those pages and download the appropriate version for your type of computer. Just visit one of those pages and download the appropriate version for your type of computer.
Line 177: Line 223:
 On Windows, installing the new version will automatically replace the old version. 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.+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.  If you have created a Dock icon for the old version, you should remove that also, and re-create it for the new version.  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.
  
  
Line 187: Line 233:
  
 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. 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.
 +
 +===== I upgraded my computer and now Zerene Stacker won't run.  What can I do? =====
 +
 +Almost always this happens on Mac, when macOS has been updated in some way that breaks old builds of Zerene Stacker.
 +
 +The problem should be fixed by un-installing Zerene Stacker and re-installing a fresh copy that has been downloaded from https://​zerenesystems.com/​cms/​stacker/​softwaredownloads .  ​
 +
 +Detailed instructions for doing this can be read at [[https://​zerenesystems.com/​cms/​stacker/​support/​knownissues#​macintosh_macos_monterey_application_silently_fails_to_launch|Known Issue: Macintosh application silently fails to launch]].
 +
 +Note that if your new computer has more memory than your old one did, then you may also need to reset the memory allocation to take advantage of it.  Detailed instructions for that can be read at [[https://​zerenesystems.com/​cms/​stacker/​support/​knownissues#​added_physical_memory_is_not_seen_by_zerene_stacker|Known Issue: added physical memory is not seen by Zerene Stacker]].
 +
 +===== I'm trying to re-install my license key, but it won't work.  What can I do? =====
 +
 +There are two common reasons that a license key won't work.  The first is that some portion of the license key has been omitted from the copy/​paste. ​ Each Zerene Stacker license key is long and complicated,​ typically 17 lines including the BEGIN and END lines. ​ If any portion of the key is not included, the key will be rejected. ​ The second is that the key has been slightly modified during the process of being saved and retrieved. ​ The key must be entered exactly correct, including upper/lower case and all punctuation,​ or it will not be accepted. Keys are almost impossible to enter correctly by typing. ​ Often they will not even survive being passed through a "​smart"​ word processing program or PDF writer. ​ Such programs often make slight changes to punctuation,​ so small that they are difficult or impossible to see by eye, but still these changes make the license key not valid.  ​
 +
 +So, when you save a copy of the license key, it is best to either save an exact copy of the email in which it came, or a plain text copy of the key.  From these formats you can then use copy/paste to enter the license key into Zerene Stacker, as described **[[:​stacker:​docs:​howtoinstallalicensekey|HERE]]**.
 +
 +To recover from problems with a license key, the simplest approach is to send email to support@zerenesystems.com .  We can use your email address or other information to find the key in our own records, and then we'll send you a fresh copy to install and save on your computer.
 +
 +===== I lost my license key.  What can I do?  =====
 +
 +This question is often asked by people who have purchased a new computer and are trying to install Zerene Stacker on it.  In that case if your old computer still works, then you can recover your license key by running Zerene Stacker there, going to Options > Registration,​ then using right-click Select All and right-click Copy to put the license key on the computer'​s clipboard. ​ Paste that into an email or plain text document for transfer to your new computer, install it as described **[[:​stacker:​docs:​howtoinstallalicensekey|HERE]]**,​ and you should be good to go.
 +
 +If that path is not available but you still have email archives, then you can search for a message containing the lines "==== BEGIN LICENSE KEY ====" and "​Software Name: Zerene Stacker 1.0"​. ​ Those two lines have been present in every Zerene Stacker license key ever issued, and they always get delivered by email. ​ (See **[[:​stacker:​docs:​howtoinstallalicensekey|HERE]]**. for an example of the full format.)
 +
 +Alternatively,​ you can write email to [[support@zerenesystems.com]],​ tell us that you've lost your license key, and give us whatever information you remember about the purchase. ​ If you know an exact email address then that's the best info, but we can also work with name and physical address. ​ We'll use that information to find your license key in our records, and send you a fresh copy and instructions for what to do with it.
 +
 ===== Do you have a "beta test" channel? ===== ===== Do you have a "beta test" channel? =====
  
Line 238: Line 311:
 ===== How do I save images as TIFF or JPEG? ===== ===== How do I save images as TIFF or JPEG? =====
  
-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).  ​+You need to use File > Save Output ​Image(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 [[http://​zerenesystems.com/​cms/​stacker/​docs/​howtouseit#​saving_work_in_a_project|Saving Work In A "​Project"​]] for more discussion about that. 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 [[http://​zerenesystems.com/​cms/​stacker/​docs/​howtouseit#​saving_work_in_a_project|Saving Work In A "​Project"​]] for more discussion about that.
 +
 +If you have used File > Save Project and then left Zerene Stacker, you can quickly recover your work by launching Zerene Stacker again, doing a File > Open Project, and selecting the project folder or the .zsj file inside it.  After the project has been re-opened, you can select one or more images in the Output Images panel and use File > Save Output Image(s) to create TIFF or JPEG.  (Note: either the project folder or the .zsj file may show as a yellow smiling dog icon, depending on what operating system and program settings you're using. ​ If neither one shows the icon, just select the .zsj file anyway.)
  
 ===== Is there some way to save EXIF and other metadata? ===== ===== Is there some way to save EXIF and other metadata? =====
Line 253: Line 328:
 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. 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 [[stacker:​docs:​faqlist?&#​i_see_some_menu_items_labeled_pro_what_does_that_mean|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.+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 [[stacker:​docs:​faqlist?&#​i_see_some_menu_items_labeled_pro_what_does_that_mean|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 if you are using a Prosumer Edition or Professional Edition license key.  It is also 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. 
 + 
 +===== What exactly is a "​project"?​ ===== 
 + 
 +In the computer’s file system, each Zerene Stacker project consists of a folder that contains a "​.zsj"​ file and several subfolders. ​ The .zsj file is the master description for the project. ​ You can look inside it with any text editor. ​ Typical subfolders include "​generatedimages",​ which contains output images in "​.zsy"​ format; "​previewimages",​ which contains cached screen preview images as low quality "​.jpg";​ and so on. 
 + 
 +When using File > Open Project inside Zerene Stacker, the project may appear in a couple of different ways.  Usually it appears as an ordinary folder, so to open the project you must navigate inside the project folder, select the .zsj file, and open that.  However, if Options > Preferences > Look & Feel is set to //not// use "​system native File Choosers",​ then File > Open Project will show the project folder as a single "​yellow smiling dog" icon that can be selected and opened without navigating inside it. 
 ===== Does Zerene Stacker help me to shoot a stack? ===== ===== Does Zerene Stacker help me to shoot a stack? =====
  
-In most cases, no.  Typically you'll shoot a stack either by controlling focus manually, or by using a camera control device such as [[http://​camranger.com/​macro-focusstacking/​|CamRanger]],​ or by tethering your camera and using a program like [[http://controlmynikon.com|ControlMyNikon]] or [[http://controlmycanon.com|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 [[http://​www.cognisys-inc.com/​stackshot/​stackshot.php|StackShot rail]] and you've chosen to use Zerene Stacker'​s own Stackshot control panel for that.+In most cases, no.  Typically you'll shoot a stack either by controlling focus manually, or by using a camera control device such as [[http://​camranger.com/​macro-focusstacking/​|CamRanger]],​ or by tethering your camera and using a program like [[https://tetherscript.com/​controlmynikon-home/​|ControlMyNikon]] or [[https://tetherscript.com/​controlmycanon-home/​|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 [[http://​www.cognisys-inc.com/​stackshot/​stackshot.php|StackShot rail]] and you've chosen to use Zerene Stacker'​s own Stackshot control panel for that.
  
 ===== Does Zerene Stacker correct for changes in magnification as I focus? ===== ===== Does Zerene Stacker correct for changes in magnification as I focus? =====
Line 273: Line 355:
  
 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. 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.
 +
 +===== Does it matter if I have extra frames at the front or back? =====
 +
 +Extra frames are OK.  In fact standard advice is to "start early and end late"​. ​ The reason is because extra frames at the front or back of the stack are not likely to cause any visible issues, but accidentally missing focus can ruin the stack.
 +
 +Frames that do not contain any focused detail will be almost totally ignored. ​ We say "​almost"​ because:
 +  - The first frame in Input Files, as ordered after processing, always serves as the master image for framing and for brightness correction (the functions controlled at Options > Preferences > Alignment).
 +  - The stacking algorithms may pick up a little information from the out-of-focus frames. ​ Typically this just causes a slight increase in pixel noise, but the stacking process may also pick up a slightly less out-of-focus version of the background from frames that do not contain any focused detail. ​ Both of these are more likely with PMax than DMap.
 +  - Time will be spent processing the out-of-focus images, even if no information from them is used in the end.
 +
 +
 ===== Do I need a focus rail? ===== ===== Do I need a focus rail? =====
  
Line 320: Line 413:
 For some hints about how to investigate what's going on, see [[:​stacker:​docs:​faqlist#​how_can_I_detect_movement_in_my_stack|How can I detect movement in my stack?]] For some hints about how to investigate what's going on, see [[:​stacker:​docs:​faqlist#​how_can_I_detect_movement_in_my_stack|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 [[http://​zerenesystems.com/​cms/​stacker/​docs/​tutorials/​tutorial002#​summaryuse_either_method_but_be_sure_to_check_framing|HERE]] for more information on that point.+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", then using File > "​Re-order input files" > "​Reverse order" as necessary to get the desired order before stacking.  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 [[http://​zerenesystems.com/​cms/​stacker/​docs/​tutorials/​tutorial002#​summaryuse_either_method_but_be_sure_to_check_framing|HERE]] for more information on that point
 + 
 +In recent versions of Zerene Stacker, edge streaks can be avoided by checking the box at Options > Preferences > Preprocessing > "Use dust & defects mask", and also checking the box under that to "Avoid edge streaks"​. ​ (For this use, you do not need to provide a dust & defects mask "from file"​.) ​ However, while this option will prevent the introduction of streaks, that region of the result image may still be degraded if the subject has details that were never captured in sharp focus due to the shift in framing. ​ It is better to avoid the shift in framing while the stack is being shot, if possible. ​ For more information about this use of the dust & defects mask, see [[https://​www.photomacrography.net/​forum/​viewtopic.php?​p=260671#​p260671|HERE]].
  
 ===== My output images have worm trails! ​ Why is that? ===== ===== My output images have worm trails! ​ Why is that? =====
Line 328: Line 423:
 If you carefully check your source images, you will find that in each of them there are a few individual spots, one spot for each trail in your output. If you carefully check your source images, you will find that in each of them there are a few individual spots, one spot for each trail in your output.
  
-Those spots will occur at exactly the same pixel coordinates in each source image.+Those spots typically ​occur at exactly the same pixel coordinates in each source image. ​ (In rare cases individual spots may move //​slightly//​ as focus is changed, due to axial shift of the lens's exit pupil.)
  
 The reason that trails appear during the stacking process is this:  Due to magnification changes, jitter, or systematic drift in your focus stepping setup, the subject moves slightly left/​right/​up/​down in each frame. ​ Essentially the subject is moving around with respect to the spots. ​ In order to make a clean rendering, the focus stacking process must correct for the subject movement, so the subject stays in the same place for each frame. ​ But then the spots appear to move around with respect to the subject. ​ To the focus stacking algorithms, the spots look just like sharp detail that should be retained, and so in the final image you see each spot in every position that it ever occupied with respect to the subject. ​ In combination with the human eye's great ability to pick out linear structures, this causes each spot to become a collection of spots that looks like a straight line, a wiggly trail, or something in between, depending on exactly how the jitter and drift behaved in the first place. The reason that trails appear during the stacking process is this:  Due to magnification changes, jitter, or systematic drift in your focus stepping setup, the subject moves slightly left/​right/​up/​down in each frame. ​ Essentially the subject is moving around with respect to the spots. ​ In order to make a clean rendering, the focus stacking process must correct for the subject movement, so the subject stays in the same place for each frame. ​ But then the spots appear to move around with respect to the subject. ​ To the focus stacking algorithms, the spots look just like sharp detail that should be retained, and so in the final image you see each spot in every position that it ever occupied with respect to the subject. ​ In combination with the human eye's great ability to pick out linear structures, this causes each spot to become a collection of spots that looks like a straight line, a wiggly trail, or something in between, depending on exactly how the jitter and drift behaved in the first place.
Line 336: Line 431:
 The best cure for these problems is to prevent them in the first place. ​ Fixing the problem after the stack has been shot inevitably means guessing about what the pixel values should have been, that were hidden by the spots. ​ So, it's best to clean your sensor and keep it that way.  Warm pixels get worse with long exposures and higher temperatures,​ so the best way to avoid them is to use short exposures by adding light, typically flash. ​ It also helps to avoid Live View mode during actual shooting, if possible, because continuous use of the sensor during Live View causes the sensor to get warmer. The best cure for these problems is to prevent them in the first place. ​ Fixing the problem after the stack has been shot inevitably means guessing about what the pixel values should have been, that were hidden by the spots. ​ So, it's best to clean your sensor and keep it that way.  Warm pixels get worse with long exposures and higher temperatures,​ so the best way to avoid them is to use short exposures by adding light, typically flash. ​ It also helps to avoid Live View mode during actual shooting, if possible, because continuous use of the sensor during Live View causes the sensor to get warmer.
  
-If you cannot avoid dust or warm pixels in the first place, then the second-best approach is to remove them before stacking, using some technique equivalent to batch mode dust removal.  ​This can be done using tools such as Lightroom or Photoshop. ​ You can find a lot of information about this by searching the internet for words like "​remove dust from multiple pictures"​. ​ Alternatively,​ it often works great to paint over the trails by retouching, either inside Zerene Stacker using Edit > Retouching, or outside Zerene Stacker using something like Photoshop'​s healing brush or clone tool.+If you cannot avoid dust or warm pixels in the first place, then the second-best approach is to remove them before stacking, using some technique equivalent to batch mode dust removal.  ​ 
 + 
 +In recent versions of Zerene Stacker, dust trails ​can be avoided by preparing a mask image that shows Zerene Stacker where spots should be removed, then checking the box at Options > Preferences > Preprocessing > “Use dust & defects mask”, and providing the name and folder path of the mask image. ​ The mask image must be the same size and orientation as the source images, with black dots on a pure white background. ​ For an extended discussion of how to create and use a dust and defects mask, see [[https://​www.photomacrography.net/​forum/​viewtopic.php?​t=41343]] .  NOTE: That discussion is a long thread that currently spans 4 pages in the standard forum layout. ​ Be sure to read all pages because some important information does not appear on the first page.  Also note that in Zerene Stacker, the dust & defects mask is a [[:​stacker:​docs:​faqlist#​i_see_some_menu_items_labeled_pro_what_does_that_mean|Pro-only feature]]. ​  
 + 
 +Dust and defect removal can also be done   
 +using tools such as Lightroom or Photoshop. ​ You can find a lot of information about this by searching the internet for words like "​remove dust from multiple pictures"​. ​ Alternatively,​ it often works great to paint over the trails by retouching, either inside Zerene Stacker using Edit > Retouching, or outside Zerene Stacker using something like Photoshop'​s healing brush or clone tool.
  
 ===== My colors changed a little. ​ Why is that? ===== ===== My colors changed a little. ​ Why is that? =====
  
-There are three common reasons that saved 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.+There are three common reasons that saved 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.  (The changes are affected by the setting at Options > Preferences > PMax Settings > "Use all color channels in decisions",​ so if you see troublesome changes, try that setting both ways.) ​ "​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.
  
 These sorts of color/​brightness/​contrast changes in the saved images 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. These sorts of color/​brightness/​contrast changes in the saved images 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.
Line 351: Line 451:
 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 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 lack of anti-aliasing can also result in Zerene Stacker'​s screen displays showing other artifacts, notably moiré patterns in areas that have fine regular texture such as fabric weave or insect eyes. 
 + 
 +All these effects ​can be worrisome when you first notice ​them.  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. 
 + 
 + 
 +===== Part of my subject looks transparent. What can I do? ===== 
 + 
 +There'​s a whole separate page that addresses this problem. 
 + 
 +See [[https://​zerenesystems.com/​cms/​stacker/​docs/​tutorials/​stackselectedfortransparentforeground|"​Using Stack Selected to Retouch Transparent Foreground"​]] . 
  
 ===== How should I set the Alignment options? ===== ===== How should I set the Alignment options? =====
Line 365: Line 475:
 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. 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 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 [[https://​www.photomacrography.net/​forum/​viewtopic.php?​p=79878#​79878]].
  
 ===== What do the percentages mean for Alignment parameters? ===== ===== What do the percentages mean for Alignment parameters? =====
Line 379: Line 489:
 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. 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 [[http://​zerenesystems.com/​cms/​stacker/​docs/​howtouseit|Zerene Stacker: How To Use It]] page.+For further discussion of these issues, see "DMap versus PMax" on the [[http://​zerenesystems.com/​cms/​stacker/​docs/​howtouseit|Zerene Stacker: How To Use It]] page, and also the "How To Use DMap" and video retouching tutorials, all linked on the main [[https://​zerenesystems.com/​cms/​stacker/​docs/​tutorials/​tutorialsindex|Tutorials index page]].
  
 ===== How should I choose those DMap Settings? ===== ===== How should I choose those DMap Settings? =====
Line 406: Line 516:
  
 **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! **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!
 +
 +===== What is "​slabbing"​ ? =====
 +
 +Slabbing is a technique for making it easier to work with stacks that contain large numbers of images. The concept of slabbing is that you split your stacking into two big steps. ​ In the first step you might reduce say 200 original source images to 30 intermediate images, by stacking sets of 10-15 photos each, with some overlap between sets.  Then in the second step you stack the 30 intermediate images, the "slab outputs",​ to produce an image with the full stack combined. ​
 +
 +When you retouch with slabbing, typically you only have to reach back to the intermediate images, instead of all the way back to each of the original source images. ​ In the example, that means retouching from a set of only 30 images instead of 200.
 +
 +Slabbing can also be very helpful if you need to explore a variety of settings for the DMap parameters. ​ In this scenario you would generate the slab outputs using the PMax stacking method, then stack the slabs using DMap.  The gain here is much faster computation for the stacking, because DMap only needs to work with the much smaller number of slab outputs, instead of all the original source images individually.
 +
 +For more information about slabbing, see [[slabbing|HERE]].
 + 
  
 ===== Should I sharpen before or after running Zerene Stacker? ===== ===== Should I sharpen before or after running Zerene Stacker? =====
Line 412: Line 533:
  
 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 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.
 +
 ===== How can I detect movement in my stack? ===== ===== How can I detect movement in my 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.  ​+The easiest way is to "​play"​ the stack as if 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.  ​ 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.  ​
Line 433: Line 555:
  
 By removing the checkmark on "​Automatic order" and adding files one at a time, you can set exactly any order that you want.  By removing the checkmark on "​Automatic order" and adding files one at a time, you can set exactly any order that you want. 
 +
 +===== My stack got shot out of order. ​ What can I do? =====
 +
 +In many cases there'​s a simple trick that handles this problem.
 +
 +The trick is this: after you've processed the stack at least once, so that all the images have been aligned against each other, then do a File > "​Re-order input files" > "Sort by Scale"​. If the files were originally not in strict focus order, chances are they will be in strict focus order after the sort is done. Then you can do another Stack operation to take advantage of the improved ordering. In especially difficult cases, it may help to do the steps of stacking and "Sort by Scale" a couple of times, to give the software the best opportunity to accurately calculate scale.
 +
 +To understand how the trick works, first note that with most optics, the image changes size along with focus. Depending on the lens, the image might get smaller or larger as focus moves back, but it's probably only going to do one of those, and it will do it consistently and by a large enough amount to be reliably determined by the computational alignment process. Fortunately,​ the alignment process can usually determine scale accurately even when the images are initially out of order, and then sorting by the recovered scale puts them back into order again.
 +
 +The nice thing about "Sort by Scale" is that it doesn'​t require much thinking or mouse-clicking. The alternative is to figure out by eye what the focus order was, then manually add files into the stacking software one at a time or in appropriate groups to get the correct ordering. ​ Alternatively,​ some people rename their image files so as to be in focus order when sorted by name.
  
 ===== Why do my saved output images look washed out? ===== ===== Why do my saved output images look washed out? =====
Line 441: Line 573:
 ===== What does "​Retain extended dynamic range" mean? ===== ===== What does "​Retain extended dynamic range" mean? =====
  
-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.+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"​.  ​In rare cases, even the normal interpolation process used for image alignment can generate pixel values ​that are outside the normal range of black to white, and in that case DMap can be affected also.  Regardless of their origin, values that are outside the normal range of black to white 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 ​or darkens ​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. 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.
Line 465: Line 597:
   * In a vertical setup, if the camera is set to auto-rotate,​ then sometimes the camera will switch randomly between landscape and portrait orientations. ​ In this case the images are different "​sizes"​ because their widths and heights don't match, even though the total number of pixels is the same.  The best fix is to set the camera so as to turn off the auto-rotate option. ​ However, stacks that have this difficulty often can be processed by setting Zerene Stacker so that Options > Preferences > Preprocessing > "​Ignore EXIF orientation"​ is checkmarked.   * In a vertical setup, if the camera is set to auto-rotate,​ then sometimes the camera will switch randomly between landscape and portrait orientations. ​ In this case the images are different "​sizes"​ because their widths and heights don't match, even though the total number of pixels is the same.  The best fix is to set the camera so as to turn off the auto-rotate option. ​ However, stacks that have this difficulty often can be processed by setting Zerene Stacker so that Options > Preferences > Preprocessing > "​Ignore EXIF orientation"​ is checkmarked.
  
-  * If a stack is preprocessed as HDR, combining multiple camera frames to produce HDR source frames that are then fed to Zerene Stacker, then the HDR process often produces outputs that are slightly different sizes. This happens because of the HDR process'​s own alignment procedure, combined with image noise or slight jitter in the stack acquisition. ​ In this case the best fix is to set Options > Preferences > Preprocessing > "Image Pre-cropping"​ to be the size of the smallest ​image produced by the HDR process. ​ Often this will be the same size as the original camera images, but with some HDR software ​it may be smaller.+  * If a stack is preprocessed as HDR, combining multiple camera frames to produce HDR source frames that are then fed to Zerene Stacker, then the HDR process often produces outputs that are slightly different sizes. This happens because of the HDR process'​s own alignment procedure, combined with image noise or slight jitter in the stack acquisition. ​ In this case the best fix is to set Options > Preferences > Preprocessing > "Image Pre-cropping"​ to be the smallest ​width and smallest height that appear in images ​produced by the HDR process. ​ Often these will be the same size as the original camera images, but with some HDR software ​the dimensions ​may be smaller.  Note that the smallest width and smallest height may occur on different images.
  
-  * If a stack is shot as raw, then very rarely, some raw conversion software will make slight changes in the image size apparently at random. ​ Again, a good fix is to set Options > Preferences > Preprocessing > "Image Pre-cropping"​ to be the size of the smallest image produced by raw conversion.+  * If a stack is shot as raw, then very rarely, some raw conversion software will make slight changes in the image size apparently at random. ​ Again, a good fix is to set Options > Preferences > Preprocessing > "Image Pre-cropping"​ to be the size of the smallest image produced by raw conversion.  As an alternative,​ try turning off distortion correction in your raw converter. ​ Lens distortion can change with focus, prompting the raw converter to output slightly different image sizes. 
 + 
 +===== When do Options > Preferences values get saved and reloaded? ===== 
 + 
 +Whenever the program exits, it writes current preferences to a configuration file, named "​zerenstk.cfg"​. ​ The next time the program is launched, it reads those saved preferences from zerenstk.cfg .  All preference values that relate to stacking, file formats, etc. are also written to each project file (*.zsj) that is created or updated by File > Save Project. ​ Whenever a project is reloaded by File > Open Project, all the preferences of that project also become the current preferences of the program. ​ So, when the program exits after reloading a project, the preferences that are saved to zerenstk.cfg will be the values belonging to that project, not whatever preferences were set before the project was reloaded. ​ Preferences can also be explicitly saved and restored, independent of any project, by using the "Save preferences..."​ and "Load preferences..."​ buttons in the Options > Preferences panel. 
 + 
 +Most of the time, you can just ignore all these details and the program will do what you expect it to do. 
 + 
 +However, there are a few situations where the program'​s handling of preferences can produce unpleasant confusion. ​  
 + 
 +Perhaps the most common one is when you've been doing some stacking, then you reload an old project for whatever reason, then you start a new project without realizing that the old project had different preference settings and now you're using those again! ​ If you frequently change preferences and reload old projects, then it's probably good to get in the habit of explicitly saving and loading preferences by using the buttons in the Preferences panel. 
 + 
 +Another situation that can cause confusion is if you run multiple copies of Zerene Stacker at the same time. In that case only the last one that exits will save preferences that get loaded on the next launch. ​ This is because all the other copies do save their preferences on exit, but then those get overwritten by each other copy that exits later. 
 + 
 +===== How do I abort an operation in progress? ===== 
 + 
 +When the progress bar appears, there is a button next to it labeled "​Cancel this operation"​. ​ Click that, and immediately a popup will appear that asks whether you're sure.  In that popup, click the button labeled "Yes, abort"​. ​ The popup will immediately disappear, but it may take some seconds for Zerene Stacker to internally reach a point where it can stop cleanly. ​ When it does, it will produce a confirmation popup, "​Operation stopped by user request"​. 
 + 
 +There are a few circumstances where you have to do this more than once, because the code does not remember the abort and starts a second operation after the first is aborted. ​ One example is if you Align & Stack All (Both) and abort the PMax.  Another is if the stack is not yet aligned, and you do a Stack Selected, then change your mind and abort while the align all frames is happening. In each case, just repeat the process.
  
 ===== What are some tips for fast retouching? ===== ===== What are some tips for fast retouching? =====
Line 484: Line 634:
  
 The Darken and Lighten brushes are like the Pixels brush, except that they only copy pixel values if that copy will make the target get darker or lighter, respectively. ​ This is occasionally handy when retouching small isolated features such as the bristles of an insect. The Darken and Lighten brushes are like the Pixels brush, except that they only copy pixel values if that copy will make the target get darker or lighter, respectively. ​ This is occasionally handy when retouching small isolated features such as the bristles of an insect.
 +
 +===== Sometimes I see noise getting added when I retouch. ​ Why is that? =====
 +
 +This effect can occur when you retouch from a PMax output into a DMap output. ​ As explained in [[:​stacker:​docs:​faqlist#​what_is_the_difference_between_pmax_and_dmap|another FAQ]], PMax output is generally noisier than DMap output. ​ Often this difference is overlooked when you are looking at just one or the other, or even side-by-side. ​ But when you retouch from PMax into DMap, the greater noise of PMax is carried over, and that's when it becomes obvious, seen against the quieter surrounding areas made by DMap.
 +
 +There are a couple of ways to reduce this problem. ​ First is to always shoot at the lowest possible ISO, so that your source images will have as little pixel noise as possible. ​ Second is to retouch in the smallest possible areas, typically only where DMap has messed up the handling of front/back overlap between two focused parts of the subject. ​ DMap will almost always give a better rendition of background and of foreground edges seen against unfocused background, so those areas usually should not be retouched from PMax.
 +
 +===== I did not save a project. ​ Can I retouch anyway? =====
 +
 +Yes, in most cases. ​ But the process is cumbersome, so it's better to use File > Save Project and File > Open Project as intended.
 +
 +In detail, the process goes like this:
 +  - Open or re-create a project that has source images in the same alignment that produced the image you want to retouch.
 +  - Go to Options > Preferences > Preprocessing,​ and put a checkmark on the option to "Add files to existing project as already aligned"​.
 +  - Add the image that you want to retouch, into the Input Files panel. ​ You can do this by either drag-and-drop or File > Add File(s).
 +  - Be sure the project has as least one output image. ​ Create one by stacking, if necessary.
 +  - Select any output image.
 +  - Edit > Start Retouching.
 +  - Set scale to "Fit window"​.
 +  - Position the retouching brush in the center of the image, then resize it big enough to cover the entire image at one time.
 +  - Click once, to replace all pixels in the placeholder with pixels from the image that you really want to retouch. ​ The "​Current Retouched Image" will then be equal to the image you want to retouch, just as if it would have been if selected from the Output Images panel.
 +  - Resize the retouching brush to be a normal small size.
 +  - Proceed with retouching as you originally intended.
 +
 +===== This program has a lot of options! ​ Is there a user's manual? =====
 +
 +There is no single document that steps through the GUI and explains what each of the items does.
 +
 +However, within the app, if you hover over each of the GUI items, you'll get a pop-up "​tooltip"​ that offers some explanatory language. ​ For example, hovering over "Shift X" at Options > Preferences > Alignment produces the tooltip "If checked, detect and correct for horizontal shift between frames."​
 +
 +Some of the GUI elements are too complicated to be adequately explained this way.  In those cases there is usually some explanation on the website, often augmented by a link into the discussion forums at photomacrography.net .  For example, the checkbox labeled "Dust & defects mask" has a tooltip that is still only suggestive: "If checked, enables replacement of bad pixels as indicated by mask file." ​ However, if you go to the website and use the Search box to look for "dust & defects mask", then you'll be directed to more information. ​ In this case the first hit goes to the faqlist page, the same place you're reading now, which can also be reached via FAQs in the navigation panel. ​ Here, browser search for "​dust"​ quickly finds several mentions, two of which point to a four-page discussion at [[https://​www.photomacrography.net/​forum/​viewtopic.php?​t=41343]].
 +
 +Finally, if all of the above process fails to find an adequate explanation,​ then the ultimate fallback is to write for help from [[support@zerenesystems.com]]. ​ In that case we'll either locate an existing explanation and link it better, or write a new one that might be found by other people also.
 +
 +To quickly summarize: hover for tooltip; search website; follow links as indicated; write to support for more information.  ​
 +
 +We hope this helps!
 +
  
 ===== Do you have a user forum? ===== ===== Do you have a user forum? =====
Line 529: Line 717:
 To locate log and configuration files, proceed as follows: To locate log and configuration files, proceed as follows:
   * On Windows, do a Start > Run on the Windows taskbar. ​ In the little window that pops up, specify to Open: "​%APPDATA%\ZereneStacker"​ (omit the quotes, and no space in the name). ​ Click OK.  This will open a file explorer window showing the ZereneStacker folder in your user area. \\ \\ On Windows 10, usually it is not possible to open the Start > Run dialog. ​ Instead, you can open a File Explorer window, then in that window'​s address bar, type in %APPDATA%\ZereneStacker and hit the Enter key. Searching Windows for %APPDATA%\ZereneStacker will also work.  \\ \\ On some systems, it is also necessary to set the folder view options to "Show hidden files, folders, and drives"​. ​ See for example [[http://​www.windows10themes.net/​guides/​how-to-view-the-appdata-folder-in-windows-10/​]] \\ \\   * On Windows, do a Start > Run on the Windows taskbar. ​ In the little window that pops up, specify to Open: "​%APPDATA%\ZereneStacker"​ (omit the quotes, and no space in the name). ​ Click OK.  This will open a file explorer window showing the ZereneStacker folder in your user area. \\ \\ On Windows 10, usually it is not possible to open the Start > Run dialog. ​ Instead, you can open a File Explorer window, then in that window'​s address bar, type in %APPDATA%\ZereneStacker and hit the Enter key. Searching Windows for %APPDATA%\ZereneStacker will also work.  \\ \\ On some systems, it is also necessary to set the folder view options to "Show hidden files, folders, and drives"​. ​ See for example [[http://​www.windows10themes.net/​guides/​how-to-view-the-appdata-folder-in-windows-10/​]] \\ \\
-  * On Mac OS X, use Finder to navigate to your home directory, and from there to your home directory'​s Library/​Preferences/​ZereneStacker. ​ \\ Note that the required directory is //not// in the /​Library/​Preferences that hangs off the root of your computer'​s disk.  Instead it is the one located in your own home directory, **~**/​Library/​Preferences. ​ In modern versions of Mac OS X ("​Lion"​ and later), your own Library folder is normally hidden in Finder. ​ To see into it, simply click the Go menu in Finder, then press and hold the Option (Alt) key to add Library to the list of available folders (as shown [[http://​osxdaily.com/​2016/​12/​12/​show-user-library-folder-macos-sierra/​|HERE]]). ​ Continue holding the Option key while you click on Library to view its contents, then double-click to open the Preferences folder and then the ZereneStacker folder.+  * On Mac OS X, use Finder to navigate to your home directory, and from there to your home directory'​s Library/​Preferences/​ZereneStacker. ​ \\ Note that the required directory is //not// in the /​Library/​Preferences that hangs off the root of your computer'​s disk.  Instead it is the one located in your own home directory, **~**/​Library/​Preferences. ​ In modern versions of Mac OS X ("​Lion"​ and later), your own Library folder is normally hidden in Finder. ​ To see into it, simply click the Go menu in Finder, then press and hold the Option (Alt) key to add Library to the list of available folders (as shown [[http://​osxdaily.com/​2016/​12/​12/​show-user-library-folder-macos-sierra/​|HERE]]). ​ Continue holding the Option key while you click on Library to view its contents, then double-click to open the Preferences folder and then the ZereneStacker folder. \\ \\ 
 +  * On Linux, navigate to ~/​.ZereneStacker .  That's the normally hidden folder named "​.ZereneStacker",​ hanging off the root of your login account.
  
 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. ​ 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. ​
Line 545: Line 734:
 \\ \\ \\ \\ \\ \\ \\ \\ \\ \\ \\ \\ \\ \\ \\ \\ \\ \\ \\ \\ \\ \\ \\ \\ \\ \\ \\ \\ \\ \\ \\ \\ \\ \\ \\ \\ \\ \\ \\ \\ \\ \\ \\ \\ \\ \\ \\ \\ \\ \\ \\ \\ \\ \\ \\ \\ \\ \\ \\ \\ \\ \\ \\ \\ \\ \\ \\ \\ \\ \\ \\ \\ \\ \\ \\ \\ \\ \\ \\ \\ \\ \\ \\ \\
  
-VPS 
  
stacker/docs/faqlist.txt · Last modified: 2024/03/03 17:26 by rjlittlefield
Copyright 2009-2024, Zerene Systems LLC, all rights reserved.