Differences
This shows you the differences between two versions of the page.
| Both sides previous revision Previous revision | |||
|
stacker:support:knownissues [2026/03/09 05:56] rjlittlefield [Using Capture One raw converter, must turn off option to "Embed Camera Profile"] |
stacker:support:knownissues [2026/05/19 17:38] (current) rjlittlefield |
||
|---|---|---|---|
| Line 8: | Line 8: | ||
| Here is an index to the known issues: | Here is an index to the known issues: | ||
| - | * [[#macos_big_sur_system_preference_for_prefer_tabs_can_hang_zerene_stacker|macOS Big Sur, System Preference for "Prefer tabs" can hang Zerene Stacker.]] | ||
| * [[#license_keys_that_contain_accented_or_non-english_characters_may_get_corrupted_in_email_transmission|License keys that contain accented or non-English characters may get corrupted in email transmission.]] | * [[#license_keys_that_contain_accented_or_non-english_characters_may_get_corrupted_in_email_transmission|License keys that contain accented or non-English characters may get corrupted in email transmission.]] | ||
| * [[#settings_are_retained_across_uninstallreinstall|Settings are retained across uninstall/reinstall.]] | * [[#settings_are_retained_across_uninstallreinstall|Settings are retained across uninstall/reinstall.]] | ||
| Line 25: | Line 24: | ||
| * [[#macintosh_os_x_could_not_establish_communications_with_stackshot_controller|Macintosh OS X, "Could not establish communications with StackShot controller".]] | * [[#macintosh_os_x_could_not_establish_communications_with_stackshot_controller|Macintosh OS X, "Could not establish communications with StackShot controller".]] | ||
| * [[#macintosh_os_x_zerene_stacker_will_work_on_only_one_stack_at_a_time|Macintosh OS X, Zerene Stacker will work on only one stack at a time.]] | * [[#macintosh_os_x_zerene_stacker_will_work_on_only_one_stack_at_a_time|Macintosh OS X, Zerene Stacker will work on only one stack at a time.]] | ||
| - | * [[#macintosh_os_x_mountain_lion_reports_installation_bundle_is_damaged_move_to_trash|Macintosh OS X (Mountain Lion) reports installation bundle is "damaged, move to trash".]] | ||
| * [[#macintosh_os_x_how_to_recover_from_excessive_memory_allocation|Macintosh OS X, how to recover from excessive memory allocation.]] | * [[#macintosh_os_x_how_to_recover_from_excessive_memory_allocation|Macintosh OS X, how to recover from excessive memory allocation.]] | ||
| * [[#macintosh_os_x_tiff_files_may_be_very_slow_to_read|Macintosh OS X, TIFF files may be very slow to read.]] | * [[#macintosh_os_x_tiff_files_may_be_very_slow_to_read|Macintosh OS X, TIFF files may be very slow to read.]] | ||
| Line 41: | Line 39: | ||
| * [[#macintosh_os_x_the_downloaded_bundle_runs_once_but_not_again|Macintosh OS X, the downloaded bundle runs once but not again.]] | * [[#macintosh_os_x_the_downloaded_bundle_runs_once_but_not_again|Macintosh OS X, the downloaded bundle runs once but not again.]] | ||
| * [[#using_capture_one_raw_converter_must_turn_off_option_to_embed_camera_profile|Using Capture One raw converter, must turn off option to "Embed Camera Profile".]] | * [[#using_capture_one_raw_converter_must_turn_off_option_to_embed_camera_profile|Using Capture One raw converter, must turn off option to "Embed Camera Profile".]] | ||
| - | + | * [[#macintosh_os_x_mountain_lion_reports_installation_bundle_is_damaged_move_to_trash|Macintosh OS X (Mountain Lion) reports installation bundle is "damaged, move to trash".]] | |
| - | ===== macOS Big Sur, system preference for "Prefer tabs" can hang Zerene Stacker ===== | + | * [[#macos_big_sur_system_preference_for_prefer_tabs_can_hang_zerene_stacker|macOS Big Sur, System Preference for "Prefer tabs" can hang Zerene Stacker.]] |
| - | + | ||
| - | Beginning with macOS "Big Sur" (macOS 11, also known as 10.16) **it is critical that System Preferences > General > "Prefer tabs: ... when opening documents" must be set to either "never" or "in full screen"**. Further, if you select "in full screen", then do not run Zerene in full screen mode. | + | |
| - | + | ||
| - | These restrictions are because there is a new bug, introduced in macOS Big Sur, that causes Zerene Stacker (and all other Java programs) to display a grossly oversized window and become nonresponsive, whenever the application tries to open a non-blocking dialog. In Zerene Stacker, such dialogs include the DMap contrast threshold slider, the StackShot controller panel, and the DOF and stereo calculators. | + | |
| - | + | ||
| - | The safest setting for "Prefer tabs" is "never". The most dangerous setting is "always", which as of this writing (Feb 2021) will cause Zerene Stacker to hang if it tries to open any of the dialogs listed earlier. | + | |
| - | + | ||
| - | When Zerene Stacker is hung because of this problem, you may not be able to get a Force Quit menu by mouse action. However, the keyboard combination Cmd-Option-Escape will still work to bring up a Force Quit menu, in which you can select Zerene Stacker and then Force Quit it. | + | |
| Line 71: | Line 61: | ||
| {{:stacker:support:knownissues:zerenestackerfolder.png}} | {{:stacker:support:knownissues:zerenestackerfolder.png}} | ||
| - | 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% and hit the Enter key. 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 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% and hit the Enter key. On some systems, it is also necessary to set the folder view options to "Show hidden files, folders, and drives". See for example [[https://www.lifewire.com/find-and-use-the-appdata-folder-in-windows-4771752]] |
| On **Macintosh OS X**, dragging the application bundle to the trash leaves behind some state information in other files and folders, so that reinstalling the program will not restore the program to a factory-fresh condition. To get back to a factory-fresh condition, you must manually remove one folder and the files it contains, before reinstalling. The folder you need to remove is ~/Library/Preferences/ZereneStacker, where ~ denotes your account's home directory. Note that the ~/Library folder is normally hidden. To open it, hold down your keyboard's Option (Alt) key while selecting Go > Library in a Finder window. Once you have the ~/Library folder, then find and go into the Preferences folder. From there, the ZereneStacker folder will be at the bottom of the list, or very close to it. Be careful that you do not remove other folders or files in ~/Library/Preferences, because these contain settings for other programs. | On **Macintosh OS X**, dragging the application bundle to the trash leaves behind some state information in other files and folders, so that reinstalling the program will not restore the program to a factory-fresh condition. To get back to a factory-fresh condition, you must manually remove one folder and the files it contains, before reinstalling. The folder you need to remove is ~/Library/Preferences/ZereneStacker, where ~ denotes your account's home directory. Note that the ~/Library folder is normally hidden. To open it, hold down your keyboard's Option (Alt) key while selecting Go > Library in a Finder window. Once you have the ~/Library folder, then find and go into the Preferences folder. From there, the ZereneStacker folder will be at the bottom of the list, or very close to it. Be careful that you do not remove other folders or files in ~/Library/Preferences, because these contain settings for other programs. | ||
| Line 280: | Line 270: | ||
| The explanation here is that by design, Zerene Stacker is programmed using the "single document" model. This means that each instance of Zerene Stacker can only work with one stack at a time. The normal process of launching Zerene Stacker by clicking its icon will not launch a second instance. Instead, clicking the icon just makes the current instance foreground, apparently in the expectation that all programs are multi-document. Unfortunately there seems to be no way to just tell MacOS that Zerene Stacker is single document and it should launch another instance when the launch icon is clicked. The "-n" argument on the open command says to create a new instance regardless of whether there's already one running. | The explanation here is that by design, Zerene Stacker is programmed using the "single document" model. This means that each instance of Zerene Stacker can only work with one stack at a time. The normal process of launching Zerene Stacker by clicking its icon will not launch a second instance. Instead, clicking the icon just makes the current instance foreground, apparently in the expectation that all programs are multi-document. Unfortunately there seems to be no way to just tell MacOS that Zerene Stacker is single document and it should launch another instance when the launch icon is clicked. The "-n" argument on the open command says to create a new instance regardless of whether there's already one running. | ||
| - | |||
| - | ===== Macintosh OS X (Mountain Lion) reports installation bundle is "damaged, move to trash" ===== | ||
| - | |||
| - | Note: All recent versions of Zerene Stacker are digitally signed in such a way as to avoid this problem. However, we're leaving this description in place in case a similar problem resurfaces at some point. Please let us know if you encounter one.) | ||
| - | |||
| - | The symptom here is that when Mountain Lion finishes downloading a Zerene Stacker application bundle such as ZS-MacOSX-T201207281315.zip, it reports that the file is "damaged" and that you have to "move it to the trash". | ||
| - | |||
| - | In fact, the file is not damaged and it will run fine under Mountain Lion if the download security settings are temporarily changed to "Anywhere". Detailed instructions to accomplish this (for a different product) are provided at [[http://wiki.espeakers.com/index.php/OS_X_Mountain_Lion_installation_instructions]]. | ||
| - | |||
| - | What has happened is that Apple has changed their malware detection to err on the side of caution and report "damaged" unless they can confirm via digital signature that the file is __not__ damaged. | ||
| - | |||
| - | Zerene Stacker distributions prior to ZS-MacOSX-SA-T201207281315.zip were not digitally signed, so they will always trigger the "damaged" message on Mountain Lion or other systems with the same security settings. | ||
| - | |||
| - | Starting with ZS-MacOSX-SA-T201207281315.zip, the distributions are digitally signed and will install without complaint on almost all systems. We have heard of one Mountain Lion installation where even the signed distribution encountered the "damaged" message and it was necessary to use the workaround of temporarily changing the download security settings. | ||
| - | |||
| - | If you need more information about this issue, please contact [[support@zerenesystems.com]] . | ||
| ===== Macintosh OS X, how to recover from excessive memory allocation ===== | ===== Macintosh OS X, how to recover from excessive memory allocation ===== | ||
| Line 444: | Line 418: | ||
| This problem is believed solved in Build T201610272136 (October 2016) and later. | This problem is believed solved in Build T201610272136 (October 2016) and later. | ||
| + | |||
| + | ===== Macintosh OS X (Mountain Lion) reports installation bundle is "damaged, move to trash" ===== | ||
| + | |||
| + | Note: All recent versions of Zerene Stacker are digitally signed in such a way as to avoid this problem. However, we're leaving this description in place in case a similar problem resurfaces at some point. Please let us know if you encounter one.) | ||
| + | |||
| + | The symptom here is that when Mountain Lion finishes downloading a Zerene Stacker application bundle such as ZS-MacOSX-T201207281315.zip, it reports that the file is "damaged" and that you have to "move it to the trash". | ||
| + | |||
| + | In fact, the file is not damaged and it will run fine under Mountain Lion if the download security settings are temporarily changed to "Anywhere". | ||
| + | |||
| + | What has happened is that Apple has changed their malware detection to err on the side of caution and report "damaged" unless they can confirm via digital signature that the file is __not__ damaged. | ||
| + | |||
| + | Zerene Stacker distributions prior to ZS-MacOSX-SA-T201207281315.zip were not digitally signed, so they will always trigger the "damaged" message on Mountain Lion or other systems with the same security settings. | ||
| + | |||
| + | Starting with ZS-MacOSX-SA-T201207281315.zip, the distributions are digitally signed and will install without complaint on almost all systems. We have heard of one Mountain Lion installation where even the signed distribution encountered the "damaged" message and it was necessary to use the workaround of temporarily changing the download security settings. | ||
| + | |||
| + | If you need more information about this issue, please contact [[support@zerenesystems.com]] . | ||
| + | |||
| + | ===== macOS Big Sur, system preference for "Prefer tabs" can hang Zerene Stacker ===== | ||
| + | |||
| + | Beginning with macOS "Big Sur" (macOS 11, also known as 10.16) **it is critical that System Preferences > General > "Prefer tabs: ... when opening documents" must be set to either "never" or "in full screen"**. Further, if you select "in full screen", then do not run Zerene in full screen mode. | ||
| + | |||
| + | These restrictions are because there is a new bug, introduced in macOS Big Sur, that causes Zerene Stacker (and all other Java programs) to display a grossly oversized window and become nonresponsive, whenever the application tries to open a non-blocking dialog. In Zerene Stacker, such dialogs include the DMap contrast threshold slider, the StackShot controller panel, and the DOF and stereo calculators. | ||
| + | |||
| + | The safest setting for "Prefer tabs" is "never". The most dangerous setting is "always", which as of this writing (Feb 2021) will cause Zerene Stacker to hang if it tries to open any of the dialogs listed earlier. | ||
| + | |||
| + | When Zerene Stacker is hung because of this problem, you may not be able to get a Force Quit menu by mouse action. However, the keyboard combination Cmd-Option-Escape will still work to bring up a Force Quit menu, in which you can select Zerene Stacker and then Force Quit it. | ||
| + | |||