Incorrect File Creation ("Date Added") Time and Date

[bitfidelity 1]

There's a weird bug where the "date created" time of some scanned media are an hour earlier than what's correct, resulting in both an incorrect time and date.

Example:

File creation date: Saturday, ‎July ‎18, ‎2020, ‏‎12:00:00 AM

Emby "Date Added": 7/17/2020 11:00 PM

 

[Luke 42081]

Hi, have you checked the time zone on the server machine to ensure that it's correct?

The value is either coming from your pre-existing nfo file, or that's what the .net core file API is giving us as the date created timestamp.

[bitfidelity 1]

16 minutes ago, Luke said:

Hi, have you checked the time zone on the server machine to ensure that it's correct?

The value is either coming from your pre-existing nfo file, or that's what the .net core file API is giving us as the date created timestamp.

Do you mean the system time? If so, they're correct, as Windows sets those automatically.

What's peculiar is that I'm only running into this problem with certain files.

Edited December 26, 2021 by bitfidelity

[Luke 42081]

Do those files have nfo files next to them?

[bitfidelity 1]

I'm not using any .nfo files.

[Luke 42081]

@bitfidelity

Can you please show us a specific example using screenshots of what you see in both Windows Explorer and Emby Server? Thanks !

[bitfidelity 1]

@Luke

This is from a fresh scan.

Edited December 29, 2021 by bitfidelity

[Happy2Play 9782]

Best guess is Daylight saving as it is showing a 1-hour difference.

Will have to test this again but yes your image shows a difference in file vs imported UTC/browser display.

[Happy2Play 9782]

In my basic test I currently cannot reproduce this as I am getting actual datetime.

What client are you seeing this issue?

What library content type?

[bitfidelity 1]

@Happy2Play

I'm using Emby Web 4.6.7.0 via Chrome. The content type is Movies.

[ebr 16185]

Hi.  And what does this screen look like on the machine?

[bitfidelity 1]

@ebr

[Luke 42081]

@bitfidelity are you still running into this?

[bitfidelity 1]

@Luke

Yes, I was actually about to ask whether anyone found a solution to this. Is it possible that there's some sort of leftover metadata that is doing this? Not sure what else it could be.

[Luke 42081]

Can you reproduce with a brand new video file ?

[bitfidelity 1]

I rescanned my library with some new movies, and the problem remains.

[cul8rmom1 5]

What happens when you tell it not to set the time automatically?  Does it show the correct time?

If you set the time manually say 5 hours into the future do the file dates show that?  Or is it getting the time data from the upside down or something.

Where are you getting the data from?

Try copying it from one directory to another instead of moving it.  It should make the modified and created date the same instead of pulling keeping some of the old stuff.

Wait … file creation date .. .and added date.  Does it make the date the time that it is added to emby and you have it scanning every hour or something?

Seems like an interesting issue.

[bitfidelity 1]

I don't think Windows' settings have anything to do with it, as it's only affecting certain files. I don't think I have any choice but to ignore it.

 

 

Edited January 15, 2022 by bitfidelity