NEGATIVE LAB PRO v3.1.1 is officially live! You can download it here.
Known Issues with current (v3.1.1):
Intel-based Macs running LrC 13.5+ may still get warning pop ups from Lightroom during large batch conversions. It shouldn’t freeze the operation (as it did on earlier versions of NLP) and it should happen much less frequency with v3.1.
In some cases, users are having issues saving presets. I haven’t been able to replicate it on my system. If you experience this issue, please provide your operating system version. You can also go to “[username]/Library/Application Support/Negative Lab Pro”. Right-click the folder and select “Get Info” and then look at what the permissions show at the bottom. Do the same thing for “Presets” folder.
Issues fixed with v3.1.0
Fixed issue caused with non-integer numbers in the “saturation” or “amount” controls.
Issues fixed during beta:
Major improvements to error handling during batch processing Fixed an issue causing Edit Only to not work properly Fixed an issue impacting LrC 12 and earlier Fixed an issue with conversion setting persistence
Troubleshooting Common Issues
“Could not locate LUTs” in the edit panel.
This message usually means that you have hidden the presets needed for this to work. In the develop module, right click inside of the presets pane on the left and select “Reset hidden presets”
“After updating, my previous conversions changed appearance. They got really bright, without even opening Negative Lab Pro”
Don’t fret! This just means that your previous conversions were done while you were missing the proper camera profiles. When the camera profile is missing, it will still convert, but Lightroom will use it’s own default “Adobe Color” as the working profile. When v3.1 correctly loaded the camera profile you need, Lightroom updates the image, and now there is a mismatch between the profile applied and the profile used during conversion.
There are two ways you can fix this:
The easiest way is to manually change the camera profile to “Adobe Color.” When you do this, you will see the image return to the way it looked previously. You can think sync that profile over to all the other images you need (you don’t need to do it individually).
The other thing you can do is to re-covert the image (this time it will do it with the proper profile for your camera). To do this, you can 1) make a virtual copy (if you don’t want to lose your previous edit), 2) Open the image in Negative Lab Pro, go to the “convert” tab and select “reset image”, 3) Then reconvert and re-edit your photo.
I’m was on LRC 14.3.1 and downloaded the 3.1b7 from Dropbox but still getting errors, now: bad argument #1 to ‘pairs’ (table expected, got nil) or sometimes ^n does nothing or only picks up 21 of 36 images when all are selected. I’m on an intel mac
I downgraded LR and works much better, I think I have gotten an error a few times. I haven’t tried reupgrading LR and b10. Anything between b7 and b10 that you think would help my specs?
I just downloaded and tried out 3.1b7. I have not been able to do any conversions with it at all so far. Tried about five images, both negatives and positives. Every time I get a message ‘an internal error has occurred: bad argument #4 to ‘format’ (no value).’
Using version 11 of lightroom classic on windows 10.
No issues so far with 3.1 b10 in Lightroom Classic 13.4 on macOS 14.7.6.
To check out limits of b10, I converted 120 normal images. Results were as expected with presaturation at 1, except for one image of an evening sky that turned out quite differently:
Even though the two images are copies of the same source, conversions are different…and the thumbnail in Library view is different too - which seems normal in this odd case.
Had another test with the two images, this time, one was blue/blue, the other red/blue. @nate , look for the files from wetransfer.com.
There are a lot of optimizations in b10, so I would give that a try, first with the downgraded version of Lightroom Classic (v13.4) and then you can try upgrading Lightroom Classic. Make sure your catalog is optimized.
Hmm, that’s odd. I haven’t seen that error.
My first thought is that this could be an issue with the specific version of Lightroom you have… so first, I would try updating to Lightroom Classic 13.4.
If that doesn’t solve it, I would try resetting your Lightroom preferences, then reinstalling the beta and trying again.
If that still doesn’t solve it, we can try some additional troubleshooting.
Just be aware that if you are making large numbers of virtual copies, it takes Lightroom a long time to update this in the their catalog. You need to wait until Lightroom has finished rendering the virtual copies before opening Negative Lab Pro on those virtual copies. It’s also a good idea to make sure that all the settings have been brought over appropriately (especially white balance)… I’ve run into issues a few times with making large virtual copies where some of the settings didn’t come over properly, which can result in this sort of issue.
But I will take a look at the files and see if I notice any issues…
This time, they were physical copies that LR has seen for a very long time. Issue being (possibly) that there is nothing to pick WB from. Nevertheless, I’d expect two similar, if not identical, conversions when converting several times. Another issue might be that Lightroom (or macOS) is not always updating views in more recent releases.
Explored Beta 10 a little bit more on the iMac and found that the new beta is almost immune to differences in exposure, pre-saturation and colour model used:
center 3 x 3 images: Different colour models top-down, different pre-saturation left-right
left column: Exposure -1/3 EV at pre-saturation like the neighbouring column
right column: Exposure +1/3 EV at pre-saturation like the neighbouring column
number of starts = level of pre-saturation
Sounds complicated? Doesn’t really matter. Differences are subtle and with these source images, I can set NLP to almost anything and get decent output. Differences were bigger in NLP v3.0.2! Please be aware that different crops and border buffers can change the outcome, this overview is by no means representative for all images and settings.
I had the same error as Dayvo. I updated my LrC to the 13.4 as Nate suggested, and it’s working now.
I noticed a new bug though (or maybe this is intentional?). When selecting a previously converted set of images, I choose the engine setting to be v3.1+ - then I’ll hit Sync to apply this to the whole image set (I select only ‘Engine’ settings to sync). Nope, doesn’t update the images, they’ll stay v3.0 until I manually one-by-one change them to v3.1+.
Okay, so not just a glitch with my setup then. Hope this doesn’t mean 3.1 will be incompatible with classic 11.I downloaded v 13.2 and although I like some of the features, my pc is pretty old and it struggles with the system requirements. v11 is much more zippy.
It should be compatible, BUT, the “refined” color process won’t work, because it relies on features in Lightroom Classic that came later. But it shouldn’t just not work at all…
Let me see if there is a good way for me to troubleshoot this… I can’t seem to find a way to download Lightroom Classic 11…
I see what you mean, but this isn’t impacting anything in this case.. the “Engine Setting” dropdown doesn’t do anything beyond changing the settings beneath it (like “CurvePoints”, “ColorProcess” etc). So those should all be syncing correctly, even if the dropdown UI is still showing v3. The only difference between v3 and v3.1 engine settings is the ColorProcess setting, and that should be carrying over via sync.
Similar to working with Negatives, if your slide doesn’t have much context in terms of different colors or black and white points, then you could run into situations like this, where it overcorrects a scene in an attempt to neutralize that dominant color. In this case, you would be better off either 1) Using the “Edit Only” mode to make adjustments, 2) Using the “match” feature from a positive that did convert well, or 3) Using Roll Analysis.
So when I run this, both files convert the same and with the blue tint (instead of the orange).
That’s selecting the Edit tab and then use available tools? Most of them are greyed out and I asked myself what the benefit of NLP is - compared to using Lr’s own sliders. Can you comment on this and will the user guide show the different modes?
Don’t know if this is a bug specific to the 3.1 beta, but with color DNGs I always find a “Profile missing” in the dev tab.
Can this be ignored or does it have an influence on the color rendition?
NLP has a profile, but it is not located where Lightroom expects it
The DNG file’s metadata (camera brand, model etc.) is wrong or missing
Can you tell us what camera took the picture(s) with missing profile(s) and what versions of Lightroom and OS you used in these cases? Camera native DNG or converted by … ?
Sorry, forgot to include that: These are Coolscan 5000 and Coolscan 8000 scans. So, it should not be the scans.
This is the most recent LR 14.3.1, the most recent MacOS 15.5 (ARM). And o/c beta 10 of NLP 3.1
You could attache one of the scans and then, we could find out if the issue is a general issue or on your system only. If you didn’t use Vuescan, it’s no use though.
Fixed issue caused with non-integer numbers in the “saturation” or “amount” controls.
