Differences
This shows you the differences between two versions of the page.
| Both sides previous revision Previous revision Next revision | Previous revision Last revision Both sides next revision | ||
|
stacker:support:knownissues [2017/06/04 01:11] rjlittlefield |
stacker:support:knownissues [2023/09/08 15:11] rjlittlefield [Macintosh macOS Monterey, application silently fails to launch] |
||
|---|---|---|---|
| Line 1: | Line 1: | ||
| ~~NOTOC~~ | ~~NOTOC~~ | ||
| - | ====== Zerene Stacker Known Issues ====== | + | ===== Zerene Stacker Known Issues ===== |
| Known Issues is a list of unusual problems that can be quite challenging to diagnose and solve from scratch. We keep this list mainly for our own use in providing support, but we're making it publicly available in case it may be useful to other people also. | Known Issues is a list of unusual problems that can be quite challenging to diagnose and solve from scratch. We keep this list mainly for our own use in providing support, but we're making it publicly available in case it may be useful to other people also. | ||
| 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_uninstall_reinstall|Settings are retained across uninstall / reinstall.]] | + | * [[#settings_are_retained_across_uninstallreinstall|Settings are retained across uninstall/reinstall.]] |
| * [[#license_key_must_be_installed_for_each_user_account|License key must be installed for each user account.]] | * [[#license_key_must_be_installed_for_each_user_account|License key must be installed for each user account.]] | ||
| - | * [[#bit_tiff_files_should_be_uncompressed|16-bit TIFF files should be uncompressed]] | + | * [[#bit_tiff_files_should_be_uncompressed|16-bit TIFF files should be uncompressed.]] |
| * [[#certain_grayscale_images_may_cause_incompatible_colormodel|Certain grayscale images may cause "incompatible ColorModel".]] | * [[#certain_grayscale_images_may_cause_incompatible_colormodel|Certain grayscale images may cause "incompatible ColorModel".]] | ||
| * [[#zonealarm_toolbar_may_significantly_reduce_available_memory|ZoneAlarm Toolbar may significantly reduce available memory.]] | * [[#zonealarm_toolbar_may_significantly_reduce_available_memory|ZoneAlarm Toolbar may significantly reduce available memory.]] | ||
| Line 17: | Line 18: | ||
| * [[#to_process_large_images_at_full_resolution_you_must_increase_the_memory_allocation_above_the_default_values|To process large images at full resolution, you must increase the memory allocation above the default values.]] | * [[#to_process_large_images_at_full_resolution_you_must_increase_the_memory_allocation_above_the_default_values|To process large images at full resolution, you must increase the memory allocation above the default values.]] | ||
| * [[#continuous_backup_or_indexing_may_interfere_with_image_caching|Continuous backup or indexing may interfere with image caching.]] | * [[#continuous_backup_or_indexing_may_interfere_with_image_caching|Continuous backup or indexing may interfere with image caching.]] | ||
| - | * [[#must_use_double-click_not_the_open_button_to_navigate_into_a_folder_when_using_file_open_project|Must use double-click, not the Open button, to navigate into a folder when using File > Open Project]] | + | * [[#must_use_double-click_not_the_open_button_to_navigate_into_a_folder_when_using_file_open_project|Must use double-click, not the Open button, to navigate into a folder when using File > Open Project .]] |
| * [[#windows_my_documents_and_my_pictures_may_not_be_writable|Windows, "My Documents" and "My Pictures" may not be writable.]] | * [[#windows_my_documents_and_my_pictures_may_not_be_writable|Windows, "My Documents" and "My Pictures" may not be writable.]] | ||
| * [[#windows_cannot_navigate_through_a_shortcut|Windows, cannot navigate through a shortcut.]] | * [[#windows_cannot_navigate_through_a_shortcut|Windows, cannot navigate through a shortcut.]] | ||
| - | * [[#windows_manually_edited_program_files_persist_across_re-installation|Windows, manually edited program files persist across re-installation]] | + | * [[#windows_manually_edited_program_files_persist_across_re-installation|Windows, manually edited program files persist across re-installation.]] |
| - | * [[#macintosh_os_x_could_not_establish_communications_with_stackshot_controller|Macintosh OS X, "Could not establish communications with StackShot controller"]] | + | * [[#macintosh_macos_monterey_application_silently_fails_to_launch|Macintosh macOS Monterey, application silently fails to launch.]] |
| - | * [[#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_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_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 34: | Line 37: | ||
| * [[#red_rasterformatexception_occurs_during_retouching|Red "RasterFormatException" occurs during retouching.]] | * [[#red_rasterformatexception_occurs_during_retouching|Red "RasterFormatException" occurs during retouching.]] | ||
| * [[#graphics_acceleration_sometimes_makes_the_retouching_brush_very_slow_and_jerky|Graphics "acceleration" sometimes makes the retouching brush very slow and jerky.]] | * [[#graphics_acceleration_sometimes_makes_the_retouching_brush_very_slow_and_jerky|Graphics "acceleration" sometimes makes the retouching brush very slow and jerky.]] | ||
| - | * [[#retouching_brush_disappears|Retouching brush disappears]] | + | * [[#retouching_brush_disappears|Retouching brush disappears.]] |
| * [[#external_tiff_reader_cannot_handle_commas_in_file_or_directory_names|External TIFF reader cannot handle commas in file or directory names.]] | * [[#external_tiff_reader_cannot_handle_commas_in_file_or_directory_names|External TIFF reader cannot handle commas in file or directory names.]] | ||
| * [[#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".]] | ||
| + | |||
| + | ===== 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. | ||
| + | |||
| ===== 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 ===== | ||
| Line 45: | Line 59: | ||
| If that doesn't work, then please contact support@zerenesystems.com and we'll get the problem taken care of. | If that doesn't work, then please contact support@zerenesystems.com and we'll get the problem taken care of. | ||
| - | ===== Settings are retained across uninstall / reinstall ===== | + | ===== Settings are retained across uninstall/reinstall ===== |
| On **Windows**, the uninstaller program removes only folders and files that it created. This causes some state information to be retained, so that uninstall/reinstall will not restore the program to a factory-fresh condition. To get back to a factory-fresh condition, you must uninstall, then manually remove one folder and the files it contains, before reinstalling. | On **Windows**, the uninstaller program removes only folders and files that it created. This causes some state information to be retained, so that uninstall/reinstall will not restore the program to a factory-fresh condition. To get back to a factory-fresh condition, you must uninstall, then manually remove one folder and the files it contains, before reinstalling. | ||
| Line 57: | Line 71: | ||
| {{:stacker:support:knownissues:zerenestackerfolder.png}} | {{:stacker:support:knownissues:zerenestackerfolder.png}} | ||
| - | 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. Be careful that you do not remove other folders in ~/Library/Preferences, as these contain settings for other programs. | + | 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 **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. | ||
| Note that removing ~/Library/Preferences/ZereneStacker will also uninstall your license key, so be sure you have a copy of that saved first. If you do not already have a separate copy of your license key, you can make one by running Zerene Stacker and extracting the key using copy/paste at Options > Registration. | Note that removing ~/Library/Preferences/ZereneStacker will also uninstall your license key, so be sure you have a copy of that saved first. If you do not already have a separate copy of your license key, you can make one by running Zerene Stacker and extracting the key using copy/paste at Options > Registration. | ||
| Line 148: | Line 164: | ||
| java.io.FileNotFoundException: C:\Users\Me\Pictures\unnamedZSproj20111103154858382\previewimages\-Unaligned-117.jpg (Access is denied) | java.io.FileNotFoundException: C:\Users\Me\Pictures\unnamedZSproj20111103154858382\previewimages\-Unaligned-117.jpg (Access is denied) | ||
| at java.io.RandomAccessFile.open(Native Method) | at java.io.RandomAccessFile.open(Native Method) | ||
| - | | + | |
| There are several possible workarounds for the problem: | There are several possible workarounds for the problem: | ||
| - Turn off or pause the backup or indexing facility while ZS is running. | - Turn off or pause the backup or indexing facility while ZS is running. | ||
| Line 193: | Line 209: | ||
| On Windows, if any files in C:\Program Files or C:\Program Files (x86) are manually edited, then those edits will persist across reinstallation of Zerene Stacker, even if Zerene Stacker is completely uninstalled first. This is caused by an annoying feature of Windows called the "virtual store". Contrary to appearances, the original file was not actually edited, but instead it became shadowed by a second file containing the edited version. When the software is uninstalled, the second file remains. Then when the software is re-installed, the second file again shadows the newly re-installed version, so the edited version mysteriously reappears. There seems to be no way to get rid of the second file except by logging in as Administrator, navigating to the virtual store, and explicitly removing the file there. The virtual store is located at C:\Users\<username>\Appdata\Local\VirtualStore\Program Files\ZereneStacker . You must be logged in as Administrator to even see this directory. | On Windows, if any files in C:\Program Files or C:\Program Files (x86) are manually edited, then those edits will persist across reinstallation of Zerene Stacker, even if Zerene Stacker is completely uninstalled first. This is caused by an annoying feature of Windows called the "virtual store". Contrary to appearances, the original file was not actually edited, but instead it became shadowed by a second file containing the edited version. When the software is uninstalled, the second file remains. Then when the software is re-installed, the second file again shadows the newly re-installed version, so the edited version mysteriously reappears. There seems to be no way to get rid of the second file except by logging in as Administrator, navigating to the virtual store, and explicitly removing the file there. The virtual store is located at C:\Users\<username>\Appdata\Local\VirtualStore\Program Files\ZereneStacker . You must be logged in as Administrator to even see this directory. | ||
| + | |||
| + | ===== Macintosh macOS Monterey, application silently fails to launch ===== | ||
| + | |||
| + | Older builds of Zerene Stacker may silently fail to launch under macOS Monterey. The underlying cause is a small change in macOS, which was accommodated in Zerene Stacker at Build T2021-07-31-1138 (July 31, 2021). This launch problem will be fixed by updating your copy of Zerene Stacker to the latest build. | ||
| + | |||
| + | In gory detail, here are instructions to update Zerene Stacker: | ||
| + | - Move to Trash all copies of ZereneStacker that you have now. | ||
| + | - Remove any ZereneStacker icons, for example on the taskbar or dock. | ||
| + | - Using Safari, download a fresh copy of the distribution .zip from https://zerenesystems.com/cms/stacker/softwaredownloads . | ||
| + | - Use Finder to open the Downloads folder. //(Do not use the "Open downloads" icon inside Safari.)// | ||
| + | - Probably the .zip download has already been unpacked to form the "yellow smiling dog face" icon named ZereneStacker. | ||
| + | - But if it has not, then unpack the .zip file manually. //Be sure to do this unpack inside the Downloads folder.// | ||
| + | - Using Finder, move the "yellow smiling dog face" ZereneStacker icon from Downloads to Applications. | ||
| + | - If you are using the Lightroom plugin, then you must also update that as follows: | ||
| + | * Be sure that Lightroom is not running. | ||
| + | * Launch Zerene Stacker from its icon in Applications. This will update the Lightroom plugin to match the new version of Zerene Stacker. | ||
| + | * Quit ZereneStacker. | ||
| + | * Launch Lightroom and confirm that you can Export to Zerene Stacker. | ||
| ===== Macintosh OS X, "Could not establish communications with StackShot controller" ===== | ===== Macintosh OS X, "Could not establish communications with StackShot controller" ===== | ||
| Line 235: | Line 269: | ||
| Interestingly, in most cases just going through the above steps to collect the required information also makes the problem disappear. That probably has to do with the reboot and order of operations. | Interestingly, in most cases just going through the above steps to collect the required information also makes the problem disappear. That probably has to do with the reboot and order of operations. | ||
| + | |||
| + | ===== Macintosh OS X, Zerene Stacker will work on only one stack at a time ===== | ||
| + | |||
| + | Solution: open a Terminal window and launch additional copies of Zerene Stacker using the command | ||
| + | <code> | ||
| + | open -n /Applications/ZereneStacker.app | ||
| + | </code> | ||
| + | |||
| + | If you put the ZereneStacker icon (the ZereneStacker.app application bundle) someplace besides in /Applications, then just edit the command line accordingly. | ||
| + | |||
| + | 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" ===== | ===== Macintosh OS X (Mountain Lion) reports installation bundle is "damaged, move to trash" ===== | ||
| Line 262: | Line 308: | ||
| ===== Macintosh OS X, accessing external drives may be awkward ===== | ===== Macintosh OS X, accessing external drives may be awkward ===== | ||
| - | **Note:** In all recent versions, you can drag-and-drop directly onto the input files list. There is no need to File > Add Files to open a filechooser as described below. Just open a separate Finder window, select your image files there, then use drag-and-drop to enter them directly into Zerene Stacker's "Input Files" panel, at the place where it says "(Drop files or folders here to begin)". | + | On Macs, Zerene Stacker normally attempts to open a Finder window to use as a helper service for navigating and selecting files. On a few Macs, for unknown reasons, the Finder window refuses to open. In that case, Zerene Stacker automatically switches to a different method, using a facility named "JFileChooser" that is part of the Java Runtime Environment that Zerene Stacker runs on top of. (The use of JFileChooser can also be selected explicitly, by removing the checkmark at Options > Preferences > Look & Feel > "Use system native File Choosers if possible".) |
| - | + | ||
| - | Further explanation and other approaches follow. | + | |
| - | + | ||
| - | The JFileChooser that can be selected for use by Zerene Stacker does not display alternate volumes like the native Mac filechooser does. External drives can still be accessed, but the procedure is somewhat awkward. | + | |
| - | + | ||
| - | On OS X 10.5 (Leopard) and later, the easiest approach is to open a filechooser dialog box in Zerene Stacker, using File > Add Files. Then separately, use Finder to open the external drive or network share, go to the appropriate directory, and select the files of interest. Drag and drop those files onto the Add Files dialog of Zerene Stacker, then click the Add button in the Zerene Stacker dialog. This method also has the advantage of showing you a thumbnail preview of the files to be added. | + | |
| - | Alternatively (and required for OS X 10.4), you can go to the bar at the top of the window, the one where the current directory is shown. Click once on that bar and it will expand into a pull-down list of enclosing directories. At the bottom of the list will be an entry like "Macintosh HD", representing the main file system of the computer. Click that. Scroll to the bottom of the list and double-click on Volumes. That should give you a list of all your currently mounted media. Double-click on any external drive to open that, then navigate as usual. | + | Unfortunately the JFileChooser interface looks much different from Finder, and it requires more mouseclicks to access drives other than the default. |
| - | The latter approach is required on OS X 10.4 because drag-and-drop into the Zerene Stacker filechooser does not work on that system. | + | To access alternate drives using JFileChooser, proceed as follows: |
| + | - Open a JFileChooser window, for example by File > Add File(s) or File > Save Output Image(s). | ||
| + | - Go to the bar at the top of the window, the one where the current folder is shown. Click on that bar and it will expand into a pull-down list of enclosing folders. | ||
| + | - At the top or bottom of the list will be an entry like "/" or "Macintosh HD", representing the main file system of the computer. Click that to open it. | ||
| + | - Scroll to the bottom of the list and double-click on Volumes. That should open to give you a list of all your currently mounted media. | ||
| + | - Double-click on any external drive to open that, then navigate as usual. | ||
| + | Also, note that when using JFileChooser, you __must__ use double-click, not the Open button, to go inside a folder. For further explanation about this issue, see [[https://zerenesystems.com/cms/stacker/support/knownissues#must_use_double-click_not_the_open_button_to_navigate_into_a_folder_when_using_file_open_project|"Must use double-click, not the Open button, to navigate into a folder when using File > Open Project"]]. | ||
| ===== Macintosh OS X, launch fails due to Courier font problems ===== | ===== Macintosh OS X, launch fails due to Courier font problems ===== | ||