[vorbis] Residue bit usage, library incompatibilities

[Michael Smith]

At 07:08 PM 11/21/01 -0600, you wrote:
>I've been using the rc2 releases of Vorbis for a while now. I've been
>in the process of making digital copies of a bunch of my music, and I
>keep getting this "residue bit usage" message when oggenc finishes. I'm
>trying to encode data from an audio CD at 160bps, and it always seems
>to get booted back down to ~128 bps with this residue bit ussage
>message. Again, I'm using the rc2 libvorbis, libogg, and vorbis-tools,
>with the libao 0.8 available from the download area on xiph.org. The
>beta4 libraries don't do this. Is this -supposed- to happen, or some odd
>sort of bug?

You're not using rc2. You're using post-rc2 cvs libvorbis. The bitrate
in cvs is currently fixed (it's in-progress code. Not recommended for
non-developers), and it has various debugging messages.
>
>To get around this, I'd just roll back to the beta4 releases of
>everything, but beta4 tends to report zero bitrates, infinite
>lengths, and ridiculously large negative-number playtimes from files
>encoded using rc2.

Weird. It shouldn't report anything at all, it shouldn't be able to
even start playing, since rc2 uses bits of the vorbis format which 
weren't added until the format was finalised (rc1) (or is something not
checking library function return values?)

Michael

--- >8 ----
List archives:  http://www.xiph.org/archives/
Ogg project homepage: http://www.xiph.org/ogg/
To unsubscribe from this list, send a message to 'vorbis-request at xiph.org'
containing only the word 'unsubscribe' in the body.  No subject is needed.
Unsubscribe messages sent to the list will be ignored/filtered.