# \[X\] Reported "DO NOT USE MP3tag! Potential Song-Load Errors!"

**URL:** https://community.mp3tag.de/t/x-reported-do-not-use-mp3tag-potential-song-load-errors/15617
**Category:** No Bugs
**Created:** [March 27, 2014, 12:58am UTC](https://community.mp3tag.de/t/x-reported-do-not-use-mp3tag-potential-song-load-errors/15617 "2014-03-27T00:58:52Z")
**Posts on this page:** 10
**Page:** 1

<div class="post-metadata">

### Author: ![chrisjj](https://community.mp3tag.de/letter_avatar_proxy/v4/letter/c/a698b9/32.png) [@chrisjj](https://community.mp3tag.de/u/chrisjj)
#### Post date: [March 27, 2014, 12:58am UTC](https://community.mp3tag.de/t/x-reported-do-not-use-mp3tag-potential-song-load-errors/15617/1 "2014-03-27T00:58:52Z")

</div>

Anyone know what this is about?

[http://forum.gibson.com/index.php?/topic/9...not-use-mp3tag/](http://forum.gibson.com/index.php?/topic/91889-do-not-use-mp3tag/)

---

<div class="post-metadata">

### Author: ![mjcm](https://community.mp3tag.de/letter_avatar_proxy/v4/letter/m/9d8465/32.png) [@mjcm](https://community.mp3tag.de/u/mjcm)
#### Post date: [March 27, 2014, 1:10am UTC](https://community.mp3tag.de/t/x-reported-do-not-use-mp3tag-potential-song-load-errors/15617/2 "2014-03-27T01:10:34Z")

</div>

I have read it and what amazes me is that no one will come to this forum and post a bug report, but just instead created a pinned topic on some other forum

If no one reports a bug (if there even is a bug ??) how can Florian fix it ??

---

<div class="post-metadata">

### Author: ![DetlevD](https://community.mp3tag.de/user_avatar/community.mp3tag.de/detlevd/32/123_2.png) [@DetlevD](https://community.mp3tag.de/u/DetlevD)
#### Post date: [March 27, 2014, 4:50am UTC](https://community.mp3tag.de/t/x-reported-do-not-use-mp3tag-potential-song-load-errors/15617/3 "2014-03-27T04:50:18Z")

</div>

> [@chrisjj](#):
>
> Anyone know what this is about? ...

In the today current view of this [forum.gibson.com](http://forum.gibson.com) webpage, each forum member from over there seems to speak about a different software product:  
"MP3Tag"  
"MP3tag"  
"MP3 tag"  
"mp3tag"

We can be glad that we use "Mp3tag"!  
Because we mostly ignore and live with the bugs.

DD.20140327.0650.CET

---

<div class="post-metadata">

### Author: ![chrishirst](https://community.mp3tag.de/letter_avatar_proxy/v4/letter/c/4af34b/32.png) [@chrishirst](https://community.mp3tag.de/u/chrishirst)
#### Post date: [March 27, 2014, 4:47pm UTC](https://community.mp3tag.de/t/x-reported-do-not-use-mp3tag-potential-song-load-errors/15617/4 "2014-03-27T16:47:49Z")

</div>

Did you happen to take note that the thread was started in September **2012** and the last post in the thread was a little over a year ago.

AND it only was regarding one particular player / device.

---

<div class="post-metadata">

### Author: ![chrisjj](https://community.mp3tag.de/letter_avatar_proxy/v4/letter/c/a698b9/32.png) [@chrisjj](https://community.mp3tag.de/u/chrisjj)
#### Post date: [March 27, 2014, 10:08pm UTC](https://community.mp3tag.de/t/x-reported-do-not-use-mp3tag-potential-song-load-errors/15617/5 "2014-03-27T22:08:46Z")

</div>

> [@Chris Hirst](#):
>
> Did you happen to take note that the thread was started in September **2012** and the last post in the thread was a little over a year ago.

If you're suggesting the bug was fixed since, I'd be interested to see the changelog.

> [@Chris Hirst](#):
>
> AND it only was regarding one particular player / device.

That would be significant if the report of corruption is false. 🙂

---

<div class="post-metadata">

### Author: ![chrishirst](https://community.mp3tag.de/letter_avatar_proxy/v4/letter/c/4af34b/32.png) [@chrishirst](https://community.mp3tag.de/u/chrishirst)
#### Post date: [March 28, 2014, 5:56pm UTC](https://community.mp3tag.de/t/x-reported-do-not-use-mp3tag-potential-song-load-errors/15617/6 "2014-03-28T17:56:30Z")

</div>

> [@chrisjj](#):
>
> If you're suggesting the bug was fixed since, I'd be interested to see the changelog.

Nope, what I'm saying is that a single report of an isolated instance does NOT qualify as a 'bug'

> [@chrisjj](#):
>
> That would be significant if the report of corruption is false. 🙂

Actually it is totally insignificant.

That 'bug' report has not been substantiated then, or since. If anything, it suggest that the problem was elsewhere.and and Mp3Tag was blamed through deductive reasoning rather than any actual 'testing'.

For it to be a true 'bug' the problem has to be demonstrable and repeatable by more than one user and if it is not repeatable it is NOT a 'bug'.

---

<div class="post-metadata">

### Author: ![chrisjj](https://community.mp3tag.de/letter_avatar_proxy/v4/letter/c/a698b9/32.png) [@chrisjj](https://community.mp3tag.de/u/chrisjj)
#### Post date: [March 28, 2014, 7:54pm UTC](https://community.mp3tag.de/t/x-reported-do-not-use-mp3tag-potential-song-load-errors/15617/7 "2014-03-28T19:54:25Z")

</div>

> [@Chris Hirst](#):
>
> AND it only was regarding one particular player / device.

> [@Chris Hirst](#):
>
> what I'm saying is that a single report of an isolated instance does NOT qualify as a 'bug'

"It causes an issue with us and a number of other media player apps."

---

<div class="post-metadata">

### Author: ![JJ\_Johnson](https://community.mp3tag.de/user_avatar/community.mp3tag.de/jj_johnson/32/67_2.png) [@JJ\_Johnson](https://community.mp3tag.de/u/JJ_Johnson)
#### Post date: [March 28, 2014, 9:00pm UTC](https://community.mp3tag.de/t/x-reported-do-not-use-mp3tag-potential-song-load-errors/15617/8 "2014-03-28T21:00:26Z")

</div>

> [@chrisjj](#):
>
> Anyone know what this is about?
> 
> [http://forum.gibson.com/index.php?/topic/9...not-use-mp3tag/](http://forum.gibson.com/index.php?/topic/91889-do-not-use-mp3tag/)

Apparently not. Apart from "malformed tags", which could mean a million things, that discussion gives no clues. Are they speaking about Mp3 files and ID3v2 tags, because not even THAT is indicated?

---

<div class="post-metadata">

### Author: ![chrishirst](https://community.mp3tag.de/letter_avatar_proxy/v4/letter/c/4af34b/32.png) [@chrishirst](https://community.mp3tag.de/u/chrishirst)
#### Post date: [March 28, 2014, 10:26pm UTC](https://community.mp3tag.de/t/x-reported-do-not-use-mp3tag-potential-song-load-errors/15617/9 "2014-03-28T22:26:45Z")

</div>

> [@chrisjj](#):
>
> "It causes an issue with us and a number of other media player apps."

Has anyone defined **what** media players,?

And of course 0 is "a number".

Until somebody defines what the problems are and/or documents the steps needed to reproduce the error conditions and in what media players the effects are seen, it cannot be termed a 'bug' or a fault in ANY perticular application, it is simply a glitch or a 'use case' issue, If only ONE person has had problems with MP3Tag and the media players that person uses, the issue is probably with HOW that person is doing something, but of course it must be the fault of the tool, rather than how it is being used. I've been using various versions of MP3Tag both pre and post 2.5.0 and played the tagged media on many different players and devices with no problems with loading or displaying tags that I have noted.

If this was a MP3Tag issue there would be more than 0 reports at these forums and more than ONE instance of a reported problem elsewhere in the past TWO years, and given that there have been no responses to that thread in over twelve months you can be reasonably confident that it is a non-issue.

---

<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 28, 2018, 2:34pm UTC](https://community.mp3tag.de/t/x-reported-do-not-use-mp3tag-potential-song-load-errors/15617/10 "2018-12-28T14:34:01Z")

</div>

This topic was automatically closed 30 days after the last reply. New replies are no longer allowed.
