Hi, and ... newbie alert!
What is the possible reason for different displayed bitrate in MP3TAG v2.66 and foobar2000 v1.3.7? Which one should I trust and what are my options to verify the actual bitrate of a track?
I tend to trust foobar2000, but this is subjective and not based on actual knowledge or expertise. It is weird how some tracks from some albums, supposedly CBR 320kbps (as shown in foobar2000) appear as 160kbps or even lower in MP3TAG. I have converted those albums myself with EAC, therefore it's not like the source of those mp3 files would be questionable.
PS. I have read up a little on the topic and it may be that different programs use different ways to evaluate and display bitrate. If that's the case here, how does MP3TAG process the data and can it be regarded as more adequate than foobar2000?
Rebuild MP3 Stream
Both operations did not have any effect regarding the incorrect information by Mp3tag.
I have applied the info tool MP3 Diags 1.2.01 ... which detected ...
a XING header containing the value 128000bps
a MPEG audio stream 320000bps CBR
I suspect the failure depends on the XING header.
The XING header may be introduced by the LAME encoder, ... probably by accident, ...
when applying any parameter, which causes the injection of the XING header for VBR or ABR with the incorrect bitrate.
Probably Mp3tag should detect and differentiate between ...
LAME VBR & ABR ==> "Xing"
LAME CBR ==> "Info"
Try out the recommendation by user "ryerman" ... "VBR fix".