Still no update of TimeLineView

[rienvanham]

Hi Mario,

Today I added around 10 files (file was created on that moment as a PDF) to my folders and iMatch didn't update the TimeLimeView. I added the files while the "Media & Folders"-view was active. And this moment the TimeLine-view still doesn't show any files for today. Refresh didn't help; stop and start of iMatch didn't help. This is unworkable for me because now I have to search for the files before I can add keywords, author etc.

How difficult is it to return to the previous version. I NEVER had any problem with adding files in the previous version.

Thanks in advance!

Rien

Oh... the files are present in "Categories -> Files Added Today".... ??

p.s. in next post all metadata of 1 file.

[rienvanham]

Metadata

[rienvanham]

Screenshots

[thrinn]

For me, it works:

• I created a new PDF (by printing to PDF)
• Rescanned folder - PDF was recognized as new.
• Timeline shows newly added PDF under date of today

So, seems to be something specific to your environment. Maybe try with debug logging enabled? I think Mario will request the log file.
I presume to did run a DB diagnosis, just to rule out some inconsistencies?

Just in case: You are using PDFs scanned by FineReader? I also have FineReader (V15, not V16, but still...). Maybe try to produce a PDF by creating a simple text file (one line of text will do) and create the PDF by "Print", using "PDF-XChange for ABBYY" as printer. Just to rule out it has something to do with the way PDFs are created.

[rienvanham]

Hi Thrinn,

Thanks for the suggestions but................

I have nothing changed in my workflow between iMatch 2021 and 2023. iMatch 2021 works as expected but 2023 shows this behavior. It MUST have something to do with the ZULU-time:
e.g. Dated Subject Created (after click on it): 2023:06:21 08:32:50Z
if I change this to: 2023:06:21 10:32:00 it appears in the TimeLineView (10 others still not).

Thanks,

Rien

[rienvanham]

Screenshot

[rienvanham]

System setting

[Mario]

None of my PDF shows this behavior, no other user reported anything similar.
I'm in the same time zone as you.

Please attach on of your PDF files that causes this issue.
Screen shots don't help much in such cases.
I need them material and information that allows me to reproduce the problem here. Then I can fix it or give advice.

Also attach a ZIPed copy of the the IMatch log file in Debug logging mode (see log file) from an IMatch session where you added one of these PDF files and experienced the problem. Maybe the log file has something to tell about the problem.

Also, screen shots from 3rd party tools output don't help.
We'll get much better information, including MWG mapping, when you use the built-in ExifTool Command Processor with the "List Metadata" option and then attach the results as a text file.

But, most important, I need a PDF file that causes this problem.

[rienvanham]

Hi Mario,

First try to send you the information.

[axel.hennig]

This is shown within my PDF-reader when viewing the metadata (if it helps).

[thrinn]

Interesting. When I import the sample PDF it appears first in the Timeline under the 1899/Dezember/30 node.

@rienvanham: Could you check if you also find your files under year 1899?

[axel.hennig]

Same here. The file appears in 1899 - December - 30.

[axel.hennig]

VarToy gives me (I'm in Germany so +02:00):

Code Select Expand

{File.DateTime}
{File.DateTime.Local.TZO}
{File.DateTime.Original.TZO}
{File.DateTime.UTC.TZO}

21.06.2023 11:09:46
21.06.2023 13:09:46+02:00
21.06.2023 11:09:46Z
21.06.2023 11:09:46Z

[Mario]

Probably related to https://www.photools.com/community/index.php/topic,13319

[rienvanham]

Hi Thorsten,

YES! They appear under 1899, december 30.

Thanks for investigation.

[Mario]

Hm. This is going to be one of those problems.
Because, when I add the PDF file to a database, I

a) get 2023:06:21 11:09:46Z as the "date subject created", which is set from the PDF's create date - OK

b) the file shows up on the right spot on the TimeLine:

YES! They appear under 1899, december 30.

This sounds like, for some reason, the "update" of the time line node is not happening for the affected users.
When the file is added to the time line initially, it may have no valid date yet. Then 1899/12/30 is the default/fallback date, the earliest supported date.
But, usually, when the import of the metadata has finished, the file timestamp is updated (which it is, since File.DateTime and Date Subject Created are valid) and this moves the file along the time line to the correct location.

This why changing the date subject created (time zone or otherwise) or just marking it as modified by clicking the pen icon in the MD panel fixes the problem. This changes the global File.DateTime and this shifts the image on the time line.

This is what happens here, but apparently not everywhere. I shall investigate this. Hopefully I can reproduce this somehow.

[thrinn]

I just remembered that there is a "Rebuild Timeline" command (File > Database tools).
After executing it, the PDF shows up at the correct position in the timeline.

[Mario]

I just remembered that there is a "Rebuild Timeline" command (File > Database tools).
After executing it, the PDF shows up at the correct position in the timeline.

I know. But that command was mostly designed to be used when the time line is switched to another "source" - a feature I had planned but that was never needed in the end.

The time line should always be correct. I need to dig into this and see if I can reproduce it somehow.
Changing the global File.DateTime should always update the time line. Which is clearly not happening on some PCs...

[axel.hennig]

"Rebuild Timeline" also solved it on my system.

[Mario]

For those who can reproduce this problem:

Switch to debug logging,
Close IMatch. Make a copy of the file in Windows Explorer.
Restart IMatch and rescan the folder.

New file in the wrong spot on the time line again?
Search the log file for CIMTimeline::OnFileAdd and CIMTimeline::OnFileUpdate
Do both method markers show in the log?

[thrinn]

Performed your steps.
CIMTimeline::OnFileAdd found in the log.
CIMTimeline::OnFileUpdate NOT found in the log.

[Mario]

CIMTimeline::OnFileUpdate NOT found in the log.

Interesting. That's what's causing the problem. But why?

When a file record is updated (after the scan has completed, the user changes something), IMatch checks if the date and time of the file has been modified. And if that's the case, it updates the time line.

When a new file is added to the database, it is also added to the database CIMTimeline::OnFileAdd
At this time, the file has no File.DateTime yet. It is 0, and this means 1899/12/30.

When the file is later updated (several times, e.g. when metadata has been ingested), IMatch should see a change in the File.DateTime and update the time line, calling CIMTimeline::OnFileUpdate

Interesting. Why does OnFileUpdate not being called...on your machine. Here it works just fine with two databases and on two computers....

I'll try something for the 2023.1.10.
Let me know if it works with that version. It will be released soon.

[rienvanham]

For what it's worth;
I have an AMD-system with a 5950X, 64 GB memory, nVidia 3090 card. 

[thrinn]

I'll try something for the 2023.1.10.

Whatever you tried - with IM 2023.1.10 it works for me.
I repeated the steps from your previous post.
Now, I can find CIMTimeline::OnFileAdd and CIMTimeline::OnFileUpdate both in the log file. And the file appears under the correct node in the Timelime.

So, from my perspective, it is fixed.

@rienvanham: ...but maybe you should also try it, as the one who first stumbled upon this issue.

[rienvanham]

Yes! I tried it and the file now immediately appeared in the TimeLineView on the correct date.

It seems to be solved; tomorrow I will do a bigger test.

Thank you all!

Regards,

Rien.

[rienvanham]

It works OK for me! Thank you!