search for: header_integr

...If it's not, let me know and I'll take it elsewhere (perhaps vorbis-dev). Saved streams are great - it lets this norteamericano get his fill of BBC Radio 1's Essential Mix. Unfortunately, saved streams aren't seekable. Running ogginfo on the stream data gives: erial=1626603590 header_integrity=pass vendor=Xiphophorus libVorbis I 20011231 version=0 channels=2 rate=44100 bitrate_upper=none bitrate_nominal=128031 bitrate_lower=none stream_integrity=fail stream_truncated=true header_integrity=fail Reported length varies; Winamp seems to think this is 6653:18 in length, while most tools t...

...If it's not, let me know and I'll take it elsewhere (perhaps vorbis-dev). Saved streams are great - it lets this norteamericano get his fill of BBC Radio 1's Essential Mix. Unfortunately, saved streams aren't seekable. Running ogginfo on the stream data gives: erial=1626603590 header_integrity=pass vendor=Xiphophorus libVorbis I 20011231 version=0 channels=2 rate=44100 bitrate_upper=none bitrate_nominal=128031 bitrate_lower=none stream_integrity=fail stream_truncated=true header_integrity=fail Reported length varies; Winamp seems to think this is 6653:18 in length, while most tools t...

>>I realize that I may have unintentionally been misleading you by leaving some information out. That error report from ogginfo keeps going, repeating the same 3 errors (as above) over and over again. It ends after a stream_truncated=true, not giving a final header_integrity=fail. (Perhaps because there's not another packet?) Then it reports a total playtime of 0. > >Yes, this is ogginfo's normal "argh!" response to any sort of stream >inconsistency - it gets the rest of the stream completely wrong. Don't >worry about it. There...

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

>> Running ogginfo on the stream data gives: >> stream_integrity=fail >This line in the ogginfo output concerns me. It means that there are actually >damaged Ogg packets in the stream. How are you saving this stream to disk? This particular one was obtained with wget on OpenBSD. I've observed the same problem with files saved from Winamp. >I think there is a problem

...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 and nothing more. I was merely being impatient. I usually record 11 hours of radio per day (6 hours automated + 1 hour automated + 4...

.... <snip> Vorbis stream 1: Total data length: 3527030 bytes Playback length: 3m:32s Average bitrate: 132.944968 kbps Logical stream 1 ended Warning: Hole in data found at approximate offset 3530268 bytes. Corrupted ogg. <p>---------- ogginfo rc3 erial=715851111 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...