Finding FFmpeg issues before they happen

[DDoors]

Hello, I was wondering if any of you know of ways to catch issues like below before they happen.

[mp3 @ 000002c3ef0ca180] Format mp3 detected only with low score of 24, misdetection possible!
[mp3 @ 000002c3ef0ca180] invalid concatenated file detected - using bitrate for duration
[mp3 @ 000002c3ef0ca180] Estimating duration from bitrate, this may be inaccurate

If possible;

What you do with music before adding it to your collection?

If you was looking for any issues in your collection how would you go about finding them? and potentially fix said issues

Thanks!

[TheDreadPirate]

Is any of your music not playing? If everything is fine, I wouldn't be concerned.

I don't look for issues until I encounter them. Even with my small-ish collection, manually finding any issues is difficult or impossible.

[bitmap]

Oh boy...searching for issues is impossible unless you manually examine and/or encode every single file before adding. Looking at ffmpeg warnings/issues, some are just reporting why data might be inaccurate -- the media may still function properly. Lots of timestamp issues for audio, Dolby audio-specific DTS problems, improper bits or images at the beginning of a file are inconsequential. Other times, they're catastrophic. I'm not sure being proactive about this will do anything other than cause you to pull out your hair.

You could possibly script something to check your log files and pull out warnings or errors and notify you, but hunting down the actual problem is an art form and fixing them is trial and error at best. Much of the time you'll cause more damage to the media than fixing anything.