Scanning photo library crashes PMS

How difficult is it for you to apply a date of something newer than 1 January 1970 ?

I ask this because the server is refusing to accept the negative date:

May 12, 2021 20:37:48.193 [0x7f25c9b8e728] WARN - HTTP error requesting GET http://127.0.0.1:32400/library/changestamp (56, Failure when receiving data from the peer) (Recv failure: Connection reset by peer)
May 12, 2021 20:37:48.193 [0x7f25c9b8e728] ERROR - HTTP -56 downloading url http://127.0.0.1:32400/library/changestamp
May 12, 2021 20:37:48.193 [0x7f25c9b8e728] ERROR - Exception inside transaction (inside=1) (../Library/MediaItem.cpp:1721): Unable to allocate a changestamp from the server
May 12, 2021 20:37:48.193 [0x7f25c9b8e728] ERROR - Exception thrown during analysis: Unable to allocate a changestamp from the server

I am running this command to set the meta dates from the file properties. Will take a couple minutes to run then I will try scanning again.

exiftool -overwrite_original "-ModifyDate<FileModifyDate" "-CreateDate<FileModifyDate" *.tif

Which date did you choose ?

It’s copying the file modified dates from the file system… they were all modified today when I re-encoded the .tif files so they will all have today’s date.

Excellent!

Looks like it still crashed… sending another log

Maybe it doesn’t like DateTimeOriginal meta set to 1968 either I can reset that

It will not like any dates before 1 January 1970 (negative time in seconds).

It should be graceful about that and not crash but definitely generate errors.

So it’s not possible to display photos in the timeline taken before 1970 ?

I’m not sure how it’s done. I’m waiting for an engineer to answer.

It’s definitely illegal to have a negative date on Linux . This is what I’m trying to get answered now. "how do they do it? "

Would you mind reposting the date/time info again which shows what’s there now?

I updated it to this (1971) and the scan is making it farther:

[System] FileModifyDate : 2021:05:12 21:43:55-06:00
[System] FileAccessDate : 2021:05:12 21:43:55-06:00
[System] FileInodeChangeDate : 2021:05:12 21:43:55-06:00
[IFD0] ModifyDate : 2021:05:12 21:43:45
[ExifIFD] DateTimeOriginal : 1971:01:01 00:00:00
[ExifIFD] CreateDate : 2021:05:12 21:43:45
[ICC-header] ProfileDateTime : 1998:02:09 06:49:00

I think that was it… I will try and rename a picture with a 1968 date per @trumpy81 's suggestion and see if that works any better.

PMS isn’t going to care about the name.

It’s going to look at the EXIF data inside it.

Yep. Found this:

We’ll try as hard as possible to extract the taken date from EXIF tags. Different vendors may store these using different tags but we look in the following tags in this order:

DateTimeOriginal
DateTime
DateTimeDigitized
CreatedDate
ModifyDate

If we fail to find any EXIF date information then we’ll fall back to using the earliest date in the file info, this is either created time or last modified time.

Interestingly linux lets me set a 1955 modified date:

image

Then that matches what I see in PMS.

The challenge is “how to get you scanning photos”.

Can these be broken into trees where you add maybe 5000 at a time?

(PMS has no limit as to how many folders are listed for a library)

They’re already scanned… I can run a batch file to fixup the meta on the files to post 1970. I could also make a second photo library for testing this stuff.

Out of curiosity, what was the source of these? Flatbed scanner of real photos?

I’m trying to figure out how I can stress test PMS from my side (without having 75000 TIFF files)

One of these… you can load it up with 50 slides at a time.

https://www.scandig.com/filmscanner/nikon/nikon-super-coolscan-5000-ed-feeder-silverfast.html