Reprocessing metadata

I see Reprocessing Metadata messages like:
2023/10/29 20:05:25.971031 [SCN] Reprocessing metadata for TV episode #9303 MASH\Season 08\S08E24 - Back Pay.mp4: 589646772 != 589571775
2023/10/29 20:05:26.494319 [SCN] Reprocessing metadata for TV episode #9295 MASH\Season 08\S08E25 - April Fools.mp4: 578497882 != 578423923
2023/10/29 20:05:26.862402 [SCN] Reprocessing metadata for TV episode #9304 MASH\Season 09\S09E01 - The Best of Enemies.mp4: 572461857 != 572534962
2023/10/29 20:05:27.195593 [SCN] Reprocessing metadata for TV episode #9305 MASH\Season 09\S09E02 - Letters.mp4: 570245173 != 570318137
2023/10/29 20:05:27.508947 [SCN] Reprocessing metadata for TV episode #9306 MASH\Season 09\S09E03 - Cementing Relationships.mp4: 593080355 != 593155791

repeatedly, suggestions as to why? I haven't looked at logs in a long time so I don't know when this started. I have all of MAS*H downloaded to my library, some time ago (years).
Thx

I agree with the comparison that they're not equal.
But what does it mean?

Maybe file size?

@kb2tdu If you update to the latest pre-release build the log message will be clearer.

This is just now, from the latest available release 2023.10.29.0156.
2023/10/29 21:05:14.707654 [SCN] Reprocessing metadata for TV episode #9312 MASH\Season 09\S09E20 - The Life You Save.mp4: 584835957 != 584760312
I'm afraid I still don't know what the non-matched numbers mean nor how to resolve.

The latest pre-release version is 2023.10.30.0034

Put up the latest prerelease version and the message tells me about changed file size. Further investigation reveals I have duplicate files for the shows appearing in the message. So the issue is resolved. Thanks!
P.S. this is an artifact of a weird behavior of the disk array manager I'm using (Drive Bender) where I managed to get 2 files with the exact same filename in the same directory (dozens of times). I know how it happens and it's an edge case that the developer declines to further investigate. FYI.

What do you mean by the same filename? Filenames are unique within a directory for all filesystems that I'm aware of.

Died at 12 years old

Sounds crazy... Yeah... if you have a solution that randomly presents two different files under the same filename at different times, you're gonna have a bad time...

You'd think so, wouldn't you. Yet when I use drag and drop over the LAN to copy something onto the LAN-shared DriveBender drive, it can put two files of identical name into the same folder. It can even have identical size and timestamps. On the local machine, it won't allow it but somehow going through the SAMBA/NFS stack it allows this error. Causes me grief with my back-upper (Backblaze) too. Looks like DriveBender is in hospice so I need to find a replacement anyway.