# Silent data loss when saving recurring WWW/MP3 or certain/WMA tags
**URL:** https://community.mp3tag.de/t/silent-data-loss-when-saving-recurring-www-mp3-or-certain-wma-tags/70206
**Category:** Fixed Bugs
**Tags:** bug-fixed
**Created:** [November 21, 2025, 10:21am UTC](https://community.mp3tag.de/t/silent-data-loss-when-saving-recurring-www-mp3-or-certain-wma-tags/70206 "2025-11-21T10:21:10Z")
**Posts on this page:** 10
**Page:** 1
### Author:  [@kanda](https://community.mp3tag.de/u/kanda)
#### Post date: [November 21, 2025, 10:21am UTC](https://community.mp3tag.de/t/silent-data-loss-when-saving-recurring-www-mp3-or-certain-wma-tags/70206/1 "2025-11-21T10:21:10Z")
If a user enters multiple WWW tags in the Extended Tags dialog:
and then clicks _OK_, the dialog closes without indicating any error.
However, only the last WWW tag is saved.
All other entries are silently discarded, without giving the user any chance to notice that their data has been lost. After saving the tags become:
This occurs for both _MP3_ and _WMA_ files.
It also occurs for any _custom WMA_ tag, regardless of its name.
It also occurs for any _built-in WMA_ tag (WMA attribute) that _does not support multiple values_.
We were told that keeping only one instance of _some_ tags is by design ([“you can only one WWW field to an ID3v2 tag with an empty description”, “not all _/multivalued WMA attributes/_ are supported by Mp3tag”](https://community.mp3tag.de/t/cant-add-more-than-one-www-tag-info-wma-file-is-it-correct/70147/8)).
This bug report is **not** about the validity of the design decision,
but about the fact that the software discards user-entered data _without informing the user_.
mp3tag is concurrent development: v3.32c, Nov 19 2025 12:36:00 (64-bit)
This is a followup to the [[Can’t add more than one WWW tag into WMA file](https://community.mp3tag.de/t/cant-add-more-than-one-www-tag-info-wma-file-is-it-correct/70147)]
---
### Author:  [@ohrenkino](https://community.mp3tag.de/u/ohrenkino)
#### Post date: [November 21, 2025, 2:23pm UTC](https://community.mp3tag.de/t/silent-data-loss-when-saving-recurring-www-mp3-or-certain-wma-tags/70206/2 "2025-11-21T14:23:34Z")
> [@kanda](#):
>
> but about the fact that the software discards user-entered data _without informing the user_.
I am not sure what should be done instead.
A warning?
Just an example: if you choose to write ID3V2.3 and ID3V1 tags then data from ALBUMARTIST and the cover will certainly no be written to the V1 tags. Also, the data in GENRE will we either transcoded to a number or if there is no equivalent, saved as type "Other".
In normal operations this would mean for me that I would switch off this warning immediately as I would get it for every file.
If would become even more complex if more than just one type of files and more than one type of tags should be written.
Of if some fields refer to a standard item in some tags and user-defined ones in other tags.
So even though I agree that user data should be sacred, I have no idea how to cope with such varying cases and still get a usable program.
Just my thoughts.
---
### Author:  [@kanda](https://community.mp3tag.de/u/kanda)
#### Post date: [November 21, 2025, 2:59pm UTC](https://community.mp3tag.de/t/silent-data-loss-when-saving-recurring-www-mp3-or-certain-wma-tags/70206/3 "2025-11-21T14:59:59Z")
> [@ohrenkino](#):
>
> I am not sure what should be done instead
There may be various solutions.
I do not think Florian needs my advice in that.
---
### Author:  [@ohrenkino](https://community.mp3tag.de/u/ohrenkino)
#### Post date: [November 21, 2025, 3:21pm UTC](https://community.mp3tag.de/t/silent-data-loss-when-saving-recurring-www-mp3-or-certain-wma-tags/70206/4 "2025-11-21T15:21:45Z")
> [@kanda](#):
>
> There may be various solutions.
Oh. So would you share your ideas with us? It would make it easier to follow.
Right now, I see nothing but obstacles that would render the tagging process virtually unusable when checks are carried out during input, after setting different options for reading/writing/deleting and if different file types and different tag types as part of the selection.
The correction of malformed tags would also take ages.
So where and how do you see a way out?
---
### Author:  [@kanda](https://community.mp3tag.de/u/kanda)
#### Post date: [November 21, 2025, 7:38pm UTC](https://community.mp3tag.de/t/silent-data-loss-when-saving-recurring-www-mp3-or-certain-wma-tags/70206/5 "2025-11-21T19:38:13Z")
> [@ohrenkino](#):
>
> Oh. So would you share your ideas with us? It would make it easier to follow.
> Right now, I see nothing but obstacles that would render the tagging process virtually unusable when checks are carried out during input, after setting different options for reading/writing/deleting and if different file types and different tag types as part of the selection.
> The correction of malformed tags would also take ages.
> So where and how do you see a way out?
What is my profit for this work? Do you affect development decisions?
---
### Author:  [@ohrenkino](https://community.mp3tag.de/u/ohrenkino)
#### Post date: [November 21, 2025, 7:50pm UTC](https://community.mp3tag.de/t/silent-data-loss-when-saving-recurring-www-mp3-or-certain-wma-tags/70206/6 "2025-11-21T19:50:01Z")
> [@kanda](#):
>
> What is my profit for this work?
You might get a function that you like better.
> [@kanda](#):
>
> Do you affect development decisions?
I would assume that good reasoning and well-thought through arguments affect development decsions.
---
### Author:  [@kanda](https://community.mp3tag.de/u/kanda)
#### Post date: [November 21, 2025, 8:23pm UTC](https://community.mp3tag.de/t/silent-data-loss-when-saving-recurring-www-mp3-or-certain-wma-tags/70206/7 "2025-11-21T20:23:12Z")
I think Florian does not need my advice on _how_ to achieve the goal.
And I have nothing to add to _why_.
---
### Author:  [@Florian](https://community.mp3tag.de/u/Florian)
#### Post date: [November 21, 2025, 8:34pm UTC](https://community.mp3tag.de/t/silent-data-loss-when-saving-recurring-www-mp3-or-certain-wma-tags/70206/8 "2025-11-21T20:34:56Z")
I'm glad that @ohrenkino and others are also answering posts and asking questions. If you don't want to answer, then just don't.
I think the whole reason for this community here is that people can think and collaborate together (otherwise there would be no point for this place). This implies, that some topics are discussed entirely without me, or that I might jump in later if I have a better understanding for myself, or if the discussion reached a point where it's necessary.
* * *
I think this point is now reached, and I'll think about possible solutions to not loose data when entering specific fields or when resaving files with those specific fields.
Because this bug report covers a broad range of possible implications, I don't have an easy answer (which I might have had, if this was only about supporting multiple WXXX frames).
---
### Author:  [@Florian](https://community.mp3tag.de/u/Florian)
#### Post date: [November 28, 2025, 9:07pm UTC](https://community.mp3tag.de/t/silent-data-loss-when-saving-recurring-www-mp3-or-certain-wma-tags/70206/9 "2025-11-28T21:07:43Z")
I've just released [Mp3tag v3.32d](https://community.mp3tag.de/t/455) with changes on how Mp3tag writes ID3v2 and WMA tags.
When writing ID3v2 tags, Mp3tag now attempts to preserve the original ID3v2 frames if they are not modified by user input. This means that multiple `WXXX` frames, even those with identical descriptions, are now simply carried over during rewrites.
In addition, it is now possible to add multiple `WXXX` frames, including those with the same description, via Mp3tag. This does not conform to the ID3v2 standard, but I believe it is a practical tradeoff that reflects the current reality of ID3v2 tagging.
Because ASF/WMA tagging is very strict, I decided to store multiple values for fields that do not support them as `Value 1; Value 2` when writing.
I hope this addresses all issues raised in this topic. Please also note that these changes required significant modifications to the code that handles ID3v2 writing, so please use with caution.
---
### Author:  [@system](https://community.mp3tag.de/u/system)
#### Post date: [December 28, 2025, 9:08pm UTC](https://community.mp3tag.de/t/silent-data-loss-when-saving-recurring-www-mp3-or-certain-wma-tags/70206/10 "2025-12-28T21:08:11Z")
This topic was automatically closed 30 days after the last reply. New replies are no longer allowed.