Print

Please login or register.
1 Hour 1 Day 1 Week 1 Month Forever
Login with username, password and session length

[craft]

null

[scthom]

There are a number of instances where if you just add the field to your library, MC will use the standard ID3v2 tag.  So try adding the Label and Catalog# fields to your library, and see if it works.

Are there even standard ID3v2 tags for that?  Apparantly not.  http://www.id3.org/id3v2.3.0
Once you add those fields, you can configure MC to write those fields to tags so as not to lose the data.  Most likely they'll end up in "Comment".

[craft]

null

[Alex B]

MC reads and writes many (but not all) ID3v2.3 v tag frames. If the file contains some ID3v2.3 tag frames that are not recognized MC leaves them unaltered.

However, the so-called multi-line comment frames are exception. MC uses these for its custom fields and when MC updates tags it rewrites the whole comment frame block with new data from the library.

Tag&Rename uses a custom comment tag for the Catalog Number and unfortunately MC cannot preserve this. For the other mentioned tags T&R uses standard dedicated ID3v2.3 fields and MC does not alter them.

Also e.g. iTunes and Musicmatch use some comment frames that MC erases automatically on a tag update.

It would be better if MC could only add its own comments instead of replacing the comment block.

[trott]

have there been any updates on this? The soundcheck tag also gets corrupted by mc's audio analysis. As a workaround I disabled writing audio analysis fields to the tags. This however does not seem like a clean way to fix it...Surely existing id3 comment fields can be preserved?