There has to be a way to not lose images in the filmstrip within “Projects”! What a real pain to have to go back and “fix the image path”. Especially when nothing has changed within my catalog, SSD, etc. No name change, no rating, etc. Good grief!
I have seen other posts about this but having to delete folders, etc. is just plain abysmal!
Move images and/or directories outside PL may cause “lost” images.
Present the original images but on a different drive, will cause “lost”" images.
You’ve found a new scenario that cause the problem or you have found a bug.
Typically “lost” images occur when you undertake any movement of images that have been added to a ‘Project’ outside PL.
Sadly, PL still do not provide the ability to move directories within PL, images - yes, directories - NO!
There is one other classic situation that can cause grief, with respect to SSDs, is it the same SSD you used when you created the images added to the ‘Projects’’ and I don’t mean “has it got the same Drive Letter”?
PL identifies drives by their drive id and not by their drive letter. Present all the same directories with all the same images and the same drive letter and you will have lost all the ‘Project’ contents that related to the original drive, if the drive identifier does not tally with the one in the PL database.
Otherwise follow @platypus’s advice. @platypus is a Mac user and I am a Windows user but I am unclear about which platform you use!?
Thanks. I have screenshot and screen-video’d this issue for the DxO supports team. Not sure what they will come up with on this as there isn’t any real hiccup to the opening and functioning of the program. Only lost images within the “Projects” folders.
HI, Thanks for this. I haven’t changes any of my directories. So weird. The past two updates blew this issue up - both times! Ugh. I was able to spend the time to recreate the Projects the first time but there were so many missing the 2nd go around that I found the whole situation untenable! I do have a ticket # on this issue and DxO has been working to look to resolve the issue. Thanks again.