similar to: Porting Speex to embedded 32bit

Dear Speex developers I am going to port Speex on LPC2368 I tested Speex encoding and the mesurments shows ~40ms cpu time for one frame Do you know who ported speex to NXP or other 32bit platform? Best Regards Zohar fox -------------- next part -------------- An HTML attachment was scrubbed... URL: http://lists.xiph.org/pipermail/speex-dev/attachments/20081105/8261e962/attachment.htm

Hi Jean-Marc, I have just discovered the post of Vit Kanevsky and I have already sent him a message. I'm currently evaluating the work of stripping stuff on the win32 platform(nicer workflow ;-) and noticed that I could not just leave out the exc_*_table.c files without getting compiler/linker warning, but possibly I made a mistake there. Is my assumption correct that I just need the

Hi to group I want to use speex for an embedded device caryying voice over rs485 .The controller i'm using is LPC2368. I recompiled the code written for stm32 . I used as per original file 8khz , narrowband,complexity 1 , quality 4 ,fixed point , generic model . Cpu speed is 72 MHZ .Running some benchmarks for the codec i found out that i have almost 90% cpu utilisation.It was about 19 ms

Hi everyone, I'm currently looking into using speex in an embedded project using an ST ARM-device (STR9 family) just with internal memory (96kbyte) and no O/S. Does anyone know if the optimizations included in the code for ARMv4 and ARMv5e are appliable to this device? I would also need to strip down libspeex pretty hard to fit into the available memory. I just want to use a fixed bitrate

two OutputsHello! I am Amelia from Auckland and work for a bank. I am new to R and I have started my venture with R just a couple of weeks back and this is my first mail to R-forum. I need following assistance Suppose my R code generates following outputs as > X [[1]] [1] 40 [[2]] [1] 80    160 [[3]] [1] 160   80  400 > Y [[1]] [1] 10 [[2]] [1] 10    30 [[3]] [1] 5  18  20

Dear R users, I've had no joy finding a solution to this online or in any of my R books. Many thanks in advance for any help you can give. I'm seeking to output a data frame (or matrix - it doesn't matter which for my purposes) to a .txt file, but omit any row or column names. The data frame that I'm using doesn't actually have column or row names to start with as it has been

Hello, I want to access a shared folder on my linux from a windows machine. The smb.conf has this entry ?? [samba_share] ??????? comment = QEMU share place ??????? path = /media/samba_share ??????? valid users = mahmood vb ??????? public = no ??????? writable = yes ??????? printable = no ??????? create mask = 0777 Then I added a user to samba with "smbpasswd mahmood". The folder mask

Dear list, hi ! I am a R beginner and I have a function to optimize . alpha = argmin{ f(x,alpha) } I want alpha to be in [0,1]. Is there any function that can work? I use nlm() but i can't fix the domain of alpha. thanks in advance _______________________ Jiang Peng, Ph.D. Candidate Department of Mathematics & Antai college of Economics and Management Shanghai Jiao

Hi, I am trying to implement Speex in freeRtos on LPC2138 (ARM7 core), to record about 10sec of voice. I like to compress the data by using Speex, because of the limitation of RAM (32KB). I have read that the speex encoder and decoder need less than 6KB RAM. "The fixed-point narrowband encoder+decoder memory use has been cut by more than half, making it possible to fit both in less than 6 kB

Hello all, I am re-posting my previous question with a simpler, more transparent, commented code. I have been ramming my head against this problem, and I wondered if anyone could lend a hand. I want to make parallel a bootstrap of a linear mixed model on my 8-core mac. Below is the process that I want to make parallel (namely, the boot.out<-boot(dat.res,boot.fun, R = nboot) command).

It would be great to get some idea of what chips and DSPs people have tried to compile Speex for, and what success they've had. So, if you've tried Speex on a chip, could you take a second to fill in the following and post it to the list? Chip Name: Speex Version: Floating or Fixed: Encode, Decode, Both or Simultaneous: MIPS (if known): Other comments: Many thanks, Gerv

Jean-Marc Valin wrote: > I don't know all the details, but here's a (partial) list of archs on > which I've heard of Speex running. I'm sure there are others (especially > the float version should really run on any chip with an FPU). > > float: > x86/x86-64 (SSE assembly optimizations provided) > PowerPC > SPARC I've had floating decoding running on a

I am using speex on a Philips LPC2138 Arm 7 processor and have hit two compiler warnings when using FIXED_POINT and the Arm 4 asm code. In cb_search.c get a warning on the call to compute_weighted_codebook of: "passing arg 2 of 'compute_weighted_codebook' from incompatible pointer type' In cp_search_arm4.h it is defined as: static void compute_weighted_codebook(const signed

Yes those instructions exist, although they're a bit slower than the basic 16x16->32 with 32-bit accumulation (SMLABB). So I'd be surprised if the function with 64 bit accumulation would run as fast as the current code. Don't know how much we care about 16-bit platforms. And accuracy should not matter. On the other hand, a 64-bit implementation is much cleaner/shorter, which is

Hi all, I'm trying to log chart but with natural looking tick marks. My specifications are very specific -- it must indicate the lowest number's tick as well as the maximum. I've attached sample code and data for a particular case (and there are a few more like this) where the bottom tickmarks on the chart are not set to where I want them to be and yet they fit in the ylim range.

Hi there. I noticed that the speex.org website does not appear to give a table of what bitrates you can expect when using the SPEEX codec in CBR (quality) mode. I have created a table for all modes, giving the bitrate for two cases. a) all coded frames saved consecutively in bitstream b) all coded frames saved with byte alignment You can see there is significant padding loss at some (lower)

Thanks for the clarifications, Bob! I’ve spent some time with the head of the llvm.org repo, and I now understand a lot better what Renato and Tim were talking about re. the architecture aliases. The patch to add v6l, therefore, seems simple enough. I haven’t been able to test it in my usual flow, because that involves the whole swift stack. I’m considering creating a program that links to

Right, there shouldn't be a problem with undefined behavior. That said, a 64 bit implementation will work very well - in fact that's how it was done originally. The reason for the current implementation is to minimize 64-bit operations in order to improve performance on limited-width architectures. This functions gets used extensively, and I think the current implementation is faster on

On Mon, 2006-01-23 at 10:15 -0500, tom abcd wrote: > I am using speex on a Philips LPC2138 Arm 7 processor and have hit two > compiler warnings when using FIXED_POINT and the Arm 4 asm code. > > In cb_search.c get a warning on the call to compute_weighted_codebook of: > "passing arg 2 of 'compute_weighted_codebook' from incompatible pointer type' OK, I forgot to

Hi Tom Thanks, just at the feasibility phase right now, so this sort of info is really useful. Memory/MHz values for the Tremor/Vorbis code seem to vary wildly - at least I could not find a consistent set of numbers after trawling through the discussion groups... Thanks John -----Original Message----- From: tom abcd [mailto:tom.abcd@gmail.com] Sent: 28 March 2006 16:34 To: Anderton, John