On Tue, Jan 22, 2002 at 08:48:03PM -0500, Kenneth Arnold
wrote:> 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...
>
Somehow I ended up with a file that the remnants of some other stream
chained to the front. The file plays fine in ogg123, but ogginfo
prints the following:
filename=1d4e3e4d2e4e625aa0da49.ogg
header_integrity=fail
stream_integrity=fail
stream_truncated=true
erial=16971
header_integrity=pass
Encoded using DropOgg 1.0.3d1 Build 20010122 (PPC)
vendor=Xiphophorus libVorbis I 20001031
version=0
channels=2
rate=44100
bitrate_upper=none
bitrate_nominal=128000
bitrate_lower=none
stream_integrity=pass
bitrate_average=121141
length=228.586667
playtime=3:48
stream_truncated=false
total_length=228.586667
total_playtime=3:48
Hopefully this kind of case is not common.
-- Aaron Plattner
-------------- next part --------------
A non-text attachment was scrubbed...
Name: part
Type: application/pgp-signature
Size: 233 bytes
Desc: not available
Url :
http://lists.xiph.org/pipermail/vorbis-dev/attachments/20020122/20dc42e3/part-0001.pgp