Zerene Stacker

Differences

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

stacker:docs:faqlist [2018/07/31 00:45]
rjlittlefield defect trails
stacker:docs:faqlist [2019/03/05 19:40] (current)
rjlittlefield "recent" --> "modern" (for macOS versions
Line 372: Line 372:
 ===== What is the difference between PMax and DMap? ===== ===== What is the difference between PMax and DMap? =====
  
-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.+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.+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. 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.
Line 491: Line 491:
 [[:stacker:docs:keyboardshortcuts|HERE]].   [[:stacker:docs:keyboardshortcuts|HERE]].  
  
-Currently there are no keyboard shortcuts for common operations such as opening and saving files.+Recent versions of Zerene Stacker also have keyboard shortcuts for some common operations such as opening and saving files.  These are identified in the menu system, as usual for whatever type of computer you are using. 
  
 ===== Is there some way to turn off the welcome screen? ===== ===== Is there some way to turn off the welcome screen? =====
Line 499: Line 500:
 ===== Is there some way to control those output names? ===== ===== Is there some way to control those output names? =====
  
-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 **[[:stacker:docs:options:preferences:imagesaving|Options > Preferences > Image Saving]]**; look at the Template field. +You've probably noticed that the default names are based on timestamps, for example "2018-12-01_16.48.14" means 2018 December 01 at 4:48 PM plus 14 seconds (local time zone).  Names like that are 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 **[[:stacker:docs:options:preferences:imagesaving|Options > Preferences > Image Saving]]**; look at the Template field. 
  
 ===== How can I find and remove orphaned files? ===== ===== How can I find and remove orphaned files? =====
Line 521: Line 522:
 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" (note, 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" (note, 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 recent 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.
  
 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 535: Line 536:
 \\ \\ \\ \\ \\ \\ \\ \\ \\ \\ \\ \\ \\ \\ \\ \\ \\ \\ \\ \\ \\ \\ \\ \\ \\ \\ \\ \\ \\ \\ \\ \\ \\ \\ \\ \\ \\ \\ \\ \\ \\ \\ \\ \\ \\ \\ \\ \\ \\ \\ \\ \\ \\ \\ \\ \\ \\ \\ \\ \\ \\ \\ \\ \\ \\ \\ \\ \\ \\ \\ \\ \\ \\ \\ \\ \\ \\ \\ \\ \\ \\ \\
 \\ \\ \\ \\ \\ \\ \\ \\ \\ \\ \\ \\ \\ \\ \\ \\ \\ \\ \\ \\ \\ \\ \\ \\ \\ \\ \\ \\ \\ \\ \\ \\ \\ \\ \\ \\ \\ \\ \\ \\ \\ \\ \\ \\ \\ \\ \\ \\ \\ \\ \\ \\ \\ \\ \\ \\ \\ \\ \\ \\ \\ \\ \\ \\ \\ \\ \\ \\ \\ \\ \\ \\ \\ \\ \\ \\ \\ \\ \\ \\ \\ \\
-\\ \\ \\ \\ \\ \\ \\ \\ \\ \\ \\ \\ \\ \\ \\ \\ \\ \\ \\ \\ \\ \\ \\ \\ \\ \\ \\ \\ \\ \\ \\ \\ \\ \\ \\ \\ \\ \\ \\ \\ \\+\\ \\ \\ \\ \\ \\ \\ \\ \\ \\ \\ \\ \\ \\ \\ \\ \\ \\ \\ \\ \\ \\ \\ \\ \\ \\ \\ \\ \\ \\ \\ \\ \\ \\ \\ \\ \\ \\ \\ \\ \\ \\
  
  
stacker/docs/faqlist.1532997915.gz · Last modified: 2018/07/31 00:45
Copyright 2009-2018, Zerene Systems LLC, all rights reserved.