# The disappearing discnumbers in Matroska files

**URL:** https://community.mp3tag.de/t/the-disappearing-discnumbers-in-matroska-files/69517
**Category:** Support
**Created:** [August 23, 2025, 8:42pm UTC](https://community.mp3tag.de/t/the-disappearing-discnumbers-in-matroska-files/69517 "2025-08-23T20:42:58Z")
**Posts on this page:** 1
**Showing post:** 2

<div class="post-metadata">

### Author: ![ohrenkino](https://community.mp3tag.de/user_avatar/community.mp3tag.de/ohrenkino/32/4843_2.png) [@ohrenkino](https://community.mp3tag.de/u/ohrenkino)
#### Post date: [August 24, 2025, 7:30am UTC](https://community.mp3tag.de/t/the-disappearing-discnumbers-in-matroska-files/69517/2 "2025-08-24T07:30:27Z")

</div>

I think that the described phenomenon is described in the thread that you linked:

> [@Matroska mapping](https://community.mp3tag.de/t/matroska-mapping/41736/6):
>
> When you enter DISCNUMBER for MKV with this new v3.28e, the field disappears from view in the tag panel, and the entered value pops up in the TVEPISODE field instead.  
> If you repeat the process (or if TVEPISODE already has a value), then the TVEPISODE field shows multiple occurrences separated by double backslashes (\), creating multiple T=50 PART\_NUMBER tags in the MKV file.  
> I think this is okay though.

So, you would have to add a field for TVEPISODE.

> [@confucius](#):
>
> Does this mean I need to use some mapping?

The same thread also says that it is not possible to map anything for Matroska.

---

_[View the full topic](https://community.mp3tag.de/t/the-disappearing-discnumbers-in-matroska-files/69517)._