# \[X\] Can't copy some unusual TRACK tags from MP3 / FLAC to WMA

**URL:** https://community.mp3tag.de/t/x-cant-copy-some-unusual-track-tags-from-mp3-flac-to-wma/17714
**Category:** No Bugs
**Created:** [March 4, 2016, 10:40am UTC](https://community.mp3tag.de/t/x-cant-copy-some-unusual-track-tags-from-mp3-flac-to-wma/17714 "2016-03-04T10:40:10Z")
**Posts on this page:** 9
**Page:** 1

<div class="post-metadata">

### Author: ![Zerow](https://community.mp3tag.de/user_avatar/community.mp3tag.de/zerow/32/11379_2.png) [@Zerow](https://community.mp3tag.de/u/Zerow)
#### Post date: [March 4, 2016, 10:40am UTC](https://community.mp3tag.de/t/x-cant-copy-some-unusual-track-tags-from-mp3-flac-to-wma/17714/1 "2016-03-04T10:40:10Z")

</div>

Till recently, I was using only MP3's and FLACs; with tags in ID3v2.3 UTF-16. And I was using tag fields not in a "standard" way, with a bunch of signs different than just letters and numbers, but had not problems with them whatsoever

But now it seems I have found a bug

If the value in the TRACK tag field starts with a dot sign `.` I simply cannot copy such value to a WMA format. But if that dot was behind I number, then there would be no problem. Also if I have a letter or letters in the TRACK field, such value cannot be copy. But if letters are following a number, then there is no such problem

So the bug is: it can be copied, but to MP3 and FLAC; but such an attempt on a WMA file will spit out an error saying, that it cannot be opened for writing

[I haven't tested all the fields with all the signs that I'm using- so maybe there are more cases like that?]

---

<div class="post-metadata">

### Author: ![poster](https://community.mp3tag.de/user_avatar/community.mp3tag.de/poster/32/4881_2.png) [@poster](https://community.mp3tag.de/u/poster)
#### Post date: [March 4, 2016, 11:13am UTC](https://community.mp3tag.de/t/x-cant-copy-some-unusual-track-tags-from-mp3-flac-to-wma/17714/2 "2016-03-04T11:13:55Z")

</div>

Why should it be a bug if you try to use tag-fields against their official definition:

"TRCK  
The 'Track number/Position in set' frame is a numeric string containing the order number of the audio-file on its original recording. This may be extended with a "/" character and a numeric string containing the total numer of tracks/elements on the original recording. E.g. "4/9"."

There is nothing mentioned of dots and letters.

---

<div class="post-metadata">

### Author: ![Zerow](https://community.mp3tag.de/user_avatar/community.mp3tag.de/zerow/32/11379_2.png) [@Zerow](https://community.mp3tag.de/u/Zerow)
#### Post date: [March 4, 2016, 12:21pm UTC](https://community.mp3tag.de/t/x-cant-copy-some-unusual-track-tags-from-mp3-flac-to-wma/17714/3 "2016-03-04T12:21:03Z")

</div>

So why does MP3 and FLAC have no issues with it and WMA does? Why are those two treated better [at least in MP3tag], in a more universal way?

Why should I limit myself to what a value should be, in terms of meaning / characters? With that logic I should not put in the TITLE tag all those non-letter signs used on this album tracklist [https://en.wikipedia.org/wiki/Reanimation#Track\_listing](https://en.wikipedia.org/wiki/Reanimation#Track_listing). And by extending that logic, I should only put one predefined genre in GENRE tag, and not my own [sometimes multiple] descriptions [number codes meaning various activities like running or falling asleep]. WHY?

---

<div class="post-metadata">

### Author: ![ryerman](https://community.mp3tag.de/user_avatar/community.mp3tag.de/ryerman/32/5285_2.png) [@ryerman](https://community.mp3tag.de/u/ryerman)
#### Post date: [March 4, 2016, 1:25pm UTC](https://community.mp3tag.de/t/x-cant-copy-some-unusual-track-tags-from-mp3-flac-to-wma/17714/4 "2016-03-04T13:25:20Z")

</div>

> [@zerow](#):
>
> So the bug is: it can be copied, but to MP3 and FLAC; but such an attempt on a WMA file will spit out an error saying, that it cannot be opened for writing

This is not a bug, but the result of an Mp3tag feature.

WMA files use ASF (Advanced Systems Format) tags.  
see here:  
[https://msdn.microsoft.com/en-us/library/wi...v=vs.85%29.aspx](https://msdn.microsoft.com/en-us/library/windows/desktop/dd757536%28v=vs.85%29.aspx)  
[https://msdn.microsoft.com/en-us/library/wi...v=vs.85%29.aspx](https://msdn.microsoft.com/en-us/library/windows/desktop/dd743066%28v=vs.85%29.aspx)

My understanding is this:

ASF tags support both Track and TrackNumber.  
Track is 0-based and included for legacy reasons. (ie back-wards support)  
TrackNumber is 1-based.  
Mp3tag writes both.

You may ask, "How does Mp3tag write those tags?"

Only the developer knows for sure, but my observations suggest this:  
Whatever number is entered by the user becomes TrackNumber.  
Track is calculated by substracting 1 from the integer portion (the part before the decimal) of TrackNumber.

This means that you may only enter any decimal number ~~greater than~~ greater than or equal to 1. [EDIT]  
Anything else will cause the warning you have seen.  
This allows the feature of writing both Track and TrackNumber.

For example:  
If you enter 1, then TrackNumber = 1 and Track = 0  
If you enter 1.12345, then TrackNumber = 1.12345 and Track = 0  
If you enter 1.9, then TrackNumber = 1.9 and Track = 0  
If you enter +1.9, then TrackNumber = +1.9 and Track = 0  
If you enter +300.9, then TrackNumber = +300.9 and Track = 299

---

<div class="post-metadata">

### Author: ![Zerow](https://community.mp3tag.de/user_avatar/community.mp3tag.de/zerow/32/11379_2.png) [@Zerow](https://community.mp3tag.de/u/Zerow)
#### Post date: [March 4, 2016, 7:52pm UTC](https://community.mp3tag.de/t/x-cant-copy-some-unusual-track-tags-from-mp3-flac-to-wma/17714/5 "2016-03-04T19:52:50Z")

</div>

> [@ryerman](#):
>
> This is not a bug, but the result of an Mp3tag feature.
> 
> WMA files use ASF (Advanced Systems Format) tags.  
> [...]  
> You may ask, "How does Mp3tag write those tags?"
> 
> Only the developer knows for sure  
> [...]

You mean developer of Mp3tag: [Florian](https://forums.mp3tag.de/index.php?showuser=203%20)?

Or developers of WMA container format?

I took a shoot at another format [because I'm looking for another lossless format to use aside from FLAC]: WavPack

WV files seem to behave the same as MP3s and FLACs. There is no problem with unusual data that I use in the TRACK field. And I've also tested to same extend other fields in that format, with different signs

But the TRACK field WVA bug question remains: should or shouldn't it behave the same as MP3 / FLAC / WV in Mp3tag?

---

<div class="post-metadata">

### Author: ![ryerman](https://community.mp3tag.de/user_avatar/community.mp3tag.de/ryerman/32/5285_2.png) [@ryerman](https://community.mp3tag.de/u/ryerman)
#### Post date: [March 6, 2016, 2:43pm UTC](https://community.mp3tag.de/t/x-cant-copy-some-unusual-track-tags-from-mp3-flac-to-wma/17714/6 "2016-03-06T14:43:58Z")

</div>

> [@zerow](#):
>
> But the TRACK field WVA bug question remains: should or shouldn't it behave the same as MP3 / FLAC / WV in Mp3tag?

This is not a bug. This is merely behaviour you don't like.  
Mp3tag should continue to maintain back-wards compatibility by writing both TRACK and TRACKNUMBER for WMA files.

---

<div class="post-metadata">

### Author: ![DetlevD](https://community.mp3tag.de/user_avatar/community.mp3tag.de/detlevd/32/123_2.png) [@DetlevD](https://community.mp3tag.de/u/DetlevD)
#### Post date: [March 6, 2016, 3:55pm UTC](https://community.mp3tag.de/t/x-cant-copy-some-unusual-track-tags-from-mp3-flac-to-wma/17714/7 "2016-03-06T15:55:44Z")

</div>

> [@zerow](#):
>
> ... I was using tag fields not in a "standard" way, with a bunch of signs different than just letters and numbers ... If the value in the TRACK tag field starts with a dot sign. I simply cannot copy such value to a WMA format. But if that dot was behind I number, then there would be no problem. Also if I have a letter or letters in the TRACK field, such value cannot be copy. But if letters are following a number, then there is no such problem. ...

Presumably Mp3tag does nothing else than the function $num() to verify and to get clean values for the tracknumber from user input.  
At last the target filetype decides which datatype can be accepted.  
Note: a dot character is not a number.

The Windows Media Format 11 SDK defines ...  
WM/Track g\_wszWMTrack WMT\_TYPE\_STRING  
WM/TrackNumber g\_wszWMTrackNumber WMT\_TYPE\_STRING  
... and therefore it seems to be allowed, to store non numerical values into a WMA tag.

DD.20160306.1807.CET

---

<div class="post-metadata">

### Author: ![Zerow](https://community.mp3tag.de/user_avatar/community.mp3tag.de/zerow/32/11379_2.png) [@Zerow](https://community.mp3tag.de/u/Zerow)
#### Post date: [March 9, 2016, 6:24pm UTC](https://community.mp3tag.de/t/x-cant-copy-some-unusual-track-tags-from-mp3-flac-to-wma/17714/8 "2016-03-09T18:24:04Z")

</div>

> [@DetlevD](#):
>
> Presumably Mp3tag does nothing else than the function $num() to verify and to get clean values for the tracknumber from user input  
> [...]

Does this mean some other tag software will also have the same "problem" with WMA?

I'm not planning to switch, WavPacks in Mp3tag seem to work the way I need; I'm just curious

---

<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: [December 28, 2018, 2:37pm UTC](https://community.mp3tag.de/t/x-cant-copy-some-unusual-track-tags-from-mp3-flac-to-wma/17714/10 "2018-12-28T14:37:49Z")

</div>

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