similar to: FLOOR_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

Dear All, Floor 1 decoder uses FLOOR_fromdB_LOOKUP table. The purpose of this table is not clear to me. It is also not explicitly explained in the vorbis specification. As i have understood is that it is used to dequantise the "Y" values which are decoded from the bitstream during curve synthesis. Is this correct ? If so why does the table have only 256 elements ? This would imply

Hi! I have some questions about R function. I try to write a function for multi-returns. The function code is as attachment. dgp.par<-function(ai, bi, t, n) { t0<-t+20 y0<-matrix(0, nr=t0, nc=n) y0[1,]<-ai/(1-bi) for(tt in 2:t0) { y0[tt,]<-ai+bi*y0[tt-1,]+rnorm(n, 0, 1) } y<-y0[21:t0,] x<-y0[20:t0-1,] z<-y0[19:t0-2,] z<-z[2:t,] dy<-y[2:t,]-y[1:t-1,]

Plotting vector fields as we know it from Wolfram Mathematica's PlotVectorField[{f1(x1), f2(x2)}, {x1, min, max}, {x2, ymin, ymax}, PlotPoints -> ...] ### FUNCTION DEFINITION #! Outer product with vector function ### # expand.outer joins functionality of "expand.grid" and "outer", so that # a vector function can be applied, values of which are then stored 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] =

Why does R think these numbers ***are*** equal? In a somewhat bizarre set of circumstances I calculated x0 <- 0.03580067 x1 <- 0.03474075 y0 <- 0.4918823 y1 <- 0.4474461 dx <- x1 - x0 dy <- y1 - y0 xx <- (x0 + x1)/2 yy <- (y0 + y1)/2 chk <- yy*dx - xx*dy + x0*dy - y0*dx If you think about it ***very*** carefully ( :-) )

Thanks to Dieter Menne and Spencer Graves I started to get my way through lsoda() Now I need to use it in with nls() to assess parameters I have a go with a basic example dy/dt = K1*conc I try to assess the value of K1 from a simulated data set with a K1 close to 2. Here is (I think) the best code that I've done so far even though it crashes when I call nls()

Hello! Some minor bugfixes... source: psy.c function: _vp_psy_init 1. '-' or '+' in this line? maxoc=toOC((n*.5f - .25f)*rate/n)*(1<<(p->shiftoc+1))+.5f; maxoc=toOC((n*.5f + .25f)*rate/n)*(1<<(p->shiftoc+1))+.5f; 2. I know: sizeof(float *) and sizeof(float) are 4 bytes long, but... old lines: p->noisemedian=_ogg_malloc(n*sizeof(float *));

I frequently run scripts that generate multiple graphs. Unless you specify a specific window location, dev.new superimposes all new graphics windows exactly on top of each other. It would be nice to have a "cascade=TRUE" option in dev.new to prevent windows from being hidden. A hasty approximation to this is the following function: # utility function to prevent overlapping plot

Dear all, I feel like I've been reinventing the wheel with this code (implementing type = 'b' for Grid graphics), http://econum.umh.ac.be/rwiki/doku.php?id=tips:graphics-grid:linesandpointsgrob Has anyone here attempted this with success before? I found suggestions of overlapping large white points to mask the lines but it's not ideal. I welcome any comments on the code.

If you select an option that's not listed during ipv4/ipv6 setup it will accept it without verification. This corrects that behavior and forces a valid option to be picked. --- scripts/ovirt-config-networking | 106 +++++++++++++++++++++------------------ 1 files changed, 58 insertions(+), 48 deletions(-) diff --git a/scripts/ovirt-config-networking b/scripts/ovirt-config-networking index

Hi I am trying to use tree() to classify movements in a futures contract. My data is like this: diff dip dim adx 1 0 100.00000 8650.0000 100.00000 2 0 93.18540 2044.5455 93.18540 3 0 90.30995 1549.1169 90.30995 4 1 85.22030 927.0419 85.22030 5 1 85.36084

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

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