# MP3 Diags Hopeful Fix

**URL:** https://community.mp3tag.de/t/mp3-diags-hopeful-fix/65023
**Category:** Support
**Created:** [June 12, 2024, 11:01am UTC](https://community.mp3tag.de/t/mp3-diags-hopeful-fix/65023 "2024-06-12T11:01:48Z")
**Posts on this page:** 1
**Showing post:** 2

<div class="post-metadata">

### Author: ![ohrenkino](https://community.mp3tag.de/user_avatar/community.mp3tag.de/ohrenkino/32/4843_2.png) [@ohrenkino](https://community.mp3tag.de/u/ohrenkino)
#### Post date: [June 12, 2024, 11:18am UTC](https://community.mp3tag.de/t/mp3-diags-hopeful-fix/65023/2 "2024-06-12T11:18:39Z")

</div>

MP3diags likes ID3vx tags but not APE tags. (Yes, this is a program that has problems with these tags). So get rid of the APE tags first, then run MP3diags again. The number of "Unsupportd ID3V2tag" messages should be lower.

Two ID3v1 tags looks a lot like a good cause for the problems that you have with your player.  
And files with unknown or broken streams should be repaired as otherwise pointers inside the files may point to the nirwana.  
Besides: the request of an integrity check was the first reply in your first thread:

> [@Boss Elite 550 Incorrectly reading Tags](https://community.mp3tag.de/t/boss-elite-550-incorrectly-reading-tags/65001/2):
>
> Have you checked if there are APE tags? I would check the files for integrity first:

so we could have come closer to the root cause 22 replies earlier.

---

_[View the full topic](https://community.mp3tag.de/t/mp3-diags-hopeful-fix/65023)._