search for: centerw

I'm looking at the vorbis_synthesis_blockin and pcmout functions, and I'm confused about the positioning and determination of centerW wrt adding in the next set of data. Specifically, it seems legal (in vorbis_synthesis_pcmout) to return to the user any data up to the centerW position; however, in vorbis_synthesis_blockin, if you have a long block following a short block, it is legal to overlap the long block back to a position b...

...s_blockout in lib/block.c, we see what how the largebound parameter is chosen: For the large block W [using the 3/4-pt to 1/4-pt overlap rule that seems to be implied by the code], ``stop searching when j gets to the midpoint of a short block following a long block.'' largebound = centerW + B/4 (to get to 3/4-pt of W) + B/2 (to get to 3/4-pt of a big nW) + S/4 (to get to mid-pt of a small nnW) This make sense and is in the code. BUT the formula for the small W case seems incorrect (and much too big) I would rather say: (S=s...

...0, time_bits = 0, floor_bits = 0, res_bits = 0, internal = 0x647330} vorbis_dsp_state: (gdb) p vdsps $10 = {analysisp = 1, vi = 0x7fffffffdde0, pcm = 0x642750, pcmret = 0x642770, pcm_storage = 221012, pcm_current = 55376,    pcm_returned = 0, preextrapolate = 1, eofflag = 0, lW = 0, W = 0, nW = 0, centerW = 512, granulepos = 256, sequence = 4,    glue_bits = 0, time_bits = 0, floor_bits = 0, res_bits = 0, backend_state = 0x608790} ===== oggpack_buffer comes from ogg/ogg.h, so I guess it may add some things not native to "pure" vorbis. Am I to understand that I am dependent on the ogg li...