V2.4 Issues and Fixes Thread

Updates in v2.4.2


:white_check_mark: Fixed Batch Mode issue where some images returned overly bright

There was a memory issue when batch mode was used in some cases, where the camera profile would not set before NLP began its analysis of the image, causing it to return erratic results. This has been resolved so batch mode should run correctly. As a side benefit of fixing this memory issue, batch mode should now run a bit faster. If you experienced erratic batch mode results, please upgrade to v2.4.2.

Thanks to @mattbeaty, @Lukeys.film and others for reporting and helping me resolve!


:white_check_mark: Unconverted images now correctly return to their previous crop on “apply”

As pointed out here, in some cases the border preview crop was persisting and not returning to the proper crop. Now, if you hit “apply” on an unconverted image while border buffer preview is active, the crop will correctly return to where it was before. Thanks to @vandebroek for pointing this out.


:white_check_mark: The Windows Hotkey can now only be triggered while Lightroom is active

As pointed out here, the previous windows hotkey could still be activated when Lightroom was not the primary window, causing potential conflicts with other shortcuts. This update ensure that the windows hotkey for Negative Lab Pro is only triggered when Lightroom is the active window. Thanks to @bcc32 for bringing this to my attention and providing a fix.



Updates in v2.4.1


:white_check_mark: The Windows installer now correctly runs for both LR6 and LrC users

In some cases, the windows installer was failing to run for LR6 users when it didn’t find Lightroom Classic. This has been fixed, and the installer will run properly for LR6 and LrC users on Windows.


:white_check_mark: Fixed issue with LR preferences not correctly updating on some systems

The previous installer attempted to improve compatibility with the LUT presets by telling Lightroom where to find them, but this caused unexpected issues for some users, so it has been removed from the installer.

If you installed V2.4.0 and notice any issues, then I’d recommend you do this (in order)

  1. In Lightroom, go to “Preferences > Presets”. If there is a “half dash” across the checkbox for “Store Presets With Catalog”, click it until it is what you want it to be (usually that will be having it unchecked), and restart Lightroom.
  2. Download and run the most recent installer (same link as in your email).

Step 1 and 2 should be enough, but if that doesn’t work, you will want to reset your Lightroom preferences , then download and run the latest installer.


:white_check_mark: Fixed Issue with Tiff Prep Utility Error

If you experience an issues with Tiff Prep Utility, please update to the latest version.

Getting error when running TIFF Scan Prep


Troubleshooting


:point_right: Can’t locate LUT

If your LUT or Saturation control is saying that it “can’t locate LUTs”, try these things (in order)

  1. In Lightroom, go to “preferences > presets” and make that “Store Presets with Catalog” is NOT selected. If it is “half-selected” with a horizontal line in the middle, click it twice to make sure it is unselected. Then restart Lightroom.

  2. If that doesn’t work, go to the “develop” module, and make sure the “presets” pane is expanded. In the expanded area, “right click” on any of the presets, and select “Reset Hidden Presets”
    reset-hidden-presets.

  3. If that doesn’t work, go to “File > Import Develop Presets and Profiles” and then manually add ALL the files from the following folders:

Mac: “HD / Library / Application Support / Adobe / Camera Raw / Settings / NLP Enhanced Settings”
Windows: “C:\ Users \ xxx \ AppData \ Roaming \ Adobe \ CameraRaw \ Settings \ NLP Enhanced Settings”


:point_right: "Camera Profile still shows 2.3? Did I upgrade correctly?

Yes, both the Camera Profile and Engine option will still be at v2.3.

The camera profile is like the foundation of a house. You don’t want to move the foundation often, unless there is a very good reason to do so. To date, I’ve gone through three camera profile versions (v1, v2 and v2.3). So most of the updates have not included a new version of the camera profile. The camera profiles will stay at 2.3 into the future unless I find a new way to improve.


:point_right: "Mac Ventura: issue if the installer is run from some folders

Issue: After running, the installer says “The installer has detected an error and was unable to complete the installation. Get in touch with the software manufacturer to ask for assistance”**

What’s happening: There appears to be a bug (or permission issue) with Mac Ventura that causes ALL package installers to fail when run from certain directories. Read more here: Install with Pkg file failed | MacRumors Forums

Solution: The solution is to MOVE the package installer to your Applications directory, and try running again from that directory.

1 Like