# \[X\] Possible Bug with Bitrates
**URL:** https://community.mp3tag.de/t/x-possible-bug-with-bitrates/2405
**Category:** No Bugs
**Created:** [October 25, 2005, 5:40am UTC](https://community.mp3tag.de/t/x-possible-bug-with-bitrates/2405 "2005-10-25T05:40:00Z")
**Posts on this page:** 6
**Page:** 1
### Author:  [@goofydave](https://community.mp3tag.de/u/goofydave)
#### Post date: [October 25, 2005, 5:40am UTC](https://community.mp3tag.de/t/x-possible-bug-with-bitrates/2405/1 "2005-10-25T05:40:00Z")
I believe I have found a bug with bitrates.
I use the mIRC chat client with a script that uses a command $mp3($file).bitrate to display in text the bitrate of the particular mp3.
If I play an mp3 without having touched it with mp3tag 2.33 It displays the bitrate correctly.
Once i take the mp3 into mp3tag and change the ID3 tags and then play the mp3 in mIRC again I get an incorrect bitrate displayed even though Winamp tells me the mp3 is infact still 192kbps
I have also downloaded the dev builds 2.33a and 2.33b without success.
I went back to 2.32 and changed the ID3 with it and the problem does not occur
---
### Author:  [@Florian](https://community.mp3tag.de/u/Florian)
#### Post date: [October 25, 2005, 5:50am UTC](https://community.mp3tag.de/t/x-possible-bug-with-bitrates/2405/2 "2005-10-25T05:50:51Z")
Why do people post on the forum and contact me by email on the same issue - I don't get it...
Does Winamp or another program also show different bitrates after files being saved with Mp3tag?
If not, it's a bug with mIRC, otherwise please send me the original file and the modified one for analyzing. My guess is, that mIRC fails badly on Unicode tags - so you might want to enable Always write ISO-8859-1 tags instead of UTF-16 at Options \> Tags \> Mpeg.
~ Florian
---
### Author:  [@goofydave](https://community.mp3tag.de/u/goofydave)
#### Post date: [October 25, 2005, 6:05am UTC](https://community.mp3tag.de/t/x-possible-bug-with-bitrates/2405/3 "2005-10-25T06:05:23Z")
> [@](#):
>
> Why do people post on the forum and contact me by email on the same issue - I don't get it...
>
> Does Winamp or another program also show different bitrates after files being saved with Mp3tag?
>
> If not, it's a bug with mIRC, otherwise please send me the original file and the modified one for analyzing. My guess is, that mIRC fails badly on Unicode tags - so you might want to enable Always write ISO-8859-1 tags instead of UTF-16 at Options \> Tags \> Mpeg.
>
> ~ Florian
>
> \<{POST\_SNAPBACK}\>
I apologise for posting here and emailing, first time here and I didn't see there was an International Section until I posted an email to you.
Always write ISO-8859-1 tags instead of UTF-16 seems to have fixed the problem for me.
I have already sent the email reply with the files attached.
I understand the option was not there in 2.32
1 question if I may, why did this not happen in v2.32 but causes a problem in v2.33?
---
### Author:  [@Florian](https://community.mp3tag.de/u/Florian)
#### Post date: [October 25, 2005, 6:08am UTC](https://community.mp3tag.de/t/x-possible-bug-with-bitrates/2405/4 "2005-10-25T06:08:29Z")
I'll mark this as "No Bug".
> [@](#):
>
> 1 question if I may, why did this not happen in v2.32 but causes a problem in v2.33?
Mp3tag 2.33 writes tags in [Unicode](http://en.wikipedia.org/wiki/Unicode) format by default now (which is perfectly valid, recommended and specified by the ID3v2 standard).\<
Some programs have still problems with reading tags in Unicode format, so I've added the option to write tags as ISO-8859-1 instead.
Regards,
~ Florian
---
### Author:  [@goofydave](https://community.mp3tag.de/u/goofydave)
#### Post date: [October 25, 2005, 6:10am UTC](https://community.mp3tag.de/t/x-possible-bug-with-bitrates/2405/5 "2005-10-25T06:10:36Z")
Ok thanks for that.
I wasn't aware of that.
---
### Author:  [@Florian](https://community.mp3tag.de/u/Florian)
#### Post date: [December 28, 2018, 2:15pm UTC](https://community.mp3tag.de/t/x-possible-bug-with-bitrates/2405/6 "2018-12-28T14:15:13Z")
This topic was automatically closed 30 days after the last reply. New replies are no longer allowed.