“Fathered” a few of them as well…

Welcome to Salmonella Beach!

https://en.m.wikipedia.org/wiki/Olympic_Truce

https://github.com/sjpiper145/MakerSkillTree

Very interesting way to present things and track progress.

Tdarr and its Health Checks is the first thing that comes to mind:

https://docs.tdarr.io/...

Elon Musk n’a décidément rien inventé…

Fribbtastic has an excellent answer:

https://lemmy.world/comment/11608364

Tdarr has many usages revolving around transcoding. I use it for space optimization mainly but you can build your own workflow/pipeline to only do integrity checks… It will check that the file is eligible prior to attempting to transcode and check new files added to your library as Tdarr is designed to run continuously, checking and transcoding as configured. I’m not sure it is relevant to your specific issue but you could try the handbrake/ffmpeg health checks commands outside of Tdarr first on a file you know has the problem and if it works, automate the thing through Tdarr to do the same check on the entire folder/library. This would only help you in flagging them. I’m not sure about repairing though and usually I would look for a new version in case of issues. The question on the transcoding behavior is complex to answer as it depends on hardware on both server and client but you could run Tdarr without changing anything on this side. Please do go through the Tdarr documentation before actually running it across your entire library. My concern is that on my library none came back with a failed health check while a few do fail during transcode to x265 so again I don’t know if that will work for you.