# !Bad ID3V2 on only one of a two disc album?

**URL:** https://community.mp3tag.de/t/bad-id3v2-on-only-one-of-a-two-disc-album/62935
**Category:** General Discussion
**Created:** [December 1, 2023, 12:40am UTC](https://community.mp3tag.de/t/bad-id3v2-on-only-one-of-a-two-disc-album/62935 "2023-12-01T00:40:00Z")
**Posts on this page:** 3
**Page:** 1

<div class="post-metadata">

### Author: ![OldJohn](https://community.mp3tag.de/letter_avatar_proxy/v4/letter/o/f4b2a3/32.png) [@OldJohn](https://community.mp3tag.de/u/OldJohn)
#### Post date: [December 1, 2023, 12:40am UTC](https://community.mp3tag.de/t/bad-id3v2-on-only-one-of-a-two-disc-album/62935/1 "2023-12-01T00:40:00Z")

</div>

First time MP3Tag user here. Seems very flaky. In processing many 2 CD albums MP3Tag will work on one CD but not the other, responding: !Bad ID3V2. Both CDs were downloaded to my PC the same way. Processing the discs in order, sometimes it is Disc 1 reported bad, sometimes Disc 2. On some CDs the first few music files will display properly but halfway through the remaining cuts are shown as bad. On rare occasions I can go back to a previously reported bad disc and have it process OK. I tried changing to the 64 bit version of MP3Tag but experience the same issues. Any ideas?  
OldJohn

---

<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 1, 2023, 2:10am UTC](https://community.mp3tag.de/t/bad-id3v2-on-only-one-of-a-two-disc-album/62935/2 "2023-12-01T02:10:03Z")

</div>

It looks like the software you’re using to process the CDs creates ID3v2 tags in a way other than what Mp3tag expects.

Can you check the relevant files for errors and let me know what software created/modified the files before Mp3tag reports the problem?

> [@How to check files for errors?](https://community.mp3tag.de/t/how-to-check-files-for-errors/44633):
>
> It’s required and often helps to reduce support cycles to check files for errors before filing a bug report. Symptoms of erroneous files are often missing or wrong bitrate or length audible blips or skips tags seem to be sticky and cannot be removed There are some really good tools to check the files for errors, namely MP3 Diags — identifies many different issues in MP3 files Website: [http://mp3diags.sourceforge.net](http://mp3diags.sourceforge.net) Download: [MP3 Diags - Getting MP3 Diags](http://mp3diags.sourceforge.net/010_getting_the_program.html#binWindows) If the font size in MP3 Diags is …

---

<div class="post-metadata">

### Author: ![OldJohn](https://community.mp3tag.de/letter_avatar_proxy/v4/letter/o/f4b2a3/32.png) [@OldJohn](https://community.mp3tag.de/u/OldJohn)
#### Post date: [December 1, 2023, 3:21am UTC](https://community.mp3tag.de/t/bad-id3v2-on-only-one-of-a-two-disc-album/62935/3 "2023-12-01T03:21:16Z")

</div>

Thanks for responding! I recently re-ripped my CDs using iTunes at a bit rate of 320kbps. They all play OK. I then ran them through MP3Gain and then edited all of the filenames to remove the leading cut numbers in the tune titles. About 2/3 of the music files are from CD; the other 1/3 were purchased from Amazon. Not sure whether it is just the iTunes coded files or not. Working through the "Compilations" folder first where the majority of the artist names are missing. I just went back to the folder containing the recoded music files **before** MP3Gain and file renaming and found things work the same there on a limited sample: Always disc 1 works; Always disc 2 caused the !Bad ID3V2 message.

I am working through 400+ folders of music with MP3Tag and keeping track of which folders work and which don't. I don't see any trends like early music being most problematic: Bob Seger works, Bob Dylan doesn't. I'll try MP3 Diags. Thanks! OldJohn
