This should now be fixed in b11… you can find it on the main announcement page.
Just note that the “refined” color process requires LrC v13… it relies on using separate tone curves within masked layers, and this wasn’t added until LrC v13.
-Nate
Downloaded NLP 3.1 b11 through the link in this post - twice, because the first download’s installer would not work. A second download fixed this.
No problems installing, but …
- I had to activate NLP again
- The hotkey would not work. It was absent and had to be added manually.
All of the above necessary after updating my 2019 5k iMac to macOS Sequoia 15.5 via resetting the drive schema and migration from a backup - plus an update of Lightroom Classic 13.5 to v14.3.1
I also got “unexpected quit” messages of Lightroom (which never even blinked) when I wanted to make a user preset the new default and with other actions too.
Hmm, that’s curious. Just check the installed and re-uploaded. I’ve confirmed that everything is notarized properly with Apple.
I suspect that the issues you are having are related to something having gone wrong here with your overall system.
I can’t replicate any of your issues. I’ll be curious to see if anyone else has these issues, but I strongly suspect that something has gone wrong with your system permissions or files during all of this.
Re-downloaded B11 and this time, the installer worked as expected. The first conversion tests were successful, except for this:
My volume config:
/dev/disk0 (internal, physical):
#: TYPE NAME SIZE IDENTIFIER
0: GUID_partition_scheme *2.0 TB disk0
1: EFI EFI 314.6 MB disk0s1
2: Apple_APFS Container disk1 2.0 TB disk0s2
/dev/disk1 (synthesized):
#: TYPE NAME SIZE IDENTIFIER
0: APFS Container Scheme - +2.0 TB disk1
Physical Store disk0s2
1: APFS Volume MacFotos 437.2 GB disk1s1
2: APFS Volume MacExtra 276.3 GB disk1s2
3: APFS Volume MacDrive - Daten 227.9 GB disk1s3
4: APFS Volume Preboot 2.3 GB disk1s4
5: APFS Volume Recovery 1.2 GB disk1s5
6: APFS Volume MacDrive 10.3 GB disk1s6
7: APFS Snapshot com.apple.os.update-... 10.3 GB disk1s6s1
8: APFS Volume VM 1.1 MB disk1s8
I Installed macOS according to this: Create a bootable installer for macOS - Apple Support and with a bootable backup on an external SSD, also created with a bootable installer and migration assistant.
Photos and Extras (mostly installers) were copied by Carbon Copy Cloner with verification.
Hi all! There is no way to save my custom presets! Doing “Create New preset” → “Save New Preset” apparently seems to work and the name of the new preset appears. But closing NLP (I press Apply, I swear) and reopening it the preset disappeared and the image automatically returns to the previous preset settings. In the folder indicated by Nate I pasted a custom preset that I had created months ago when I used Windows and it’s the only one I see in my own presets, any new one I try to save doesn’t create any file. I am using NLP 3.1 b11, Lightroom Classic 14.3.1, MacOS Sequoia 15.5 on Mac Mini M4. Where I’m wrong? Thank you in advance.
Further tests on 5k iMac with Lr 13.4 on Sonoma and Sequoia (booted from external SSD) produced no issues. Same for the tests with Lr 14.3.1 on Sequoia on M1 MacBook Air 2020.
While NLP 3.1 B11 works well on my M1 MBA with LrC 14.3.1, I had to downgrade Lightroom to 13.4 on the iMac.
Hi Nate,
After installing 3.1 beta. I’m seeing the message “Could not locate LUTs” in the edit panel.
Hey Nate! Thanks for all your work on NLP. I’ve been using the 3.1 beta for a few weeks with no issues, but I started having some trouble today. I converted a roll and edited each frame as usual, but then at some point NLP stopped appearing for one frame in particular. I’ve tried uninstalling and reinstalling b11, but I can’t get it to appear (this happens on both LRC 14.3.1 and 14.4 by the way). Here’s a screen recording if that helps. Thanks!
EDIT: I found the bug! This happened because I set the Sat slider to a non-integral value on the frame in question. Is there a way to reset this value to an integer in the LR catalog without the NLP editor? Even if I choose a previous edit from my LR history that worked before, the NLP window still won’t appear, so I’m guessing this value is baked into the catalog file somewhere.
Apologies if I’m not using the thread correctly, it’s my first time. I’m using v3.1, which is great, my question is about the Undo button which existed before and was very helpful, but I can’t find it on v3.1. Am I missing something?
Ah, yeah, that would do it… both the “amount” slider and the “sat” slider need to be integer values. I understand though why you would try to set it to a non integer, so I should probably make that not possible to do…
Yes, the only way to do this would be to select the image (or images) with the issue, right click and select “remove photos > remove from Lightroom Catalog”, and then just re-sync that folder (or manually import the file back).
That’s the only reliable way to do this.
It’s still there, but it only shows up once you start making edits (and the redo button only shows up if you have a change you can redo).
Where you running any versions previously and did you ever have this issue?
This message usually means that you have hidden the presets needed for this to work… but it could also be an install issue.
First try this: In the develop module, right click inside of the presets pane on the left and select Reset hidden presets. If that doesn’t work, email me at nate@natephotographic.com with info about your system and I can give you further help to try to see what’s gone wrong here.
1 Like
Blockquote
First try this: In the develop module, right click inside of the presets pane on the left and select Reset hidden presets.
Thanks Nate, this did the trick. I have 3.01 previously but never noticed this issue
While my first tests with NLP 3.1 (as released? a few hours ago) were uneventful, a new series of tests have brought up the following:
I got this message with each run and even though Lr never actually closed. The popup appeared in what looked random moments and numbers, and by pressing “Ignore” every time, conversions finished without further issues. The random appearance of popups feels like some timing issue.
Testing was done with NLP 3.1, Lightroom Classic 14.4, macOS Sequoia 15.5, on a 5k iMac, booted from (an external) Samsung T7 SSD. 138 Canon RAW and DNG files (super resolution and HDR) created by LrC 13.4 (a while ago); virtual copies converted in 4 runs. Total of 552 images after testing.
Yes, v3.1 is officially out here. Sending out update emails later today. (I like to get it on the website a day or so earlier just so that I can confirm that everything is downloading and working properly.)
The final v3.1 is the same as b11, but with the removal of a few internal logs calls that were never displayed (but were still evaluating internally, and could cause syntax errors).
That’s great that it’s still finished as it should. I suspect that these errors are popping up just from Lightroom itself struggling to keep up with a large number of super resolution DNGs and lots of virtual copies which are very memory intensive and require a lot of writing to the catalog.
That’s certainly a good sign, but having to interact with these popups is at least annoying and I hope that you and Adobe will find (and remove) the cause.
I use the same set of images with every test and convert virtual copies. LrC seems to be the one causing the popup indeed, but it doesn’t when I test LrC 13.4. The number of super resolution DNGs is small (2), I use these to see how they compare with stitched images. My iMac has 40 GB of RAM. This usually prevents any swapping.
I’ll check memory usage and report back…also with results from the M1:
Testing NLP 3.1.1 with LrC 14.4 on M1 MacBook Air (late 2020)
- on macOS 14.7.6 Sonoma: No issues, RAM at 3.6 GB max.
- on macOS 15.5.0 Sequoia: pending
- on macOS 26.0.0 Tahoe ß: pending
Note that I have reinstalled all volumes from scratch.
Granted LrC full disk access.
Issue: NLP does not store custom settings and defaults (2nd tab) on M1. Also, the first tab fields don’t react to “tab” to move to the next box, it’s as if “tab” has no effect.
This has now been fixed in v3.1.1 (it disallows setting non-integer values in the Sat and Amount sliders).
For any images that you might have had this issue with on v3.1.0, you will still need to remove and then reimport the images back into the catalog to reset this.
1 Like
Hello All,
Updated to 3.1. Experimenting with the new features and I am stumped on the “refine color” drop down in the Advanced tab. The options listed don’t match those in the 3.1 tutorial and updates on the forum that was released last fall. I am running LRC 14.4. I don’t have ColorProcess option. Has this been removed/updated? Do I need to change any of my settings in LR? Puzzled. Thank you.
Chris
Looks like you have an earlier beta version somehow, probably from an old link.
Download the latest from this link.
Thanks for the v3.1 update. I downloaded the new version today, upgrading from v3.0. However, after installing v3.1 and opening Lightroom, I noticed that all the images I previously edited using NLP v3.0 now appear significantly washed out.
I’m not sure how to fix this, and it’s a serious concern since these aren’t personal photos—they’re client work I’ve spent many hours editing with v3.0. I really need a solution to restore or maintain the original look one way or another.
Let me know how best to proceed. Thanks in advance! (see the screenshot below)
I have not touched anything.. all I did was download the new version and updated in lightroom.
I tried switching the profile to “Adobe Color,” but it still doesn’t match the original look. Here’s an example: on the left is a JPEG exported before I updated to v3.1, and on the right is the same photo after updating to v3.1 and changing the camera profile to “Adobe Color.”
I’ve tried other toggles as well to match the original edit, but nothing comes close to how the photo looked before. It’s really off from what I originally edited.
Or it may be “Adobe Standard” in some cases. There should be a camera profile that was being used by Lightroom while it didn’t have the profile for your camera.
One way to temporarily return everything to exactly the way it was before is to do this:
- Close Lightroom
- Navigate to the folder where the NLP camera profiles are stored.
- Find the profile for your camera (that was added in v3.1), and move it somewhere temporarily where Lightroom won’t see it (like on your desktop)
Here is where you will find the camera profiles:
Mac:
Library/Application Support/Adobe/CameraRaw/CameraProfiles/NegativeLab Camera Profiles
Win:
C:\Users<YourUserName>\AppData\Roaming\Adobe\CameraRaw\CameraProfiles\NegativeLab Camera Profiles
This can be useful if you want to be sure that everything returns to exactly as before (and you still get all the advantages of v3.1).
But for ongoing conversions, I do recommend having the correct camera profile present as this will improve your conversions.