Photo Supreme

I strongly believe that there is some sort of race condition occurring in the sync process when files are replaced, since the failures are random in nature and number. I've seen it happen with a batch of as few as 37 replacement files in a batch, and had successful syncs with batches of 100 ...

This is not the case here. These are all JPEG files with .jpg extensions. The two files in question give problems on my Desktop PC, but not on other PCs, which would seem to point to an issue in the Windows environment on this PC. 'Tis a puzzlement.

Hert has come back to say that he couldn't find any problems with the files. After further investigation here, I found that the issue lay in my PC, because when I copied the files to my other PCs, the issue was not present on those PCs.

What's causing this, I have no idea, we've eliminated a number ...

Gradually working through my collection removing and then recreating clean XMP metadata in batches.

For the most part it's working, but I have come across a couple of files that when I use PSU to remove the XMP, File Explorer and other image handlers (e.g. Paint.Net) can display and open the files ...

gcoupe wrote: 22 Nov 24 17:07 Hert suggests that I use PSU to remove all XMP metadata from my collection and then use PSU to recreate clean XMP metadata. I'll give this a go (testing small batches to start with...).

This procedure works, but rather than run it on my entire collection at once, I'll use it in batches...

Thanks, but Hert has done further investigation on a sample file. It looks as though the XMP marker holds wrong data, and while PSU can deal with this, Windows File Explorer doesn't.

Hert suggests that I use PSU to remove all XMP metadata from my collection and then use PSU to recreate clean XMP ...

I thought I would try applying a tag to a file directly via the Windows Properties screen. However, when I tried adding a Test tag, I got an error:
Screenshot 2024-11-22 144922.png

This on a file that has blank Title and Tag fields.

On files where the Title and Tag fields are displayed correctly ...

Further to the above post, Hert tells me that as far as he knows, Windows reads the embedded XMP to populate the Windows Properties fields, so the finger of blame would seem to point to Windows not reading the XMP metadata for some files.

Wish me luck in getting Microsoft to pay any attention to ...

Something else odd that is going on...

The photos on my PC are synced to the OneDrive cloud. When PSU writes the Title and Tag fields in Windows Properties, then the photo in the OneDrive cloud will have the full complement of tag metadata displayed. If PSU does not write into the Title and Tag ...

Just an update to this saga. I followed the suggestions above, but synchronising a folder with multiple changed files still caused the creation of false duplicate files. As a result, I've repeated the scenario and sent OneDrive and Fiddler logs to OneDrive Support at their request for further ...

I've just come across this discussion thread because I've discovered that some of my photos are showing tags in Windows properties and others are not. This goes for photos taken on the same day. For example, these two photos taken with my Android phone and imported into PS. Also, the photo with the ...

Well, the telephone support was a success inasmuch that I was able to demonstrate the problems to the support person. He first pointed me to this troubleshooting page: https://support.microsoft.com/en-us/topic/duplicate-files-in-onedrive-fd47ce5e-8dd0-465e-9e3a-461e1a3cf613 However, it was not ...

This issue is still giving me problems. I've now tried @barneagle 's workaround by moving the folder hierarchy containing my photos to a staging folder outside of OneDrive, and then will sync this with the copy in OneDrive.

However, I'm not convinced that this will solve the problem. I suspect that ...

Hmm - I tried the workaround of pausing OneDrive whilst I used Photo Supreme - and it didn't work. I added a label to 121 images, and 33 of them got created as a copy with the PC name appended...

Microsoft strikes again...

I realise this is an old thread, but after doing some major updating of my photo metadata in Photo Supreme, I've run into the same problem.

I think the only workaround is to pause OneDrive's automatic sync (you get a choice of 2/8/24 hours) while using Photo Supreme, and then restarting OneDrive ...