In fact the files I happened to test with were VBR but without a VBR header, and they still show up correctly, so they must have been fully scanned at some point.Įr, I'd say only p.ain is correct. I have tested and confirmed it does show within 1 kbps of the rate shown by foobar2000. It is probably OK to assume it is correct (or at least, it is no less correct than what other tools would show you without reading the whole file). In Windows, a file properties window report of 257 kbps, not being one of the standard frame sizes, suggests a VBR tag was read. This works well enough for most files, except when a VBR file is missing the VBR header frame or when a file has been corrupted in some way. When it is absent or otherwise not being read for some reason, the file is assumed to be CBR and the tool instead assumes the first frame's bitrate is accurate, and the duration is then based on that and the file size, minus tags.
If this header is present, the file is assumed to be VBR. From this info, an estimated duration and bitrate is derived. Other tools just read the file's "VBR header" (if present) which is a silent first frame with some extra metadata crammed in it, including a total byte count and frame count. Some tools read the whole file upon load to see whether all the frames are the same bitrate, and to find out the actual duration and average bitrate. Those are either VBR or 256 kbps and there was a problem reading the details.Īndrew.lisowski.1 and p.ain are both correct.Īn MP3 file is CBR if all frames are the same bitrate, otherwise it is VBR. It looks like you've also submitted some other questionable mp3 releases: That release you submitted to should just say VBR. There is no such thing as a 257 kbps track. That doesn't mean that the whole tracks is 257 kbps. I'm pretty sure that's because, like most applications, when trying to figure out the details of a VBR mp3, it just looks at one point in the file and tells you what that is. For example, for my above cited release ,on a Windows machine, I would go to >Music>In War & Peace>01>Properties>Details. At the moment I cannot see any actual defined property container for a bit-rate when a variable encoder is used.Ī file bit rate is documented and directly visible in the file Properties itself, no need to display via an application. Please let me know which of the ID3 tags contains the bit-rate and I'll endeavour to get some more info. MediaMonkey, dBpoweramp, etc can report different averages. I can't say how various metadata readers return their results other than they can vary for same file. How would different software produce different results when looking at the mp3 file Properties data itself? The bit rate of the file (track) is recorded there. I would not bother adding the bitrates of variable bitrate tracks to notes either, different software can show different results.
0 kommentar(er)
