Re: lmc bugginess

On Sat, 2003-03-22 at 22:09, Ed Sweetman wrote:

> I'm making some compromises for speed, since ogg vorbis files dont have 
> anything like xing's vbr tag which gives an exact abr and allows for 
> exact time length without parsing the entire file and somewhat exact 
> seeking (it would be pretty complicated to do exact seeking in a vbr 
> file), i'm using the bitrate_nominal data.  the accuracy of this number 
> is soley up to the encoder.   I could get the exact data but this would 
> require 1 pass of the entire file which for files up to 6MB/10MB or so 
> is less than a second on my system, but i also have an extremely fast 
> hdd and nothing else is trying to get at it while i'm doing this.  The 
> innacuracy shouldn't be too far off so long as the encoder isn't 
> dropping the ball on it.  I believe we have the same problems for mp3 
> files without the xing vbr tag that are vbr as well.

If we don't get the exact time when a file is first scanned, will the
database be updated when the track is actually played? I guess it
doesn't do this right now. Maybe the method needs to be a preference? I
think for some people getting reasonably accurate times could be
important. (e.g. when putting togethor compilations, or planning a radio
show?)

Although we all know that time is an illusion! right? Speaking of which,
I make it lunch time. ;-)

I've noticed that there can be some quite dubious time estimates made by
various programs. Especially if the mp3's are downloaded of the net.
There seems to be some seriously broken mp3 encoders out there.

I have tracks that xmms gets a bit rate of 8kbps, (although when it
actually plays it's 128kbps), and mpg123 -t shows as 448 kbps, and it
skips most of the file as junk.

Maybe we need some kind of tool in the music browser to help you find
and fix broken files.

Rob




-------------------------------------------------------
This sf.net email is sponsored by:ThinkGeek
Welcome to geek heaven.
http://thinkgeek.com/sf