similar to: New LSP code committed

It seems to me that in this version of the function using float p=.7071067812f; float q=.7071067812f; will just leads after applying all the products and squaring to p and q having a common factor 0.5 which can be extracted from the formulaes. So I propose to replace: float p=.7071067812f; float q=.7071067812f; float w=vorbis_coslook(wdel*k); float *ftmp=lsp; int

(Disclaimer: this is not an LPC vs. LSP question) After looking at the Vorbis code I was wondering why you were using LSP to quantize the spectral envelope instead of simply quantizing the cepstrum (DCT(log(envelope))) or modified cepstrum (DCT(envelope.^alpha)). To me it seems like when the information is already in the frequency domain, there's no need to go back to LPC. Also, I think a DCT

Jack, I got the asm we were working last night committed ont he beta 3 branch. It's in use in both vorbisfile:ov_read() and the lsp lookup (when using float lookups) I'd like to have a patch of the other things you did in the past day or so, even if you don't want to commit yet. Monty --- >8 ---- List archives: http://www.xiph.org/archives/ Ogg project homepage:

All, Am running asterisk on an Opteron 165 with 4GB RAM and 1x80GB and 1x320GB SATA for a call center application (running VICIDIAL). Asterisk CLI (accessed by screen logging asterisk on startup and entering the allocated screen) gives me 'Warning LSP Low' and the voice quality goes down when this message pops up! That is, to start, we use: `/usr/bin/screen -L -d -m -S asterisk

Jean-Marc, Last week I tried the SVN code (build 11700) on the TI C55x DSP, and found that operation was broken again. I traced this to build 11522, committed on 5 June. The problem is in lsp.c, function lsp_to_lpc(). The line (lsp.c line 461 in build 11700): xin = 1<<(QIMP-1); /* 0.5 in QIMP format */ evaluates to zero. The following change corrects the problem: xin =

Hi, I think that the introduction of the lsp_look lookup array isn't ideal and found a better change that can be applied. in floor0_map_lazy_init() you can replace look->linearmap[W][j]=val; by look->linearmap[W][j]=vorbis_coslook(M_PI*val/look->ln); and in vorbis_lsp_to_curve you then replace float w=vorbis_coslook(wdel*k); ... }while(map[i]==k); by float w=map[i]; ...

One other thing that may or may not illuminate the situation. When I run under gdb (on OS X 10.8.3 this is an ancient version of gdb 6.3.5 - but it works with clang compiled C++ code) I get the following error when I try to list a line in dwarf1.lsp: Dwarf Error: Cannot handle DW_FORM_<unknown> in DWARF reader [in module /Users/meister/Development/cando/src/tests/core/dwarf1.bundle] (gdb)

Here are two optimisations for LSP : in vorbis_lsp_to_lpc, Ae and Ao are filled with zero when i increase so you can reduce the j loop, and I replaced qsort in cacm (maybe there are better algorithms, but it's already much faster than qsort on my mac) void vorbis_lsp_to_lpc(double *lsp,double *lpc,int m){ int i,j,m2=m/2; double *O=alloca(sizeof(double)*m2); double

Hi there, I would like to ask something about how to avoid a possible error message within a for loop. I am running a simulation and in some repetitions there may be an error that will cause a crash and stop the whole procedure, what I want is to simply move on to the next iteration automatically and discard the "bad" repetitions from my results. I used the "try" function to

When I try to open a specific file from a samba share (LSP), the application (on WINXP) says that it could not open the file. The errors pasted below (from the smb client) show something different from anything I've seen before. Usually these kinds of problems are straight forward. In other words, usually this is a permission issue. In this case, it is not. I am trying to open a file

Hi, I've downloaded the Speex-1.1.5 code and am trying to compile the Speexdec code using Microsoft VC++ 6.0 IDE. When I try to open the speexdec.dsw workspace, I get a dialog asking to locate the ogg_static file. I simply cancel that message, and then the project is opened in the VC++ 6.0 IDE. Now, when I simply try to compile the program, I receive this 5 error messages. error1.

Okay, Not exactly the answer I was looking for. This sounds like a big change. I don't mind re-writing the LSP quantizer but re-training code books and breaking compatibility is not what I want to do. I am working on an optimization for an ARM cortex-A8. It is desirable to process things in 4 element blocks. Is there a simpler approach you could recommend? Vasant Shridhar

Please forgive me if you already received this. I had an e-mail sending glitch this morning. http://cran.r-project.org/src/contrib/checkSummary.html reported an error in Design.trans.Rd * checking Rd files ... ERROR Rd files with syntax errors: /var/mnt/hda3/R.check/r-devel/PKGS/Design/man/Design.trans.Rd: unterminated section 'alias' The .Rd file is attached. It begins

Jean-Marc, >> > It's odd that it "almost" works with the fixed_generic.h. The easiest >> > thing would be to gradually replace routines and see which one causes >> > problem. It's most likely (though I'm not 100% sure) that somewhere in >> > the code, I have a 16-bit value that gets sent to a function/macro that >> > expects a

I upgraded my versions of llvm, clang and compiler-rt to the top-of-tree versions from last night (r180162, April 24). I recompiled debug versions of llvm, clang and my code. I then regenerated my test case and the results were the same - I can list lines of dwarf1.lsp in lldb but I can't set break-points or do anything else (what else should I be able to do?). The updated file that

After playing with the vorbis code for a while and doing tons of hacks and analysis on it, I've found it to perform very poorly with impulse signals. The MDCT seems to cause lots of spreading, and it seems to result in much worse impulse performance then mp3. What is the current plan on handling this? Will a smart quantizer be able to avoid it? I've been looking at various ways of

Hi Jean-Marc, I thought at quality 3 (wideband) - wb_submode1 that the 4-8k band was not using a codebook table. From the code I can see that some sort of "lsp" encoding is performed. What exactly does this encode? (I assume lsp means line-spectral pairs) The reason I am asking is I'm comparing the "effective" spectral bandwidth of Speex against the

Hi Alastair, Thank you so much for the information on the tools. Actually, I need to analyze which sections of code are prone to misses and mis predicts, and would have to eventually instrument the code. I was able to instrument and call an external function, but faced an issue while passing an argument to the function. I am following EdgeProfiling.cpp but couldn't figure out the problem.

I've not so much bandwidth to add channel coding but i've few bytes to spare for error detection. With a polynomial CRC-8 i've already more than 99.6 % to detect a burst error in a frame. So let's suppose the critical fields of Speex are: Wideband bit Mode ID LSP OL pitch OL pitch gain OL Exc gain So my plans are to calculate a CRC on these fields for each frame i send, then if i

I would like to know if my vision of things is correct about frame structure. -------------------------------------------------------- Frame header -------------------------------------------------------- Subframe1 header|Subframe1 content| -------------------------------------------------------- Subframe2 header|Subframe2 content| --------------------------------------------------------