ogginfo doesn't play nice with libvorbis 1.1

Bug #21904 reported by Paulo J. S. Silva on 2005-09-17
4
Affects Status Importance Assigned to Milestone
vorbis-tools (Ubuntu)
Medium
Tollef Fog Heen

Bug Description

Hello,

I have just noticed that libvorbis 1.1.0 entered Breezy, great!

However when I use ogginfo on a vorbis file enconded with the new vorbis
library I get a warning stating that the ogg file is corrupted (see an
example below). The error is discovered at the end of file. This may scare
users.

-- Example output --

pjssilva@leia:~/musicas/vorbis/radiohead/ok_computer$ ls -l airbag.ogg
-rw-r--r-- 1 pjssilva pjssilva 5906560 2005-09-17 17:32 airbag.ogg
pjssilva@leia:~/musicas/vorbis/radiohead/ok_computer$ ogginfo airbag.ogg
Processing file "airbag.ogg"...

Warning: Hole in data found at approximate offset 4500 bytes. Corrupted ogg.
New logical stream (#1, serial: 1ee6fad4): type vorbis
Vorbis headers parsed for stream 1, information follows...
Version: 0
Vendor: Xiph.Org libVorbis I 20040629
Channels: 2
Rate: 44100

Nominal bitrate: 160,000000 kb/s
Upper bitrate not set
Lower bitrate not set
User comments section follows...
        title=Airbag
        artist=Radiohead
        genre=Pop
        date=1997
        album=OK Computer
        tracknumber=01
Vorbis stream 1:
        Total data length: 5900259 bytes
        Playback length: 4m:43.626s
        Average bitrate: 166,423251 kbps
Logical stream 1 ended
Warning: Hole in data found at approximate offset 5906560 bytes. Corrupted ogg.

Tollef Fog Heen (tfheen) wrote :

I'm unable to reproduce this problem:

: tfheen@xoog /tmp > sudo cdparanoia 1 airbag.wav
cdparanoia III release 9.8 (March 23, 2001)
(C) 2001 Monty <email address hidden> and Xiphophorus

Report bugs to <email address hidden>
http://www.xiph.org/paranoia/

Ripping from sector 0 (track 1 [0:00.00])
          to sector 21331 (track 1 [4:44.31])

outputting to airbag.wav

 (== PROGRESS == [ | 021331 00 ] == :^D * ==)

Done.

: tfheen@xoog /tmp > oggenc -q5 airbag.wav
Opening with wav module: WAV file reader
Encoding "airbag.wav" to
         "airbag.ogg"
at quality 5,00
        [ 99,8%] [ 0m00s remaining] /

Done encoding file "airbag.ogg"

        File length: 4m 44,0s
        Elapsed time: 0m 12,0s
        Rate: 23,6408
        Average bitrate: 165,9 kb/s

: tfheen@xoog /tmp > ogginfo airbag.ogg
Processing file "airbag.ogg"...

New logical stream (#1, serial: 05a55d17): type vorbis
Vorbis headers parsed for stream 1, information follows...
Version: 0
Vendor: Xiph.Org libVorbis I 20040629
Channels: 2
Rate: 44100

Nominal bitrate: 160,000000 kb/s
Upper bitrate not set
Lower bitrate not set
Vorbis stream 1:
        Total data length: 5899617 bytes
        Playback length: 4m:44.426s
        Average bitrate: 165,937099 kbps
Logical stream 1 ended
: tfheen@xoog /tmp >

Can you provide me with what set of switches you called oggenc with (or what
other tool you used)?

Paulo J. S. Silva (pjssilva) wrote :

(In reply to comment #1)
> I'm unable to reproduce this problem: ...
>
>
> Can you provide me with what set of switches you called oggenc with (or what
> other tool you used)?

After your comment, I have confirmed that the command line oggend doesn't present
problems here. I only get the problems if I use grip.

After realizing that I have decided to move my old grip configuration away and start
with a fresh grip run. Now grip does not presents any problems either. I believe
we can consider this "bug" invalid. Should I change the bug status, or are you
supposed
to do it?

Do you think I should contact the grip people with my old config?

Thanks!

Tollef Fog Heen (tfheen) wrote :

Ok, closing as invalid.

If the problem is reproducible by changing settings in grip, I'm sure the authors would like
a bug report, yes.

To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.