Traktor analysi erroeously reports track corruption errors

Phill

I've been seeing this Analyze error pop up with occasional / several Tractor analysis imports since version 4 was realease (possibly earlier) I have been completely rebuilding my track collection of some 54,000 tracks over the past several weeks. Yesterday was my first rebuilt Track import of some 3500 tracks.

As part of my cleaning steps I have been careful to look for corrupt Tracks using two different tools looking for corrupt Audio frames and corrupt headers. Except for 5 tracks intentionally seeded in the import queue (that have unwritable tag blocks) None of the imported track showed errors in my pre-import diagnostics but Traktor kept reporting frequequent corruption errors. Around 590 of the 3600 tracks imported were reported corrupt.
I have a powershell script that uses TABLIBSHARP.DLL to look for inidcations of corruption by way of the PossiblyCorrupt Field which is computed as taglib reads the track. The logs show no reason why Traktor thinks its corrupt only that it is. Retesting the tracks after import shows none of the tracks are reported corrupt.