similar to: Floor1 encode/decode and FLOOR1_fromdB_LOOKUP

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

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

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

Lancer 20060302 (based on aoTuV 4.51) http://homepage3.nifty.com/blacksword/ Changes: * update to oggenc v2.81 * optimized SSE2 code implementation * bark_noise_hybridmp and seed_curve are inline assembled * modified mdct_forward's SSE optimization * double step bresebham algorithm for render_line, render_line0 implementation

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, 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, We are two students doing project with Vorbis audio compression for our B.Sc studies. We have two questions: Our first question related to the floor1 inverse dB lookup table. As we understood the floor values encoded as offset integers (Y) from 1 to 256 and then used as index in the floor1_inverse_dB_table to get an encoded value. This value (denoted as X) is inverse of linear frequency so

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

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

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!

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

Mandag, 2 juni 2003, skrev du: >On Mon, 02 Jun 2003 21:22, Vitaly Nechyos wrote: >This is what people usually want when they say 'normalization'. AFAIK, you >can't easily tinker with the vorbis frames to add a scale factor in the same >way you can with MP3, but I could be wrong. I could be wrong too, but if I haven't overseen anything, it should be possible to

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

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