Copy link to clipboard
Copied
Hi everyone
(Yes, that is correct, I'm still using 6.14 as I can't justify a monthly outlay for Lightroom in my current financial circustances)
I'm currently trying to make my photo storage more redundant. I used to just store my photos on my Synology NAS but as that didn't provide any actual backup of my images when my laptop decided to die earlier this year I replaced it with a desktop machine (unexpected bills, yay...) with a big HDD to store the photos on and use the NAS properly as a backup.
As I also needed to have a good sort out of the images I'd got stored I'm gradually working through my catalog, deleting images and then moving them over to the local drive via Lightroom. This was working well enough until the last few days when Lightroom has started shutting down during the deletion process. Lightroom does delete the files from the NAS but then crashes before removing reference to the images from the catalog, as when I restart Lightroom and go to the folder the images were removed from, Lightroom still shows the previews for them and complains the images can't be found...
I've been able to work around this somewhat by right-clicking the folder the files were being deleted from in Lightroom and selecting Synchronise (although this again causes Lightroom to crash) but it's not ideal.
Last night also brought to light a new problem in that trying to open the People module also causes Lightroom to crash. That appears to happen regardless of whether the folder I have selected at the time is on the local HDD or on the NAS>
This morning I've tried uninstalling Lightroom completely and reinstalling again but this doesn't appear to have helped.
Does anyone have any suggestions for what I can do to resolve this?
(My system is self-built, Win 10 Pro version 2004 build 19041.685)
Try running the program in Windows 8 compatibility mode. I was experiencing a crash wehen removing photos and when accessing the People module. Seems to be working again now, fingers crossed.
Copy link to clipboard
Copied
Try to change your system date, last year for instance. Everything works then. It's an obvious obsolescence program. They need to be prosecute for that
Copy link to clipboard
Copied
here's an applescript that works on big sur
on run {input, parameters}
set ntpdPID to do shell script "systemsetup -getusingnetworktime; exit 0" with administrator privileges
if ntpdPID is "Network Time: On" then
do shell script "systemsetup -setusingnetworktime off" with administrator privileges
do shell script "systemsetup -setdate '01:01:2020' -settime '12:00:00'" with administrator privileges
else
do shell script "systemsetup -setusingnetworktime on" with administrator privileges
end if
tell application "Finder"
activate application "Adobe Lightroom"
end tell
delay 10
do shell script "systemsetup -setusingnetworktime on" with administrator privileges
return input
end run
Copy link to clipboard
Copied
Great news for Mac users I think I have it :
open libfrsdk-8.6.0.so with hex fiend for instance ( Applications ▸ Adobe Lightroom ▸ Adobe Lightroom.app ▸ Contents ▸ Frameworks ▸ CIT ▸ Plug-ins ▸ FaceRecognition ▸ FaceRecognitionCognitec.bundle ▸ Contents ▸ Resources)
search for 48 8D 3D 62 22 88 00 hex string and replace with 48 8D 3D 64 22 88 00
It works for me with 56000 photos no crash anymore and no need to change system date 😉
Only drawback is when I import a new photo, LR detects a face but doesn't provide a name. But I can still put a name so it's fine for me.
Maybe an other value allows this to work but it's ok for me.
If someone is interested I use cutter to open the file and search for anything that rings a bell (that was the first time I reverse something)
So happy !!
of course if you do this save everything before 😉
Copy link to clipboard
Copied
I looked at the Windows Event Viewer and found that the failing module was:
C:\Program Files\Adobe\Adobe Lightroom\CIT\Plug-ins\FaceRecognition\libfrsdk-8.6.0.dll |
I just deleteed that FaceRecognition directory, effectively removing the Facial Recognition plug-in, and that fixed all my crashes.
Selling a permanent license to software that internally has an expiration date on a feature is what I consider an unacceptible business practice, and the reason I no longer do business with Adobe.