flashing metadata
flashing metadata
Recently it is not uncommon for one or more files in a folder to have the metadata below the thumbnail flashing. Any idea what would cause that or how I can correct it?
Re: flashing metadata
I had this exact issue with a small number of files for some number of months in 2021. Like you I usually am using the Custom Thumbnail Info view and have some label rows that were comprised of multiple macro values.
I recorded diagnostic data back in November 2021 and got to the point of noting that there are two Collection Macro Parser.TMacroImageValueHandler threads that get locked into a loop where the actions of the one presumably perpetuate the actions of the other and vise versa.
Based on your seeing it it clearly is still a potential issue when the right circumstances arise, but I took some steps that made it go away for me, so I didn't run it down any further at that time.
Based on noting that the first iteration of the two threads responsible for the flashing resulted in search data being updated with valid date info such as:
('30541A852958448BA31942AB2EBC0D88','F18C502FA171451D8B10606CAD07F3A5','CATITEM','PHOTODATE','05 February 2014' ),
('95A5C20007F9459290609342449C0DBE','F18C502FA171451D8B10606CAD07F3A5','CATITEM','ALTPHOTODATE','February,2014' )
But then each iteration after the first wrote invalid date info like this:
('2C32F1DE13B342C895F1316A590F2B89','F18C502FA171451D8B10606CAD07F3A5','CATITEM','PHOTODATE','30 December 1899' ),
('04D0C8D843944EE28A408EE5CFEC1606','F18C502FA171451D8B10606CAD07F3A5','CATITEM','ALTPHOTODATE','ember,December,1899' )
... I took several steps including ensuring relevant date fields were populated but probably more importantly I made everything for those items was exported to xmp sidecar, made sure there weren't any invalid dates buried in some property by directly editing the xmp file, cleared the xmp data in the database for the impacted files and re-imported from the xmp sidecar file.
I also ran a 'Compact Current Catalog' operation. I may have done other things too, but those are what I specifically remember, and the issue finally went away and I haven't had it return for any images in the now 7 months since then.
I am of course not disagreeing that whatever allows the two competing threads to become locked in a loop should be fixed with the application even if the circumstances that give rise to it are quite rare, but figured you might want some info that could facilitate a faster resolution than tracking down the root cause and getting a fix applied might entail.
I recorded diagnostic data back in November 2021 and got to the point of noting that there are two Collection Macro Parser.TMacroImageValueHandler threads that get locked into a loop where the actions of the one presumably perpetuate the actions of the other and vise versa.
Based on your seeing it it clearly is still a potential issue when the right circumstances arise, but I took some steps that made it go away for me, so I didn't run it down any further at that time.
Based on noting that the first iteration of the two threads responsible for the flashing resulted in search data being updated with valid date info such as:
('30541A852958448BA31942AB2EBC0D88','F18C502FA171451D8B10606CAD07F3A5','CATITEM','PHOTODATE','05 February 2014' ),
('95A5C20007F9459290609342449C0DBE','F18C502FA171451D8B10606CAD07F3A5','CATITEM','ALTPHOTODATE','February,2014' )
But then each iteration after the first wrote invalid date info like this:
('2C32F1DE13B342C895F1316A590F2B89','F18C502FA171451D8B10606CAD07F3A5','CATITEM','PHOTODATE','30 December 1899' ),
('04D0C8D843944EE28A408EE5CFEC1606','F18C502FA171451D8B10606CAD07F3A5','CATITEM','ALTPHOTODATE','ember,December,1899' )
... I took several steps including ensuring relevant date fields were populated but probably more importantly I made everything for those items was exported to xmp sidecar, made sure there weren't any invalid dates buried in some property by directly editing the xmp file, cleared the xmp data in the database for the impacted files and re-imported from the xmp sidecar file.
I also ran a 'Compact Current Catalog' operation. I may have done other things too, but those are what I specifically remember, and the issue finally went away and I haven't had it return for any images in the now 7 months since then.
I am of course not disagreeing that whatever allows the two competing threads to become locked in a loop should be fixed with the application even if the circumstances that give rise to it are quite rare, but figured you might want some info that could facilitate a faster resolution than tracking down the root cause and getting a fix applied might entail.
Re: flashing metadata
Wow, thanks aaronj for the detailed solution that worked for you! I'll chase down those entries but it looks like you found the problem. Super appreciated!
Re: flashing metadata
All the images with flashing metadata show a date on the time line as 1899. They also all show as out of sync. I cannot find 1899 in any metadata fields and no matter what I do, they stay out of sync. I'm at a loss as to how to fix this!
Re: flashing metadata
Maybe you can share a sample file here that refuses to sync. Make sure that you remove any personal details from a file before sharing it on a public forum.
Better yet: for tech support, always best to send a support message.
support@idimager.com
https://www.idimager.com/contact-us
Better yet: for tech support, always best to send a support message.
support@idimager.com
https://www.idimager.com/contact-us
This is a user-to-user forum. If you have suggestions, requests or need support then please send a message