Home | History | Annotate | Download | only in doc

Lines Matching defs:codebook

4 \section{Probability Model and Codebooks} \label{vorbis:spec:codebook}
19 The codebook mechanism is built on top of the vorbis bitpacker. Both
27 \subsection{Packed codebook format}
34 \subsubsection{codebook decode}
36 A codebook begins with a 24 bit sync pattern, 0x564342:
79 codebook contains unused entries that are not to be included in the
87 codebook entries:
116 codebook is encoded in ascending length order. Rather than reading
154 Codebook decode precedes according to \varname{[codebook_lookup_type]}:
204 Briefly, each used codebook entry (recall that length-unordered
266 Similarly, in the original codebook, it's clear that the tree is fully
269 undecodable. Take special care that a codebook with a single used
271 bits and 'reading' a value out of such a codebook always returns the
274 Codebook entries marked 'unused' are simply skipped in the assigning
299 vector values are what a codebook would return during audio packet
306 final values of a codebook entry vector from the entries in
309 \varname{[lookup_offset]} in this codebook):
339 final values of a codebook entry vector from the entries in
342 \varname{[lookup_offset]} in this codebook):
370 \subsection{Use of the codebook abstraction}
372 The decoder uses the codebook abstraction much as it does the
373 bit-unpacking convention; a specific codebook reads a
379 to the codebook mechanism requests either a scalar entry number or a
383 requesting decode using a codebook of lookup type 0 in any context
389 Using a codebook to read from the packet bitstream consists first of
392 codebook. This process can be though of as logically walking the