You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The date anomoly in AVI files is because they have incorrect metadata, see example below. Conversely the Google Photos metadata is somehow correct. When I do a local folder comparison pass I extract the create date using ffprobe and write it into the DB, thus trashing the order. The actual metadata comparison is a good way to identify if two files are a copy of the original so probably want to keep this ffprobe.
Solutions?
dont use ffprobe and rely on Google meta data only.
do ffprobe but have a separte column in the DB for these dates, only used for comparison
comparison is a relativley rare (expensive) operation, could simply always re-run a normal scan with --flush-index afterward (which is what I'll do right now while I think about this)
Note that fixing #57 will remove the issue of the order of items in folders. But the create date (which gets shown in the filesystem as file Modified Date) will be 'wrong'. Wrong in quotes because one of Google Photos metadata and internal ffprobe metadata must be wrong, in the example I found it looks like Google is the more likely correct but this might not always be true?
I'm going to address #57 and close this issue. Having ffprobe metadata dates in the DB is not issue for the rare cases this is going to happen as long as there is the correct sort order in albums.
The date anomoly in AVI files is because they have incorrect metadata, see example below. Conversely the Google Photos metadata is somehow correct. When I do a local folder comparison pass I extract the create date using ffprobe and write it into the DB, thus trashing the order. The actual metadata comparison is a good way to identify if two files are a copy of the original so probably want to keep this ffprobe.
Solutions?
Originally posted by @gilesknap in #57 (comment)
The text was updated successfully, but these errors were encountered: