# Semicolon in Disc and Track
**URL:** https://discourse.beets.io/t/semicolon-in-disc-and-track/2037
**Category:** Help
**Created:** [February 25, 2022, 1:13pm UTC](https://discourse.beets.io/t/semicolon-in-disc-and-track/2037 "2022-02-25T13:13:58Z")
**Posts on this page:** 6
**Page:** 1
### Author:  [@47West63rd](https://discourse.beets.io/u/47West63rd)
#### Post date: [February 25, 2022, 1:13pm UTC](https://discourse.beets.io/t/semicolon-in-disc-and-track/2037/1 "2022-02-25T13:13:58Z")
In the example below my original tags are on the left and beets version on the right. Can anyone tell me what I am doing wrong or why the semicolons are being placed in the Disc and Track values?
Thanks!
Just noticed its in the year too…and particular version year not the original release year
---
### Author:  [@adrian](https://discourse.beets.io/u/adrian)
#### Post date: [February 25, 2022, 1:53pm UTC](https://discourse.beets.io/t/semicolon-in-disc-and-track/2037/2 "2022-02-25T13:53:58Z")
Hi! This is likely a quirk of the tool you’re using to look at the tags, not a literal semicolon. This issue has some background:
>
>
> I don't know if this comes from beets or if it's me configuring ncmpcpp poorly.
> …I got this line in .ncmpcpp/config :
> song\_columns\_list\_format = "(5)\[red\]{n}(5f)\[green\]{l} (25)\[cyan\]{a} (40)\[\]{t|f} (25)\[red\]{b}"
> This is the default way to display the songs in the column format in ncmpcpp except that I added the track number: (5)\[red\]{n}
> The issue is that tracks are displayed that way :
> !\[track\](https://f.cloud.github.com/assets/1104190/871594/4f367d4e-f84f-11e2-9f86-0efad2f1c4bd.PNG)
> If I go into the ncmpcpp tag editor :
> !\[tags\](https://f.cloud.github.com/assets/1104190/871601/85cfa13c-f84f-11e2-97ec-1d129b90fb9d.PNG)
> Of course all those tracks were imported with beets,
> it seems like a strange format. Is that a bug from beets mistagging the tracks or a ncmcpp rendering issue ?
---
### Author:  [@47West63rd](https://discourse.beets.io/u/47West63rd)
#### Post date: [February 25, 2022, 2:07pm UTC](https://discourse.beets.io/t/semicolon-in-disc-and-track/2037/3 "2022-02-25T14:07:02Z")
Thanks for the quick reply. I’m really digging beets so far.
If I don’t right click and view properties in windows…just hover over the track I still see 1; 1/9. Where before it would be just 1/9. Doesn’t the additional “1;” suggest there is more/different data there?
---
### Author:  [@adrian](https://discourse.beets.io/u/adrian)
#### Post date: [February 25, 2022, 2:29pm UTC](https://discourse.beets.io/t/semicolon-in-disc-and-track/2037/4 "2022-02-25T14:29:36Z")
Yes! Just not a literal semicolon. The Windows viewer seems to be interpreting the existence of two different relevant tags as needing _both_ to be shown. As the aforelinked thread mentions, MediaFile’s “read any, write all” approach to compatibility occasionally leads to this kind of display in tools that use a “read all” approach.
---
### Author:  [@47West63rd](https://discourse.beets.io/u/47West63rd)
#### Post date: [February 25, 2022, 2:41pm UTC](https://discourse.beets.io/t/semicolon-in-disc-and-track/2037/5 "2022-02-25T14:41:23Z")
I’ve been reading through that and trying to wrap my head around it. Do you understand to be like this…paraphrasing of course:
In my original collection there was just one of either “track” or “tracknumber” present so windows just gave me what was there. Now that I have two/both of them and depending on the the method used to view it knows both exist and just displays both under the same “label” for lack of a better term.
Would you say, nothing to really worry about I my end, I’ve not configured anything wrong?
The reason I ask is I have over 9K albums and 100K tracks so being very careful and testing batches of different kinds of albums/files before I turn beets loose on my 20+ years of CD rips and digital purchases.
---
### Author:  [@adrian](https://discourse.beets.io/u/adrian)
#### Post date: [February 25, 2022, 2:57pm UTC](https://discourse.beets.io/t/semicolon-in-disc-and-track/2037/6 "2022-02-25T14:57:00Z")
Yes and yes! (That is, I wouldn’t consider this anything to worry about.)