Hi, Couldn't see this question asked in the archive so... Why is MAD so slow at detecting the correct length and average bitrate of a track? Surely just reading the Xing VBR tag gets all this info in just the first few hundred bytes of an mp3? It strikes me as quite odd that it takes so long to detect this. WinAmps in-mp3.dll seems to have none of these problems. Cheers.
Mark Powell - UNIX System Administrator - The University of Salford Academic Information Services, Clifford Whitworth Building, Salford University, Manchester, M5 4WT, UK. Tel: +44 161 295 5936 Fax: +44 161 295 5888 www.pgp.com for PGP key
On Saturday, March 31, 2001, 1:15:53 AM, you wrote:
MP> Hi, MP> Couldn't see this question asked in the archive so... MP> Why is MAD so slow at detecting the correct length and average bitrate MP> of a track? Surely just reading the Xing VBR tag gets all this info in MP> just the first few hundred bytes of an mp3? It strikes me as quite odd MP> that it takes so long to detect this. WinAmps in-mp3.dll seems to have MP> none of these problems.
I'd love to know too. I used LAME to encode about forty of my CDs using VBR. If I use MAD's "fast playtime calculation" then my playlist loads fairly quickly, but the playtimes are grossly miscalculated (23 minutes for a 5 minute track?!). If not, then I usually can go away and watch at least half an hour's worth of television before it's finished loading and calculating the track play times properly.
DRS
From: "Mark Powell" M.S.Powell@salford.ac.uk
Why is MAD so slow at detecting the correct length and average bitrate of a track?
Because it has no support for Xing/VBRI tags. As an MPEG audio decoder, these are really outside its remit. The Winamp plugin might be adapted to support them, though.
-- Mat.
On Sat, 31 Mar 2001, Mathew Hendry wrote:
From: "Mark Powell" M.S.Powell@salford.ac.uk
Why is MAD so slow at detecting the correct length and average bitrate of a track?
Because it has no support for Xing/VBRI tags. As an MPEG audio decoder, these are really outside its remit.
Really? I understand the strict definition, but isn't knowing the length of a track quite useful? Why go to the trouble of programming this "fast playing time" checkbox when you can just read a few hundreds bytes to get the same information completely accurately?
The Winamp plugin might be adapted to support them, though.
And so it should. It seems such an elementary oversight for an otherwise exemplary piece of software. I have a reasoanbly fast machine and sometimes go back to Nullsoft's plugin just to get rid of the ~30s that WinAmp stops responding for. Cheers.
Mark Powell - UNIX System Administrator - The University of Salford Academic Information Services, Clifford Whitworth Building, Salford University, Manchester, M5 4WT, UK. Tel: +44 161 295 5936 Fax: +44 161 295 5888 www.pgp.com for PGP key
The next release of the MAD plug-in for Winamp will most likely have support for reading Xing headers.
This has been on the TODO list for quite some time. It's not an oversight that this is currently missing -- I'm quite aware of the fact.
Cheers,
On Sat, 31 Mar 2001, Rob Leslie wrote:
The next release of the MAD plug-in for Winamp will most likely have support for reading Xing headers.
This has been on the TODO list for quite some time. It's not an oversight that this is currently missing -- I'm quite aware of the fact.
Nice one Rob. Keep up the good work. Cheers.
Mark Powell - UNIX System Administrator - The University of Salford Academic Information Services, Clifford Whitworth Building, Salford University, Manchester, M5 4WT, UK. Tel: +44 161 295 5936 Fax: +44 161 295 5888 www.pgp.com for PGP key