# \[X\] Something with bitrates
**URL:** https://community.mp3tag.de/t/x-something-with-bitrates/2686
**Category:** No Bugs
**Created:** [December 27, 2005, 9:44pm UTC](https://community.mp3tag.de/t/x-something-with-bitrates/2686 "2005-12-27T21:44:29Z")
**Posts on this page:** 9
**Page:** 1
### Author:  [@awx](https://community.mp3tag.de/u/awx)
#### Post date: [December 27, 2005, 9:44pm UTC](https://community.mp3tag.de/t/x-something-with-bitrates/2686/1 "2005-12-27T21:44:29Z")
I've noticed strange thing in MP3TAG: after tagging i cant see correct bitrates. I'm using Soulseek and there i can see bitrates, when i write tags using MP3TAG, i see bitrates from 96 to 160 and wrong track length and no VBR. When i delete all tags, everything is normal, i can see 192 - 320 or VBR. With other tag editors everything's ok. At first I thought that this problem is caused by discogs.src or something, but after trying to write tag by myselft i got the same result - incorrect bitrates and track length. maybe its a bug?
---
### Author:  [@Florian](https://community.mp3tag.de/u/Florian)
#### Post date: [December 28, 2005, 8:52am UTC](https://community.mp3tag.de/t/x-something-with-bitrates/2686/2 "2005-12-28T08:52:52Z")
Are the track lengths and bitrates displayed correctly in Mp3tag or foobar2000/Winamp. I think using Soulseek as reference for correct bitrates is not very reliable (maybe it has problems with ID3v2 tags).
Best regards,
~ Florian
---
### Author:  [@awx](https://community.mp3tag.de/u/awx)
#### Post date: [December 28, 2005, 9:50am UTC](https://community.mp3tag.de/t/x-something-with-bitrates/2686/3 "2005-12-28T09:50:17Z")
in winamp or encspot everything's ok. maybe it is as you said, problem with ID3v2 in soulseek, but i mentioned that after taging with other software, there were no problems, so maybe it is a way how MP3TAG is taging files? it is not a big problem, but i found it strange, that everyone was tellin me, that i have only low bitrate files.
---
### Author:  [@Florian](https://community.mp3tag.de/u/Florian)
#### Post date: [December 28, 2005, 9:54am UTC](https://community.mp3tag.de/t/x-something-with-bitrates/2686/4 "2005-12-28T09:54:12Z")
ID3v2 tags written by Mp3tag are perfectly valid. Maybe Soulseek doesn't support ID3v2 tags written in Unicode and the option Always write ISO-8859-1 tags instead of UTF-16 at Options \> Tags \> Mpeg prevents this issue.
Otherwise just ask the Soulseek developers for a fixed version of their software.
Best regards,
~ Florian
---
### Author:  [@awx](https://community.mp3tag.de/u/awx)
#### Post date: [December 28, 2005, 2:57pm UTC](https://community.mp3tag.de/t/x-something-with-bitrates/2686/5 "2005-12-28T14:57:32Z")
Thank You for quick response 🙂 I've tried write ISO-8859-1 tags and everythings ok.
BTW you've created very handful program, i like it because of discogs sources 🙂 Thanks.
---
### Author:  [@MorieZ](https://community.mp3tag.de/u/MorieZ)
#### Post date: [January 6, 2006, 2:21pm UTC](https://community.mp3tag.de/t/x-something-with-bitrates/2686/6 "2006-01-06T14:21:45Z")
Lo there.
Im having the same prob in Soulseek. Should i completely delete the tag info and start writing it all over again? Following Florians tip, just saving doesnt seem to help:(
Thx for the help!
---
### Author:  [@Florian](https://community.mp3tag.de/u/Florian)
#### Post date: [January 6, 2006, 7:17pm UTC](https://community.mp3tag.de/t/x-something-with-bitrates/2686/7 "2006-01-06T19:17:04Z")
Just enable the option mentioned above and rewrite the tags.
Best regards,
~ Florian
---
### Author:  [@MorieZ](https://community.mp3tag.de/u/MorieZ)
#### Post date: [January 7, 2006, 11:59am UTC](https://community.mp3tag.de/t/x-something-with-bitrates/2686/8 "2006-01-07T11:59:14Z")
Thx Florian. Eventhough that didnt help me out, re-installing soulseek did. So for all you out there having this prob, try that! 
---
### Author:  [@Florian](https://community.mp3tag.de/u/Florian)
#### Post date: [December 28, 2018, 2:15pm UTC](https://community.mp3tag.de/t/x-something-with-bitrates/2686/9 "2018-12-28T14:15:24Z")
This topic was automatically closed 30 days after the last reply. New replies are no longer allowed.