I am experiencing the same exact problem. Once I switch a previously converted image to multi-pass, all sliders don’t do anything.
Can you try the latest beta (b10) and see if the issue is still there? It should be fixed.
You can download the latest beta version here:
Just run the installer, and you should be good to go. If you run into issues, please let me know in the NLP v3.1 Beta Issues thread.
Awesome!
Assuming there aren’t any major issues in b10, it should be this week. I’m also trying to time this with a website update (with an updated and refreshed Guide section).
Wow! Love this example!
It’s in this latest beta, linked earlier in this post.
Should be fixed in v3.1b10.
It’s intended… basically the “refined” option uses two separate curves (one in the regular tone curve panel and one on a separate mask.
Awesome, that’s great to hear! Would love to see any samples you’d be willing to share here!
This issue should be fixed in b10, but let me know if it isn’t!
I made a bit of a discovery tonight while I was working on my dad’s old slides from the 1950s and I think it may lead to a small additional to my process. All I can say at this point is that it has lead to an improvement to my end result.
I used the positive option as normal, tinkering a little with the white balance and colour sliders to get the colours as natural as I could, did a conversion, edited out off the scratches and marks in lightroom that I inevitably get with these old slides. Then went back and I made my tiff copy. Only then am I tinkering with the curves to get the contrast as I want it, sharpening etc. It seems to work better doing these things when it’s a tiff even though it shouldn’t matter as it was a positive image.
This previously was my end point. But I was finding tonight that if I put this end stage tiff through negative lab pro again - so the second time the sane image has gone through, it improves the colours more - the contrast gets better, any slight colour cast issue that I have been struggling with gets sorted. Everything looks puncher. This is not something you can do with a negative - putting it through twice, but with a positive you can do it and I am liking the result.
EDIT: Just saw in the beta report section that it has to do with the LR version. Because my iMac is an old one from 2013 I try to stay as much on an old LR version as possible, so I can use the same catalogue on both machines…
guess I’ve either to stay at NLP 3.0.2 or upgrade my old iMac…
I just downloaded the beta 10 and installed it over the 3.0.2 and tried to re-convert some scans and also some new dngs.
However, it does not work and always stops with an error “bad argument #4 to ‘format’ (no value)”.
Any ideas what might be the problem?
I’m on a MacBook Air M1
Which version of LR should we be using for the latest version of NLP?
Sorry, it’s a bug in the b10 beta. Fix coming.
It should be the same as previous versions of NLP (any version of LR Classic, or the old perpetual license LR 6.14).
But..
- The “Refined” color process requires later versions of LrC
- There is an issue with the current beta (b10) that is impacting older versions of LrC, which will be addressed shortly.
Nate, I’m using NLP 3.0.2 with Lightroom version 13.0.2 on an Intel Mac running Sonoma 14.7.5. I am not having any problems and I want to keep it that way. But after reading your recommendation:
…it sounds like I might get away with updating Lightroom to 13.5 (if possible) and trying the NLP 3.1 beta? yes? no?
When LRC 13.5 was released, I had issues with NLP 3.0.2 and went back to LrC 13.4.
A few days ago, I updated macOS to 15.5 and LrC to 14.3.1…and issues came back. Checked other combinations and gave up. Finally, I restored macOS 14.7.6, LrC 13.4 and NLP versions 3.0.2 and beta 10 without issues so far. All of this on a 2019 5k iMac.
Note that downloading beta 11 worked, but the installer often was rejected and macOS proposed to trash it. → attn. @nate
Hi @runswithsizzers,
You can also keep Lightroom at 13.0.2 and try NLP v3.1… that would be my reco for now.
You don’t really gain much at the moment by updating to LrC v13.5 or later, but you are welcome to try that. In theory, you should be OK unless you are trying to do large batch conversions, and even then it should work. I’m also working directly with Adobe to try to help with the overall stability issues for plugins in v13.5 and later on Intel machines (they are aware of the issue and trying a fix for an upcoming version).
I’m curious if anyone else is having this issue… I have confirmed that the package is properly notarized with Apple, and it doesn’t really make sense that it would work sometimes on your system and sometimes not, which makes me think it may be a systems issue with your computer.
Just to be safe, I’ve reuploaded the package.
…and the beta 11 installer properly worked this time.
The issue was that macOS rejected the installer, not the plugin. Maybe the OS needed a few behind-the scene updates (Gatekeeper?) after I had re-installed macOS Sonoma because Sequoia (and Lr 14) were making NLP unable to convert more than a single digit number of files in one batch.
Update:
I had one issue, when NLP worked with super resolution-, stitched images and with roll analysis. (NLP3.1 b11, LrC 13.4 macOS 14.7.6, 5k iMac 2019)
Update June 19th, 2025
New version of NLP tested and okay.
Nate, thanks for your reply.
I don’t know how many images it takes to qualify as a “large” batch. Lately I have been shooting 120, so a roll is only 12 shots. However, I just loaded my old Pentax MX with a 36 exposure roll.
I would really hate to have to uninstall my system software and /or Lightroom and revert to a previous version, so I am reluctant to “try” anything that does not have a very high probabilty of working. My 2020 Intel iMac is very similar to the one @Digitizer is using, so I am not going to try anything that does not work for him. Thanks, @Digitizer for doing the testing so I don’t have to!
So I guess for now, I wait for the next version of Lightroom and see if Adobe’s fix works. I am in no hurry to update my system software from Sonoma to Sequoia, but I would like to update Lightroom and NLP as soon as practical.
Did a few test runs with NLP 3.1 b11 on LrC 13.4 on macOS Sequoia 15.5 from an external SSD attached to the 5k iMac 2019 - without any issues I relate to NegativeLab Pro.
Understood. You can also update NLP without needed to update Lightroom Classic… v3.1 will work great on LrC 13.0.2.
Looking at the first post in the thread, I got the impression that NLP version 3.1 has silently been released by @nate … I downloaded and installed NLP 3.1 without any issues on my 2019 iMac running macOS Sonoma 14.7.6 and Lightroom Classic 13.4. So far so good.
Testing against a collection of 138 images worked without issues and with results that met my expectations. This is how I tested:
- Created a new catalog and added test images to it
- Cropped the images and adjusted orientation as needed (rotate and flip)
- Adjusted WB automatically for all images (colour and b&w)
- Created a set of virtual copies, launched NLP and repeated the following
-
- Set conversion parameters (Basic, Pre-Saturation = x, Border Buffer = 10%)
-
- Start conversion and wait until done, hit okay
-
- Create a set of VCs from the newly converted images
-
- Select NLP’s first tab and undo the conversion
- At the end, I got converted VCs with pre-saturation set to 1, 2, … 5
Converting and resetting or un-converting VCs had so far and often produced popups because of whatever the causes were. NLP 3.1 as available from the download page did not cause any ill effects during the tests.
NLP 3.1 seems to run stably in the system described above and it’s my expectation that it will do so with other versions of Lightroom, operating systems and hardware platforms. I might retest on M1 MacBook Air. Don’t hold your breath!
Yep! Updated website with the official v3.1 is now live. You can find the release on the download page. It’s close to identical to v3.1b11.
Great!
Yeah, it should be running really well (certainly way better than v3.0.2), although you still might get some Lightroom errors here are there on intel-based Macs. I’m working with Adobe to solve some of those issues that I can’t do on my end.
If you do run into any issues, please use the v3.1 issues tracking thread!
Thanks for all your help @Digitizer, you are a legend for all your help! 
1 Like
I compared the checksums of the respective zip files. According to the checks, the downloads for b11 and the released version are identical.
Hi, did you get to fix the issue? I’m having a same issue as well..
Very interesting update with the positive/digital editing possibilities!
Been doing some initial testing with archive files today, here are some comparison samples:
Kodak Gold 200 negative conversion v3.0 vs v3.1 – this one really shows the benefit of the Refined color process well, the green tones of the truck were overpowered by the overall warm tint in previous version, the v3.1 brings out the green really nicely, while still retaining an overall warm look.
An old Fuji Velvia scan with an Epson flatbead to a TIFF, earlier Lightroom edits vs NLP 3.1 in Positive mode – NLP really brings out the Velvia tones and contrast in a very natural (to that film!) way.
Digital RAW file (Canon 5D), edited to taste in Lightroom vs a quick spin at NLP 3.1 in Edit only mode – Much prefer the skin tones and the overall tonality on the NLP version. Overall this might be the mode and use case I’m most exited about, will be interesting to see how well NLP finds it place in a purely digital workflow as a way to make the files look more natural & analogue!
1 Like
Hi,
If you are asking about the camera profiles, the correct camera profile will be Negative Lab v2.3. So if you see that, that is correct.
It’s pretty rare for me to change the underlying profile, and it’s only happened when I’ve found very specific ways to improve it.
-Nate
1 Like
Hi @miemo,
Thanks so much for sharing these examples!
And I couldn’t agree more! The “edit only” mode is something that I’ve been loving in my own workflow with digital positives… I haven’t hyped it too much since I don’t want to take away the focus from film, but man, it really is such a useful tool for digital!
Back when I used to design presets, this would have been a game changer for me. I may have to make another post or tutorial just specifically about this…
2 Likes