Closed grainsoflight closed 7 months ago
Unfortunately no, looks like the fields are still empty
Did you refresh and rescan metadata? It's definitely working for me now.
To sanity check, rename the file so it's ingested from new.
Im getting a persistent error with metadata processing
An exception occurred in the database while saving changes for context type 'Damselfly.Core.Database.ImageContext'. -- | | | | | | 16:42:07.876 | ERR | Failed executing DbCommand (0ms) [Parameters=[@p23='?' (DbType = Int32), @p0='?' (DbType = DateTime), @p1='?' (DbType = Double), @p2='?' (Size = 7), @p3='?' (DbType = Int32), @p4='?', @p5='?', @p6='?', @p7='?' (DbType = DateTime), @p8='?' (Size = 19), @p9='?', @p10='?', @p11='?', @p12='?' (DbType = Boolean), @p13='?' (DbType = Int32), @p14='?', @p15='?' (DbType = Int32), @p16='?' (DbType = DateTime), @p17='?' (DbType = Double), @p18='?' (DbType = Int32), @p19='?' (DbType = Double), @p20='?' (DbType = Int32), @p21='?' (DbType = DateTime), @p22='?' (DbType = Int32)Is there more error info than that in the logs? That's not much to go on. I wonder if the DB schema change didn't work when it upgraded to the new version....
If the metadata isn't working, you're not going to see the new data.
Actually, ignore this - I can see the error. Investigating.
Okay, dev should be better now. Can you try it out?
SUCCESS!
WOOT!!!
Thanks. I'm going to make a patch release. :)
Im running into an issue where the "Date Taken" information seems to be displaying the date the image was imported into damselfly. I am editing the capture date/time metadata in lightroom, though when I write it to the file, it does not change in damselfly. Other metadata, such as tags, do change when updated. Additionally, the date shown in damselfly does not seem to match any data in the metadata, as both the existing capture and digitization dates were in 2022 and the changed date is 1988, though damselfly has always shown 2023. No date ending in 2023 has ever existed in the file metadata.