Recently I have found myself unable to convert negatives.
I have scanned DNGs thru Silverfast, run the Silverfast prep utility, then white balance them. I then open up the NLP dialog with no problems and hit convert. It seems to go thru the whole process, but the image remains unconverted and I get this error screen ?:0: attempt to index field '?' (a nil value). Making any adjustments with the NLP dialog makes the error show up again. Finally, NLP believes it has converted the image and I have to unconvert to get it to try again.
I found a few other topics with similar errors that lead me to try deleting and reinstalling NLP, but this doesnāt seem to have resolved it. Unsure what to try next!
Are you on the latest version of LR Classic? Are you using a custom preset as your default preset?
The only thing I can think of off the top of my head is that it could be that you have a custom preset that either isnāt available or is somehow breaking something?
What happens if you hit āapplyā after conversion and those warningsā¦ when you reopen Negative Lab Pro does it still show those warnings?
If it still shows those warnings, could you do this:
Select the image which is producing warnings
Go to āfile > export as catalogā
Make sure āInclude Negativesā is selected (so that the image itself will be copied)
Send the resulting zip to me at nate@natephotographic.com, and I can see exactly where the error is.
Another thing you can try which may resolve the issue is to reset your Lightroom preferences. This will reset Negative Lab Pro back to its default settings (you may need to install again after resetting preferences).
Apologies, I shouldāve included more helpful info for diagnostics in my original post! Latest version of LR Classic, 13.1, and macOS Sonoma 14.2.1, running NLP 3.0.2.
I have no custom presets. NLP was working fine for me, and then I scanned a roll with Silverfast as TIFF instead of Raw to try out how itās dust removal works and thatās when I encountered this error the first time. I rescanned it as DNG and it still seems to be happening with pictures from that roll, though files previously converted seem to work just fine still.
It does, this persists thru a restart of LR as well.
I reset my Lightroom preferences, but the error persists.
Iāve gone ahead and did the export as catalog and sent it your way. Thanks for the help.
Havenāt seen that exact error but recall something similar when using another plugin which couldnāt find a custom metadata field. Youāve not mentioned but worth having a look to make sure that the Update Silverfast/Vuescan menu button is adding NLP metadata?
I noticed I was able to scan a new roll, and NLP worked ok. This lead me to rescan this previous roll in the same fashion to see if there was some weird Silverfast setting I had set that got reset upon restarting it.
I scanned 1 image, and was able to convert it no problem. But then when I scanned the rest of the roll and ran NLP, same issue. It seems now individually selecting images and changing the roll selected in Roll Settings ā Analysis to This image only seems to resolve the error and allow the inversion to take place.
Yeahhh so I too have begun encoutering this issue!
Fresh install of Lightroom Classic 13.2 on Sonoma 14.2; Camera Raw 16.2
NLP v3.0.2
Successfully converted a bunch of rolls (both TIFF & RAW DNG scans from Silverfast 9)
Now have suddenly started getting this message when converting (both single file and whole roll):
āAn internal error has occurred.ā
ā?:0: attempt to index field ā?ā (a nil value)ā
Toggling roll analysis off/on did not make a difference for me (as the error is also ocurring on single file).
I had the same problem when scanning with Silverfast. The issue was that the positive format was tiff instead of DNG.
Changed it to DNG and worked just fine!
I had the same issue And after deeper exploration I found out that āUpdate Vuescan / Silverfast DNGsā on a batch of scans (Multiple Files Selected) will update all files, however the āRead Metadata from Fileā will update only one scan (if in Develop Module, No issues in Import), not all selected. You have to do this one by one in order to avoid the error message.
PS. I am experiencing this on Mac, Not 100% sure if the issue is happening on my windows PC as well and I am not home now to check, sorry. (Might update the info eventually), I donāt use Roll analysis as my photos are probably not consistent enough due to occasional over exposure some turn out too dark and some are too bright, so I am not sure if that is the Actual cause of the issue.
Can you try creating a new catalog (āFile > New Catalogā) and see if you still encounter the problem there? If you do, can you send some sample files to me at nate@natephotographic.com?
I still havenāt been able to replicate this issue.
Maybe you havenāt been able to replicate this issue, but I have! I hadnāt converted any negatives for a while, but when I tried this evening I immediately hit the ātable index is nilā error. I have not been able to convert a single negative. āRoll analysisā on/off is not applicable because I get the same issue even when selecting a single negative and attempting to convert. Iām on MacOS Ventura 13.6.9 and Lightroom Classic 13.4 release. Iāve tried relaunching Lightroom Classic and re-loading the plugin from the plugin manager. Has there been any progress with a fix for this? Thanksā¦
Update: Mysteriously, after various failed attempts, I found my ability to convert negatives returned. I was trying to record a screen-capture movie to catch a dialog box that appeared briefly just before the failure (it turned out to be simply the āLoading settings and metadata. This could take a minuteā¦ā dialog) and while recording, the negative I was trying did convert. I tried again after that and mostly got successful conversions, although I did see the error twice more. Iām just going to cross my fingers for now and hope it keeps workingā¦
Iām completely unable to get roll conversion to work on one of my rolls of film. I wasnāt sure if I had done sync scene so I unconverted the whole role. I selected all the images and tried to convert with the roll checkbox checked. I get an internal error with ā?:0 attempt to index a nil valueā then āAdobe Lightroom Classic has quit unexpectedly ā¦ Reopen / Reportā¦ / Ignoreā even though it didnāt really crash. Maybe NLP did? After that I get ā?:0 attempt to perform arithmetic on field āwhitePointOriginā (a nil value)ā.
Mac, most recent Lightroom Classic as of 8/16/2024 (13.5), OSX updated today (Sonoma 14.6.1), NLP installed yesterday (3.0.2). TIFF images from Silverfast.
Iāve seen an uptick in reports on this exact issue, with LrC 13.5 and Sonoma 14.6.1.
It seems that downgrading to LrC 13.4 may fix this issue, so it could be that there is a bug in the latest Lightroom Classic release, or it could be an issue with Sonoma 14.6.1 (I havenāt experienced the issue with LrC 13.5, but Iām still on Monterey).
Yes, it is still happening. Iām getting the error when converting a full roll. Checking or unchecking the create roll doesnāt seem to make a difference. My workflow currently uses TIFF scans from SilverFast. It sounds like DNGs are preferred but Iād like to stick with TIFF if possible. My current workaround is to convert each image and save it with no tweaking. Then I select all the images and create a new roll. That seems to consistently work. I can then tweak images as needed. I use sync and copy/paste.
I like the roll functionality. It helps a lot to get a consistent look. Iāve probably converted a couple hundred rolls (in the older version) and I still struggle with getting color conversion right. It also helps me get a roll finished a lot faster.
To confirm, yes, I am at LrC 13.5 and Sonoma 14.6.1.
follow up: originally I was doing the conversion from the grid view. I have since switched to using the develop view and have been able to successfully convert 2 rolls so far. I wonder it thatās a factor.
Thereās an update for Lightroom Classic: Version 13.5.1
Havenāt seen the release notes yet and lightroomqueen is also fairly sketchy about it.
Just updated LrC and did two series on conversions without any issueā¦but the third series brought back the error message. I then ignored the messages of both LrC and NLP and re-converted the seriesā¦and conversion went through without issuesā¦
Update: I tested NLP 3.0.2 on LrC 13.5.1 on macOS 15 (beta 8) and found that every test went as expected. Got no error messages. Thereās a caveat: In order to keep the trial conversions at their max, I never saved the results. Usually, the error message popped up before NLP switched to tab 2, so, not saving the results should be relatively unimportant, except if the error is caused by āleftoversā as might be the case due to what I experienced above (see 2nd paragraph).
That could absolutely be a factorā¦ Iād be interested to hear from others if using the develop module instead of the library module fixes this for them.
(It could also just be that the library module is a bit more demanding on memory and could be exacerbating a memory leak).
Interesting. Almost all of the reports Iāve received in the last two weeks has been users with Sonoma 14.6.1, which has received a LOT of bug reports with other software as well, so perhaps Apple has fixed the underlying issue with the latest beta?
Thatās also a possibilityā¦ There are a few periods when Negative Lab Pro has to access and update the Lightroom Catalog itself, and one of them is when you click āOKā it is writing the NLP metadata to the file. Iām sending you a PM about trying this not in trial modeā¦
Iāve got volumes for macOS 11 (Big Sur) up to macOS 15 (Sequoia Beta), the latter without (M15) and with Rosetta (M15R). M99 is a shared volume that contains e.g. my test images.
I get the macOS installers through the links provided by āmrmacintosh.comā
