search for: total_playtime

...erial=1037942235 header_integrity=pass vendor=Xiphophorus libVorbis I 20011217 version=0 channels=2 rate=44100 bitrate_upper=none bitrate_nominal=96016 bitrate_lower=none stream_integrity=pass bitrate_average=65 length=182692.561270 playtime=3044:52 stream_truncated=true total_length=182692.561270 total_playtime=3044:52 <----------------- what winamp also thinks. E:\> ---------------------------------- While this looks allright, there appears to be some errors: Obviously playtime/total lenght is way up. (true time is 1.50) Average bitrate was reported 96kbps in winamp _wh...

...the point where Ctrl-C doesn't work, and I have to `killall ogg123` from another virtual console. Something to work out? I'm not sure what to make of ogginfo. With RC3 ogginfo, I could do something like this... find -type f -name *.ogg -exec ogginfo {} \; >> files.txt grep "^total_playtime=" files.txt > lengths.txt ...or grep whatever. I'm looking for a new strategy to replace my old "grep header_integrity=" test. That's not a request for help, only an observation that I like the geeky RC3 ogginfo program better so far. Anyway, that's a status report...

After accidentally ogginfo-ing a WAV file, I'm wondering if there's any reason I shouldn't commit my fix that breaks out of the current file test if header integrity fails. Is there any case where the header integrity will fail but there is still any useful information to get out of the stream? I don't think so... -- Kenneth Arnold <ken@arnoldnet.net> - "Know

...51111 header_integrity=pass <snip> vendor=Xiphophorus libVorbis I 20010813 version=0 channels=2 rate=44100 bitrate_upper=none bitrate_nominal=128000 bitrate_lower=none stream_integrity=pass bitrate_average=132758 length=212.240000 playtime=3:32 stream_truncated=false total_length=212.240000 total_playtime=3:32 ----------------- What could cause this? (Other than physical data loss.) This file never went anywhere. Ripped with grip, directly to a local hard drive... possibly a bad sector though, hard drive was replaced, was still under warranty. Didn't think the oggs were affected, and these &qu...