[vorbis] Byte-width of a bitstream, cabbages, and other things

[Ignacio Vazquez-Abrams]

On Wed, 29 Aug 2001, Michael Smith wrote:

> At 04:59 AM 8/29/01 -0400, you wrote:
> Vorbis encodes everything (and decodes everything) as floating point. As
> such, there _is_ no concept of 8 or 16 bit input/output. However, in
> interfacing to the outside world, it's obviously neccesary to convert
> to such formats. VorbisFile supports two widths - 8 and 16 bits. However,
> should it prove useful, it'd be very easy to add support for 24 bit
> output - that hasn't been done because there hasn't been any demand for it.

I'm guessing that mixing 8-bit and 16-bit reads in the same bitstream is safe
then (even if silly)?

> Encoding is a similar situation - you need to convert to floating point
> before passing the data into the encoder. oggenc, for example, supports 8
> and 16 bit input (as well as direct floating-point pcm input, though I
> think that's buggy on big-endian platforms). Again, if anyone actually
> wanted 24 bit input, it'd take about 5 minutes to add.

Same as above with encode as well then?

> Michael
>
> p.s. update to rc2 ASAP, please. beta4 can't decode all vorbis files.

Meh. I would but the only stuff I have to decode is stuff that I've encoded
myself, and all I have is a little 28-second test file @ 160kbps. Sounds
beautiful though ;)

IOW, sure, but I'll do it when I'm not busy.


-- 
Ignacio Vazquez-Abrams  <ignacio at openservices.net>

--- >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.