Consistency Check does not update files

YCarlos

Hi everyone,

I’m running into an issue with Consistency Check and was wondering if anyone has found a solution.

I recently updated the metadata of a large number of tracks, specifically the Comments tag. The changes were written successfully to the files themselves, and I can see the updated comments correctly in iTunes / Apple Music and other tag editors.

However, when I run Consistency Check in Traktor, the Comments field does not get updated in the Traktor library. Traktor continues to show the old comments.

Is there a way to force Traktor to refresh metadata from the files without having to remove all tracks from the collection and import them again?

Ideally, I’d like to keep all existing analysis data, playcount, beatgrids, and collection information intact while updating the Comments field from the source files.

Has anyone encountered this before, and is there a recommended workflow?

Thanks!

djcoryminto

Yes this is expected but indeed detrimental Traktor behavior. The best way I can describe it is that certain metadata fields Traktor reads & writes constantly (artist, title are two definites here), and other proprietary fields it stores inside the collection file and never reads or writes to ID3 (think comment 2, key text, producer, as these do not exist as ID3 tags). However, there is a third group of metadata fields that it will indeed READ BUT UPON FIRST IMPORT ONLY. Comment field is part of this third group; meaning, Traktor will read the comment field from ID3 upon first import into Traktor, but from that point forward, Traktor takes over administration of this field as a now-proprietary field, storing the info and any future changes in collection.nml and never writing to the ID3, and as such, only reads the comment ID3 upon FIRST import and never again. It takes over admin duties. This is the case with comment, remixer, and a few others. Someone could make a good chart of these expected behaviors per field.