I have a 32.56 MB, 17min 46secs mix that has been encoded (not be me) with LAME 3.92 to attain a CBR 256kbps file.
Foobar 0.8.3 reports the file:lame_version = LAME3.92
lame_profile =
lame_profile_index = 0
enc_delay = 576
enc_padding = 2112
mp3_accurate_length = yes
bitrate = 256
codec = MP3
channels = 2
samplerate = 44100
mp3_stereo_mode = stereo
--------------------
47049600 samples @ 44100Hz
(rounded samples : 47049408)
When I load this file into WinMP3Packer the information column shows the bitrate as 96kbps. This is clearly incorrect.
When I run this file through mp3packer using only the -i switch it outputs the following:INFO:
MPEG1 layer 3
40844 frames
44100 Hz
38.281250 frames per second
1066.945306 seconds
34144384 bytes in file (256.016002 kbps)
34142249 bytes in MP3 frames (255.999994 kbps) = current bitrate
261209171 bits of payload data (244.819645 kbps)
32669016 bytes of payload data (244.953632 kbps)
142957 bits wasted from partially-full bytes (0.133987 kbps)
34139400 bytes of MP3 data (255.978632 kbps) = minimum bitrate possible
2849 bytes of padding (0.021362 kbps)
2135 bytes outside MP3 frames (0.016008 kbps)
0 sync errors
Bitrate distribution:
256: 3335,37509
Largest frame uses 9740 bits = 1218 bytes = 372.859375 kbps
Smallest bitrate for CBR is 256
Thus, as mp3packer displays the correct bitrate I'm thinking this is a WinMP3Packer issue (although tbh I'm not sure why this would the case since I thought WinMP3Packer would simply display whatever mp3packer reported back).
Thought you might wanna know psyllium.
BTW if I edit the id3 tags in foobar (0.8.3) then WinMP3Packer reports the correct bitrate; it's like the updating of the metadata now allows the correct bitrate to be interpreted correctly.
And WinMP3Packer has no problem in packing the file to make a VBR 250kbps 31.85mb file