search for: lsp

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) ---------- full gdb transcript follows ---------- (gdb) run Reading symbols for shared libraries ++++++++++++++++++++++...............................

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

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 describes the test case is at: https://dl.dropboxusercontent.com/u/6229900/dwarf1_new.txt I did have to make a few changes to my code to make it work with the latest llvm. In...

(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 domai...

...ut as this application uses 3.0.28a is indicated below, specifically the line "Intermediate not found linux-file1" This is unique when compared to another application opening such files. [2008/04/16 12:16:01, 5] smbd/filename.c:unix_convert(246) unix_convert begin: name = linux-file1/lsp/LSP-Current-User-Data/smuhammad/55622/55622-pc_Saver.exe, dirpath = , start = linux-file1/lsp/LSP-Current-User-Data/smuhammad/55622/55622-pc_Saver.exe [2008/04/16 12:16:01, 10] smbd/mangle_hash2.c:is_mangled(276) is_mangled linux-file1/lsp/LSP-Current-User-Data/smuhammad/55622/55622-pc_Saver.exe...

...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 c=m>>1; by: float w=vorbis_coslook(wdel*k); float p=lsp[0]-w; float q=lsp[1]-w; float *ftmp=lsp + 2; int c=(m>>1) - 1; and: vorbis_invsq2explook(qexp+m) by: vorbis_invsq2explook(qexp+m-1) André --- >8 ---- List archives: http://www.xiph.o...

So, it turns out (and another implementation actually explicitly mentions it) that LSP->LPC computation using the FIR algorithm is very sensitive to noise (iterative algorithm) and really really requires doubles [we're not kidding]. This was complicating things for folks pursuing fixed point implementations, and also was a potential source for bugs if FP optimizations got out...

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 = SHL32(EXTEND32(1), (QIMP-1)); /* 0.5 in QIMP format */ Regards, Jim Crichton -------------- next...

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 /usr/sbin/asterisk -vvvvvvvvvvvvvvvvvvvvvgc`; and then screen -r gives (among other processes) 2640.asterisk (Detached) and screen -r 2640 gives: Warning...

...so good and everything is working fine with "az" having the values of lse having also discarded the "bad" iterations. However I would like to store (as an output) both values (logitse AND logitsp) in the function logitsboots, that is the list would be as : list(lse=logitseb,lsp=logitspb). This way the quantity "res" would have two arguments: res$lse and res$lsp each time it is called. However when an error occures I just cannot seem to manage to "unlist" the "res" properly since typing "res$lse" for example will warn me that the &q...

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

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; do...

Hello I'm working on a fix-point decoder for AOS/Bluebottle - the proprietary OS of ETH Zurich. I've some problems with Floor0-curve-computation: I don't know what the little omega [cos(w)] stands for, line 3 of the official Vorbis documentation. Does anybody knows what this value means? I've tried to get the answer from the jOrbis and Tremor, but both seem to do - among

...esign.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 with \name{Design.trans} \alias{Design.trans} \alias{asis} \alias{pol} \alias{lsp} \alias{rcs} \alias{catg} \alias{scored} \alias{strat} \alias{matrx} \alias{\%ia\%} \title{ Design Special Transformation Functions } \description{ This is a series of functions (\code{asis}, \code{pol}, \code{lsp}, .... No error is detected when I run CMD CHECK using the latest R-devel locally,...

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

...en 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. d:\speex\speex-1.1.5\libspeex\lsp.c(104) : error C2054: expected '(' to follow 'inline' error2. d:\speex\speex-1.1.5\libspeex\lsp.c(105) : error C2085: 'spx_cos' : not in formal parameter list error3.d:\speex\speex-1.1.5\libspeex\lsp.c(105) : error C2143: syntax error : missing ';' before '{'...

...tion would first force the conversion to 32 >> > bits. My initial guess would be with the SH[RL]32 and ADD32 functions. Nice call. The culprit is SHRL32. This is not used in many places, and in most of those, the operand comes from EXTEND32. The only really suspicious instances is in lsp.c (lsp_interpolate): spx_word16_t tmp = DIV32_16(SHL32(1 + subframe,14),nb_subframes); (subframe is an int) > I just checked in changes that may fix some bad behavior on 16-bit > architectures. You might want to try if it fixes the problem. As I said, > it's not clear yet whether...

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: http://www.xiph.org/ogg/ To unsubscribe from this l...

...g this? Will a smart quantizer be able to avoid it? I've been looking at various ways of taking care of this, and before I bother implimenting something I'd like to make sure that no one has gone down this path before: Roughtly vorbis currently does: input wave -> MDCT -> LPC -> LSP -> quant -> ------------------>output \->delpc->error->quant -^ What do you think of this: input wav -> DWT -> sum non-impuse factors -> iDWT -> MDCT ... (like above) \ -> -> sum impulse fact...

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 AMR-WB (G.722.2) codec. (Available from 3GPP.org) Speex performs very compara...