Author Topic: Bitrate display on FLAC radio streams--a fix?  (Read 1149 times)


  • Hero Member
  • *****
  • Posts: 1960
On several Icecast server ogg-wrapped FLAC streams for example Rondo Classic Klasu
( and Frequence3
( MusicBee shows the bitrate as "128k".

This is must be due to MusicBee pulling that info directly from the Icecast server bitrate header "icy-br", which incorrectly shows "128" as its value.  For instance, the first example's header log looks like this in the AIMP player:

HTTP/1.0 200 OK
Server: Icecast 2.4.2
Date: Sun, 27 May 2018 20:41:56 GMT
Content-Type: application/ogg
Cache-Control: no-cache
Expires: Mon, 26 Jul 1997 05:00:00 GMT
Pragma: no-cache
ice-audio-info: ice-samplerate=44100;ice-bitrate=128;ice-channels=2
icy-description:Classical music for modern listeners, 24/7
icy-genre:Classical music
icy-name:Rondo Classic Klasu-flac

However, AIMP correctly displays the actual FLAC bitrate in its running line:

Can MusicBee also be made to display the actual bitrate instead of using the often erroneous info from the "icy-br" server stream header?

Thanks for your consideration.
Last Edit: May 27, 2018, 10:01:38 PM by sveakul


  • Hero Member
  • *****
  • Posts: 1960
Another example of what I am asking for using an OPUS stream instead of FLAC,  and the XMPlay player instead of AIMP for the comparison:

MusicBee displays this OPUS stream ( as being "1024k" bitrate, which of course cannot be accurate:

This is because it trusts the value from the erroneous "icy-br" header value sent for reasons unknown by the server, shown here from the XMPlay player (which can display these headers):

However, the same player also is able to determine and display the REAL bitrate in its version of MB's "Track Information":

So I am hoping MusicBee can add the ability to sample and display the actual bitrate for such streams as opposed to relying on the header's value.
Last Edit: August 27, 2018, 04:04:49 AM by sveakul