Differences
This shows you the differences between two versions of the page.
| Both sides previous revision Previous revision Next revision | Previous revision | ||
|
stacker:docs:options:preferences:imagesaving [2020/07/23 21:13] rjlittlefield |
stacker:docs:options:preferences:imagesaving [2022/06/29 05:07] (current) rjlittlefield correct typo |
||
|---|---|---|---|
| Line 13: | Line 13: | ||
| The option to "Retain full dynamic range" controls how PMax outputs are saved. The default, with __no__ checkmark on "Retain full dynamic range", is to save files as they appear on screen. This preserves whatever contrast and brightness the PMax method naturally produces, but it may cause unwanted clipping at black and white if the source files reach near those limits and PMax's intrinsic contrast enhancement pushes them past the limits. Placing a checkmark on "Retain full dynamic range" causes the image's brightness and contrast to be adjusted if necessary to assure that no information is lost by clipping. The resulting image is likely to appear washed out, in which case it will require further levels or curves adjustment to restore whatever appearance you prefer. To get the best results, files saved with "Retain full dynamic range" should be formatted as 16-bit TIFF so that adjustments can be made without introducing posterization artifacts. | The option to "Retain full dynamic range" controls how PMax outputs are saved. The default, with __no__ checkmark on "Retain full dynamic range", is to save files as they appear on screen. This preserves whatever contrast and brightness the PMax method naturally produces, but it may cause unwanted clipping at black and white if the source files reach near those limits and PMax's intrinsic contrast enhancement pushes them past the limits. Placing a checkmark on "Retain full dynamic range" causes the image's brightness and contrast to be adjusted if necessary to assure that no information is lost by clipping. The resulting image is likely to appear washed out, in which case it will require further levels or curves adjustment to restore whatever appearance you prefer. To get the best results, files saved with "Retain full dynamic range" should be formatted as 16-bit TIFF so that adjustments can be made without introducing posterization artifacts. | ||
| - | The bottom section, titled **Output Image Names**, provides a template that controls how Zerene Stacker names output images as they are generated. | + | The bottom section, titled **Output Image Names**, provides a template that controls how Zerene Stacker names output images as they are created and placed into the Output Images list. |
| By default, the output naming template is set to "{datetime} ZS {method}", which produces names like "2011-04-23-15.37.40 ZS PMax". However, you can redefine the template to use any combination of certain //{tagnames}// surrounded by curly braces, as follows. | By default, the output naming template is set to "{datetime} ZS {method}", which produces names like "2011-04-23-15.37.40 ZS PMax". However, you can redefine the template to use any combination of certain //{tagnames}// surrounded by curly braces, as follows. | ||
| Line 19: | Line 19: | ||
| **Note:** To work properly, the tagnames must be surrounded by curly braces {} and not by ordinary parentheses (). These characters look very much alike in certain fonts, so be sure to type carefully. | **Note:** To work properly, the tagnames must be surrounded by curly braces {} and not by ordinary parentheses (). These characters look very much alike in certain fonts, so be sure to type carefully. | ||
| - | * //{datetime}// date and time (in fixed format: YYYY-MM-DD-hh.mm.ss) | + | * //{datetime}// date and time (in fixed format: YYYY-MM-dd-hh.mm.ss) |
| + | * //{datetime://format//}// date and/or time in variable format, as described [[https://docs.oracle.com/javase/7/docs/api/java/text/SimpleDateFormat.html|HERE]]. For example the default {datetime} tag is equivalent to {datetime:YYYY-MM-dd-hh.mm.ss} | ||
| * //{method}// either "PMax" or "DMap" | * //{method}// either "PMax" or "DMap" | ||
| Line 26: | Line 28: | ||
| * //{mininp}// shortest unique minimum number that appears in the names of source frames used for this output. If the image was constructed from input files named IMG_9713 through IMG_9765, then {mininp} will be "13". The file name extension such as ".JPG" or ".TIF" is always ignored. | * //{mininp}// shortest unique minimum number that appears in the names of source frames used for this output. If the image was constructed from input files named IMG_9713 through IMG_9765, then {mininp} will be "13". The file name extension such as ".JPG" or ".TIF" is always ignored. | ||
| - | * //{mininp://#//}// like {mininp}, except that at most only # characters will be truncated from the full file names. If the image was constructed from input files named IMG_9713 through IMG_9765, then {mininp:2} will be "G_9713" instead of just "13". In most cases, {mininp:0} will be the entire name of the first file, "IMG_9713". However, if every one of the input file names has the same string of characters on its trailing end (a "common suffix"), that that string will always be deleted. For example, {mininp:0} of IMG_0001_RustyNail.JPG through IMG_0016_RustyNail.JPG will be simply IMG_0001. At this time there is no way to force a common suffix to be retained. | + | * //{mininp://#//}// like {mininp}, except that at most only # characters will be truncated from the full file names. If the image was constructed from input files named IMG_9713 through IMG_9765, then {mininp:2} will be "G_9713" instead of just "13". In most cases, {mininp:0} will be the entire name of the first file, "IMG_9713". However, if every one of the input file names has the same string of characters on its trailing end (a "common suffix"), then that string will always be deleted. For example, {mininp:0} of IMG_0001_RustyNail.JPG through IMG_0016_RustyNail.JPG will be simply IMG_0001. At this time there is no way to force a common suffix to be retained. |
| * //{maxinp}// similar to {mininp}, except the maximum number. Note that maxinp does not accept a :#chars argument. Instead, {maxinp} inherits the argument from {mininp}, if there is one. Also note that //{mininp}// and //{maxinp}// are designed to work with numbers that have been zero-filled to a constant length, for example "Image-001" through "Image-247" and not "Image-1" through 'Image-247". | * //{maxinp}// similar to {mininp}, except the maximum number. Note that maxinp does not accept a :#chars argument. Instead, {maxinp} inherits the argument from {mininp}, if there is one. Also note that //{mininp}// and //{maxinp}// are designed to work with numbers that have been zero-filled to a constant length, for example "Image-001" through "Image-247" and not "Image-1" through 'Image-247". | ||