similar to: Specification documents

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] =

Hi, as Conrad suggested, I've made a complete list of all points in the specification, which I beleive are errors, or where the explanation is unclear, contains unneccessary steps and so on. I hope someone has time to look through the points and if and when accepting or rejecting them be so very kind and inform me about it. I will also once again try to work through the residue

Hello, I have two questions concerning floor1 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

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

Hello, You know, I always worry about the precision and the float constants... and there is a large lookup table in the floor1.c ... and I figure out a way to keep the code size and speed, but to improve the precision at this lookup table. (the difference is small, but audible) Here is the modifications in the floor1.c: tatic unsigned long FLOOR_fromdB_LOOKUP[256]={

Hello, I was printing some Floor1 X values from a test audio file, and the values that I've obtained look mostly like the following: [23,33,46,65,79,93,111,130,158,186,220,260,312,372,464,556,750,1024] => For long blocks [8,16,33,70,128] => For short blocks Obviously they are not in Hz, so, could someone please tell me what is the unit used? In the specs it's said that the Floor1

Hi, In the course of some work which I describe below, I have found a very significant difference between the BARK function described in the Vorbis specification and its implementation in libvorbis. In the specificationhttp://xiph.org/vorbis/doc/Vorbis_I_spec.pdf bark(x) = 13.1arctan(.00074x) + 2.24arctan(.0000000185x**2 + .0001x) In the libvorbis code

Hi! While implementing a Vorbis I decoder, I have found a few errors in the specification. After making the following changes everything works as advertised, thank you! Errata: 1.) In section 7.2.2 Floor1 header decode (on a side not wouldn't 7.2.2.1 be the logical number here, looking at the overall structure of the document?), step 21 element element ([j] + [floor1_values]) should

Here is a test case: extern double floor(double); extern double floor_(double); double x = 1.5; double y, y_; void foo() { double y = floor(x); double y_ = floor_(x); } If I compile this for Mips16, it calls the proper helper function for floor_ but not for floor, because the signature for floor in callee info is wrong. Args[0] = void RetTy = void

Hi, is there an error in the last part of the algorithm describing how to read a floor1 header? According to point 18 and 19, the vector [floor1_class_dimensions] must have at least [floor1_partitions] elements, but when reading/computing these two values on the beginning of the header, they are not related to eachother, and my attempts to apply this algorithm to real ogg-files gives me

Hello, There is a bug in the current version of vorbis/lib/floor1.c. The line that says:- qsort(sortpointer,n,sizeof(int),icomp); should be:- qsort(sortpointer,n,sizeof(int *),icomp); But somebody probably fixed that already. :) Also, I'd like to know how I can encode a file using the channel coupling modes. oggenc doesn't have an option for that yet. Greetings,

Hi, Am trying to run beta4 encoder on a Sun machine. Want to compare floor0 and floor1. Do not have autoconf and automake. Got the encoder to compile with a simple makefile. The only define i am using is NO_FLOAT_MATH_LIB. The encoded file when played(winamp) gives out plain noise. Am i missing any other flags/defs? -Cathy <p>--------------------------------- Do you Yahoo!? Yahoo!

Hello, I've read in a thread from this mailing list ( http://lists.xiph.org/pipermail/vorbis-dev/2009-September/020019.html) that the usage of FLOOR1_fromdB_LOOKUP table is to convert Floor1 values from a dB scale to a linear scale. In a dB scale, given a reference value, the other dB values are obtained from it, normally dB_value = 10log(p1/p0), where p0 is the reference value. Supposing p0

Hi According to vorbis I spec, there are several configurations. There are 2 formats of floor, 3 formats of residue and 3 look up types of VQ codebook, etc. I think to get all kinds of vorbis file with these configurations but what I have got from network only support some of the formats (Ex. floor1, residue 1 & 2, VQ lookup type0 & 1). I downloaded several freeware vorbis encoder

Hi, Lately, my oggenc builds (from CVS) haven't been running correctly. In a few debugging sessions, I've found that I'm getting a divide by zero exception. The exception happens in accumulate_fit (floor1.c), line 455: int weight=nb*info->twofitweight/na; Here is the call stack: accumulate_fit floot1_fit mapping0_forward vorbis_analysis oe_encode main The

Hi Guys, I want to compile libvorbis, but I get this error message if I made a make. I use Sun Solaris 9 on a UltraSPARC Server and gcc 3.3 can anyone help me, please? <p>Best Thanks Daniel Here the message output from compiling. ----------------------------------------- /usr/ccs/bin/ld -G -z defs -h libvorbis.so.0 -o .libs/libvorbis.so.0.3.0 mdct.lo smallft.lo block.lo envelope.lo

VorbisHi Any help is appreciate. I have two questions. First, I looked into the vorbis-?-specific and was confused by the floor1 algorithm. I think at last the aim is to derive the piecewise curve with the list X and Y,then when encodering ,why not use the selected point orderly to get the curve ? In other words, the specific use the list of [0,128,64,32,96,16,48,80] , why can not use

A few more notes on the specs -- I just spent a few minutes and did up floor 1 header decode. Short and sweet, but still important. Monty, please read these and my several earliers -- I'm trying to improve and validate the spec for your codec, and though I understand you were taking a break before, a reply would be appreciated. Note (again, if you read my other emails) that if you help me get

Hi, I'm looking for more documentation on the Vorbis bitstream format. The goal for me is to write an optimized decoder using only integer or fixed point math for use on the Phatnoise Car Audio System (see http://www.phatnoise.com). I've already found the info on the Ogg framing system and I've already written my own thing for parsing through Ogg frames (easy). Also, is RTP

I'm getting some problems because it seems that the compiler is treating "floor" differently from other math library functions like "sin". The Args and RetVal have the parameter and return types marked as void. For mips16, it's important that I be able to know the original signature for floating point functions. In some cases, need to create calls to helper