MP3-Files corrupted after editing

Hello everyone,

I am new to MP3Tag and used it for the first time recently. I mainly added some album covers and fixed some missing tags. It all went very well and I was very happy with how my library looked afterwards.
Unfortunately though, I discovered an issue that occurred right after I was done editing: All of the modified files were kind of corrupted, i.e. the sound was distorted. I am absolutely sure that the issue stems from the editing as I tried to open the files with different music players (Windows Media Player, VLC) and on different systems (Windows 10 Laptop, Android Smartphone) to eliminate any possible error source. The the problem persists however.

Thats why I am addressing you guys now. Is this a known issue and/or is there a fix available? I undid the changes on some files to see if the files would get restored back to normal, but to no avail. As I edited almost 5 GB of files in one go it would be really unfortunate if I cant rescue the songs...

Does anyone know what to do?

1 Like

It's highly unlikely that Mp3tag corrupted your files. Get MP3 Diags and scan some of your files to see if any errors show up.

Anytime you modify files with unfamiliar software you should create backups of the files just in case there's a problem.

Dont know about that. I mean they werent corrupted before I used MP3Tag, which makes it hard for me to believe that it was caused by anything else. The remaining unedited files that are located in the same folder are still working perfectly fine too.

But yeah you are right, not creating backups was dumb.

Anyways, I ran the program and apparently there are errors (as far as I am able to understand what it says at least). Is there some kind of log-feature so I can show you?

You could also run mp3val (search machine will tell you where to get it) - this program shows files with problems and tries to repair them.

(Claiming that MP3tag corrupted files with no further evidence is rather bold, i'd say. Esp. if the rest of the files shows problems.)

You could post a screen shot. All of the errors have a corresponding fix. Again, make backups before you try the fixes.

Ok so apparently you take me suspecting MP3Tag to be the cause very seriously. I am not trying to badmouth the program in any way, in fact I was pleasantly surprised how well and easy the process of modifying the files went. Unfortunately though an issue occurred, and as the only thing that actually had anything to do with the files recently is MP3Tag, I am suspecting it to be the origin of the issue simply because it is the most obvious option. The rest of the files show no problems whatsoever btw.

I am not here the blame anyone or claim anything, I'd only like to find a fix :slight_smile:.

I tried mp3val and fixed the broken files, but it didnt help.

@stanman thanks for the heads up! Here's the screenshot.


You should have a look at all the files as they all have different peculiarities, e.g.
kimdracula has the errors:
aa - two mpeg streams
ah - different channel mode
ak - invalid mpeg frame
bc - frame count mismatch
kc - unknown stream

These are the serious errors. And that is a file from the same folder - so that is apparently no criterion.
I would seriously check the files for integrity and repair them with mp3val, mp3diags and foobar2000 before you do any further tagging.
MP3tag was here the messenger, not the origin.

These are the fixes for those errors

aa - two mpeg streams - 10 Remove multiple ID3 streams
ah - different channel mode - not sure about this one, experiment
ak - invalid mpeg frame - 5 Remove unsupported streams
bc - frame count mismatch - try 13 Repair VBR if that doesn't work 14 Rebuild VBR
kc - unknown stream - 3 Remove unknown streams

Select the files you want fix, do only one type at a time.
Click the hammer with the down arrow and RIGHT-click the fix you want to use, that will apply the fix to only selected files.

Also use Mp3tag to do a Tag Cut and then a Tag Paste to remove unsupported tag frames.
Make sure you do the Tag Paste and NOT Tag Copy because that will delete the data.

hmm that doesnt sound too good.

I tried to repair some of the files with m3val and mp3diags, but I have to admit I have no clue what I'm doing. I basically scanned the programs for 'repair'-options and applied them - no idea if I have done it correctly.
The same folder as before now looks like this in mp3diags (see screen). Apparently something changed, but I cant tell what exactly (the audio didnt change, it remains in the same state as before).
Also, how can I check the files for integrity and fix them with foobar 2000?

Thanks a lot for the help so far!


Those "errors" are OK. The ea error just means you don't have an album cover in the file.

an - you can ignore if you don't use normalization.

bh - can be ignored too unless it causes a problem.

Don't use Mp3val with MP3 Diags because they use different methods to repair VBR data.

MP3 Diags and Mp3tag should be the only programs you need.

Didnt help :frowning: . I applied mp3val and mp3diags for different folders now and neither of them changed anything in terms of restoring the original audio. Both programs fixed some errors though.

Thousands of users have used Mp3tag to tag millions of files without causing damage.
That is why it is hard to believe that Mp3tag has damaged your files.
But statistics prove nothing.

In order to prove that Mp3tag caused damage, the damage must be reproducible by others.
One way to do that is to provide a copy of an undamaged file; one that you believe will be damaged by Mp3tag, but before it is touched by Mp3tag.

If lots of other users are able to process it in any way you describe, without causing damage, then Mp3tag probably has nothing to do with the damage.
If other users also suffer file damage, Mp3tag might be the culprit.

If the audio part was in a mess before (with invalid pointers to the start of the audio, for instance) you will never get the "original" (=corrupt) audio back.
You may have another look at the audio part with mp3directcut that shows you some audio data.

So: first check the files that their audio part is OK, then start tagging.

Ohrenkino's explanation seems to be on point I think. I ll try to reproduce the issue though.

@ohrenkino will do.

Three weeks old topic, but heck ... removing tags could "trigger" distortion, if volume is too high and your playback chain does play back at digital full.

Try the following (on a copy of your files)

  • A ReplayGain-aware audio player (foobar2000, I'd suggest)
  • Scan ReplayGain and write tags
  • Play it again, Sam, and see what you get.

Replicated this issue successfully with same file repeatedly. The same file after changing tags through mp3tag get curropt. Did this many times to be sure of it. No avail.

1 Like

How do you know that the file is corrupt?
How do you know it is not corrupt before you use MP3tag?
In short: how do you test the state of a file?

3 posts were split to a new topic: Audible "blip" or "skip" after editing tags