Mp3tag V.2.33 released
Reply #20 – 2005-11-27 00:59:51
From the 128 kbps test thread:You made me to download the v.2.34 and upgrade my 2.33. Now, when I try to open the "Customize columns" dialog the program produces a runtime error ... This bug should be fixed with Mp3tag 2.34a . Thanks for reporting.However, unfortunately it can't display wma bitrates correctly. For example, the about 75 kbps Satie.wma file shows up as 176 kbps. I'm using the "Bitrate" attribute to get the bitrate and I have no idea what WMP10 uses to get the information. Best regards, ~ Florian[a href="index.php?act=findpost&pid=345405"][{POST_SNAPBACK}][/a] Thanks. I'll try the "a" build. The WMA "Bitrate" field shows something like the maximum bitrate used, but not exactly even that. Perhaps it is used for showing the needed bandwidth when streaming files. It seems that you should use either the CurrentBitrate or the OptimalBitrate field (these two values seem to be always identical inside wma audio files). Here is an example tag dump:Audio Codec: Windows Media Audio 9.1 Format: 128 kbps, 44 kHz, stereo 2-pass VBR Protected: No Seekable: Yes Trusted: No WMA Tag dump: Signature_Name: WMFSDKVersion: 10.00.00.3802 WMFSDKNeeded: 0.0.0.0000 Duration: 1901730000.0000000000000000 Bitrate: 141627.0000000000000000 Seekable: Yes Stridable: No Broadcast: No Is_Protected: No Is_Trusted: No HasAudio: Yes HasImage: No HasScript: No HasVideo: No CurrentBitrate: 129515.0000000000000000 OptimalBitrate: 129515.0000000000000000 HasAttachedImages: No Can_Skip_Backward: No Can_Skip_Forward: No FileSize: 3101421.0000000000000000 HasArbitraryDataStream: No HasFileTransferStream: No WM/ContainerFormat: 1.0000000000000000 IsVBR: Yes ASFLeakyBucketPairs: <unknown data> When I calculated the bitrate from the actual file size I got 130.47 kbps, but the WMA header is included in the value (no other tags) so I guess it is a close match.