search for: floor1_i

Hi everyone, after having an extensive look at the reference decoder as well as the specification documents, I'd like to point out what I think to be some minor omissions/flaws in the latter, and suggestions for correcting them. --- #1: in vorbis-spec-floor1.html, packet decode: Between 14) and 15) a crucial step is missing. Please insert: 14a) [cval] >>= [cbits] ---- #2: in

Hi, I've found some more errors in the file format specification (or at least points, where the specification and actual libvorbis implementation mismatch): - Floor 1 / curve computation / step 1: amplitude value synthesis 21) vector [floor1_final_Y] element [i] = [predicted] - (([val] - 1) divided by 2 using integer division) hould be: 21) vector [floor1_final_Y] element [i] =

Hello, I've been "playing" a little with the floor1 encoding, and my game has posed me a question. I've been modifying (just curiosity) manually, and randomly (not too great modifications), the quantized [floor1_Y] values, just before coding them with the codebooks. As, if I'm not wrong, the [floor1_Y] obtained are then removed to get the residue vectors for each channel, I

...r1 encoding/decoding. First I'll ask about the FLOOR1_fromdB_LOOKUP table: what is it's purpose? Is it to convert the amplitude differences between [floor1_Y] values to a dB scale? And, if I'm right with that, here comes the 2nd question: when render_line0 is used to encode floor1, then floor1_inverse2 must be used in decode (in order to convert to dB scale), and, in the other hand, if render_line is used to encode, then floor1_inverse1 must be used in decode (render_line converts to dB and therefore floor1_inverse1 gets the amplitudes in dB). If all my suppositions are right, is there any...