# Mappings of vorbisComments DATE, TRACKNUMBER

**URL:** https://community.mp3tag.de/t/mappings-of-vorbiscomments-date-tracknumber/58612
**Category:** Mac
**Created:** [September 28, 2022, 6:21pm UTC](https://community.mp3tag.de/t/mappings-of-vorbiscomments-date-tracknumber/58612 "2022-09-28T18:21:58Z")
**Posts on this page:** 5
**Page:** 1

<div class="post-metadata">

### Author: ![nicolas](https://community.mp3tag.de/letter_avatar_proxy/v4/letter/n/67e7ee/32.png) [@nicolas](https://community.mp3tag.de/u/nicolas)
#### Post date: [September 28, 2022, 6:21pm UTC](https://community.mp3tag.de/t/mappings-of-vorbiscomments-date-tracknumber/58612/1 "2022-09-28T18:21:58Z")

</div>

Hello and thank you for having a look at this,

I routinely batch transcode FLAC files to mp3, and most of the time the resulting files are missing the year or track number, or the year is different than the corresponding field in the source files.  
At first I thought there was an issue with the transcoding software, and got in touch with the developer.  
He eventually noticed that the issue is how MP3tag writes FLAC metadata, apparently in a non-standard way for both fields:

- year to _year_ instead of _date_
- track number to _track_ instead of _tracknumber_

I see in MP3tag preferences that if I check _use field mappings_, I can remap fields and that both year and date are remapped to the standard fields by default.  
I suppose checking that option will solve my issue, but this remains perplexing: why would mp3tag not follow standard practices by default ? Are there disadvantages ? Or have I disabled this myself unwittingly ?

Thanks !  
Nicolas

---

<div class="post-metadata">

### Author: ![Florian](https://community.mp3tag.de/user_avatar/community.mp3tag.de/florian/32/5759_2.png) [@Florian](https://community.mp3tag.de/u/Florian)
#### Post date: [September 28, 2022, 6:48pm UTC](https://community.mp3tag.de/t/mappings-of-vorbiscomments-date-tracknumber/58612/2 "2022-09-28T18:48:16Z")

</div>

I've just checked with a fresh install and the field mappings are enabled by default.

---

<div class="post-metadata">

### Author: ![nicolas](https://community.mp3tag.de/letter_avatar_proxy/v4/letter/n/67e7ee/32.png) [@nicolas](https://community.mp3tag.de/u/nicolas)
#### Post date: [September 28, 2022, 7:46pm UTC](https://community.mp3tag.de/t/mappings-of-vorbiscomments-date-tracknumber/58612/3 "2022-09-28T19:46:54Z")

</div>

Ok, thank you, this is unexpected but certainly possible.

---

<div class="post-metadata">

### Author: ![Florian](https://community.mp3tag.de/user_avatar/community.mp3tag.de/florian/32/5759_2.png) [@Florian](https://community.mp3tag.de/u/Florian)
#### Post date: [September 29, 2022, 7:51am UTC](https://community.mp3tag.de/t/mappings-of-vorbiscomments-date-tracknumber/58612/4 "2022-09-29T07:51:21Z")

</div>

More on this here at [Preferences → Tag Types → Use field mappings](https://community.mp3tag.de/t/preferences-and-configuration/56296#use-field-mappings-9):

> Mp3tag comes with a list of pre-defined default mappings for VorbisComments. It’s generally recommended to not remove those to preserve interoperability.

---

<div class="post-metadata">

### Author: ![system](https://community.mp3tag.de/uploads/default/original/2X/c/ce7035d426cb755a7916793326d23b465222a407.png) [@system](https://community.mp3tag.de/u/system)
#### Post date: [October 29, 2022, 7:51am UTC](https://community.mp3tag.de/t/mappings-of-vorbiscomments-date-tracknumber/58612/5 "2022-10-29T07:51:21Z")

</div>

This topic was automatically closed 30 days after the last reply. New replies are no longer allowed.
