# \[X\] Mp3tag corrupts every mp3 file after editing the tag

**URL:** https://community.mp3tag.de/t/x-mp3tag-corrupts-every-mp3-file-after-editing-the-tag/14751
**Category:** No Bugs
**Created:** [May 23, 2013, 6:14am UTC](https://community.mp3tag.de/t/x-mp3tag-corrupts-every-mp3-file-after-editing-the-tag/14751 "2013-05-23T06:14:17Z")
**Posts on this page:** 1
**Showing post:** 8

<div class="post-metadata">

### Author: ![David\_Diamond](https://community.mp3tag.de/letter_avatar_proxy/v4/letter/d/779978/32.png) [@David\_Diamond](https://community.mp3tag.de/u/David_Diamond)
#### Post date: [May 23, 2013, 10:58pm UTC](https://community.mp3tag.de/t/x-mp3tag-corrupts-every-mp3-file-after-editing-the-tag/14751/8 "2013-05-23T22:58:36Z")

</div>

**CONCLUSION** (Edit 5) : **(Jumped to top of the post)**

OK , So i tried my best to analyse this weird artifact and got conclusions and a solution . Well i really like to encounter bugs and debugging software is part of my daily challenge at my own development projects . So , my meanwhile conclusions are that firstly **Magix-Music-Maker has a glitch** (encountered bug by bug lol) that reads the ID3v2.3 as an audio stream (Not separating between audio data and the tag/non audio streams in the file at all . even proper non audio streams will get into the audio importer) .  
The MediaMonkey reads and plays the data very well , But unlike WMP it reads "Unknown Stream/Broken Streams" as "MPEG Audio Stream" unless it is explicit "ID3 Stream" at the end of the file or "ID3v2 Stream" at the beginning of the file . Any other streams include "MPEG Audio Stream" would be considered as "MPEG Audio Stream"s . While WMP and many other players playes data only from explicit "MPEG Audio Stream" . So that's why I can hear it only in some certain players .

Now about the Artifact itself . It is not exactly artifact but an "Unknown Stream" not ID3 tag and not LAME header or anything like that . But maybe it was in the past "LAME Header" that was corrupted by some one of the following : Or Mp3tag while tagging . Or MediaMonkey while rating/analysing , Or Windows Explorer while editing information . Now which one of them corrupted this LAME header i really have no idea . **You guys should check out and debug mp3tag and catch if it corrupts LAME Header's Stream because it maybe this**. If it is not mp3tag then its or Windows Explorer (Hard to believe that Microsoft actually released unstable software) Or its likely MediaMonkey player (Which is also a very famous and advanced editor that includes advanced tagging and editing . Why i think that MM is more likely is because this MediaPlayer has many bugs that i faced them my self also while looking at mp3 Diags i can see Unknown ASCII chars in MediaMonkey's ID3v2 tagging . I flushed the the tag in MP3 Diags and now the file plays fine . And the unknown (Broken Stream - corrupted LAME biased) is removed .

**So for those who got the same problem as i got . I can only suggest to use always mp3diags to remove any unknown/broken streams after tagging the file no matter what software you have used .**

Update :  
It seems that many files has more than 1 ID3v2x streams . Another surmise for this corruption may that mp3tag not deletes older ID3v2x streams before creating new streams or when detecting more than one ID3v2x streams . The ID3v1 stream at end should remain and reflect the basic data from the main ID3v2x stream .

* * *

> [@ohrenkino](#):
>
> I would not agree but say that it is very similar to this bug report:  
> [/t/14398/1](https://community.mp3tag.de/t/14398/1)  
> It also involves Magix Music Maker. So this seems to be incompatible.

But i can hear it in media players and game engines .  
Again the MMM is just a tool to check the file ! The file wasn't created in MMM or anyhing like that .  
So far i faced that Clauswitz 2 of Paradox Interactive reads and plays the artifact at running time . So it's a big problem . And MediaMonkey doing the same only if the artifact is large enough .

Here is anoter report regerding to the same noise artifact :  
[Weird Noise](https://community.mp3tag.de/t/13235/1)  
And the the bug you gave me regerding to MMM editing ... But again i do not use MMM to edit any of my files ! and actually MMM doesn't reports me anything about bad tag . Just a visible artifact in the wave monitor .

> [@chrisjj](#):
>
> Thanks David, but I think the requested file pair is needed.

The two files you requested are in the RAR file .

1. reconverted (Clean file)
2. mp3tags' (Two artifacted files after using mp3tag) .

Edit :  
Mp3Val (The latest one) says on the artifacted file :

> [@](#):
>
> Analyzing file "C:\Users\David\Desktop\Mp3tag Artifact - Hearable.mp3"...  
> WARNING: "C:\Users\David\Desktop\Mp3tag Artifact - Hearable.mp3" (offset 0xadb): MPEG stream error, resynchronized successfully  
> INFO: "C:\Users\David\Desktop\Mp3tag Artifact - Hearable.mp3": 4269 MPEG frames (MPEG 1 Layer III), +ID3v1+ID3v2, CBR  
> Done!

But the other file (Tagged again with mp3tag after reconverting) it says everthing alrighty .

Edit 2 :  
Accourding to [this article](http://stackoverflow.com/questions/5710598/is-the-leading-structure-in-mp3-file-a-real-frame) in StackOverFlow mp3 file **should not** have any headers , So what is that artifact/header in the first frame in each of my files after tagging with mp3tag ?

Edit 3 :  
So i took some time to analyse the files even deeper and i have some news after looking at them with Mp3 Diags v1.0 Unstable :  
The first artifacted file has an "unknown header" instead of "Lame header" that is missing :  
Here is the the beginning of the file (That was translated to an artifact later) :

> [@](#):
>
> begins with: "ha;pc..-.'n..=. ...\<.......kh..."

I have no idea what header is it supposed to be . The other thing is that i still don't understand what mp3tag is adding there always after tagging the file , I need some info about the way mp3tag tagging the file , Does it adds any new bytes in the beginning of the file ? Because the ID3 tags are located at the end of the mp3 file and not at the beginning AFAIK . SO what exactly mp3tag is searching there i am really trying to realise .

Edit 4 : I just have read the mp3 file structure at Wikipedia . The ID3v2X tag is located at the beginning of the file while ID3 tags are in the end of the file . So this artifact (at the first frame) could be an a side effect of the ID3v2 tagging . Now i am not sure why this overflows into the mp3 data .

---

_[View the full topic](https://community.mp3tag.de/t/x-mp3tag-corrupts-every-mp3-file-after-editing-the-tag/14751)._