Differences
This shows you the differences between two versions of the page.
| Both sides previous revision Previous revision Next revision | Previous revision Next revision Both sides next revision | ||
|
stacker:docs:faqlist [2020/04/25 00:07] rjlittlefield fix explicit html anchors to work around dokuwiki bug |
stacker:docs:faqlist [2020/06/05 22:52] rjlittlefield [How can I detect movement in my stack?] |
||
|---|---|---|---|
| Line 241: | Line 241: | ||
| ===== 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. | ||
| Line 417: | Line 417: | ||
| ===== 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. | ||