similar to: How to get size of WB frame in bits/bytes?

> Oh, you're right, inband handling is different, but it's a matter of one > flag, passed to functioin. Probably not that much to keep code DRY. Well, let's first merge your code and then we'll see about possible simplifications. >> frame: 20 ms encoding >> sub-frame: 5 ms encoding (internal) >> layer: one frame of nb or sb >> sb: sub-band >>

> Ok, here is cleaned up and fixed version. > > * Function is named speex_get_num_frames() now and return > number of frames, as you suggested. > * WB layers sizes are taken from wb_skip_table[], while NB frame > sizes are calculated with speex_mode_query(). Looking better. Just make sure to remove the stuff that isn't C99-compatible (e.g. // comments). > I've

First patch fixes two typos in manual. Second patch adds few notes about latency, as promised. Hopefully I haven't added any typos and grammar errors :) On Wed, Jul 1, 2009 at 8:02 PM, Alexander Chemeris<Alexander.Chemeris at sipez.com> wrote: > Thank you for clarification. I attached a patch which (IMHO) > makes it more clear for everyone who just read Doxygen > docs.

Hi, I want to do a careful measure of mic-to-net and net-to-spkr delays in sip media engine and to make it really precise I need to know delays, introduced by Speex algorithms. In particular, I'm interested in delays of: 1) encoder in NB, WB and UWB modes, 2) decoder (I guess it should be 0?) 3) resampler. I think it varies depending on input rate to output rate ratio. Any generic formula or

Hi, Thanks! can this program generate speex.lib instead of libspeex.lib?? the OpenSpeak link to speex.lib instead of libspeex.lib I can compiled the libspeex.lib but not speex.lib. Correct me if I am wrong Thanks ----- Original Message ----- From: "Alexander Chemeris" <ipse.sipx@gmail.com> To: <alex@gorex.com.hk> Cc: <speex-dev@xiph.org> Sent: Tuesday, May 29,

On 11/28/07, Jean-Marc Valin <jean-marc.valin@usherbrooke.ca> wrote: > I think the amount of Windows crap is getting a bit ridiculous. Does > anyone know of a solution to keep things manageable? I mean, the same > autotools files manage the build for Linux PCs, Blackfins and MacOS (and > others). Yet, we need one set of files for each MS compiler version > (good thing they

On 02/04/2008, Alexander Chemeris <Alexander.Chemeris at sipez.com> wrote: > On 4/1/08, Keith Kyzivat <kkyzivat at sipez.com> wrote: > > IIRC, under ARM, I believe I was having issues with --without-libogg. > > I resorted to just downloading libogg sources, setting up my > > cross-compilation environment, and cross compiling it per the general build > >

On 12/13/07, Jean-Marc Valin <jean-marc.valin@usherbrooke.ca> wrote: > > I am a newbie here and just started using speex in our lab. > > During compiling my voice application with windows-compiled version provided > > today, I am getting "unresolved external symbol _speex_wb_mode". > > I am probably missing some setting with VS6.0 linker... (I am a bit new

Hi, You again include host includes in your build: -I/usr/include You should not do this. -- Regards, Alexander Chemeris. SIPez LLC. SIP VoIP, IM and Presence Consulting http://www.SIPez.com tel: +1 (617) 273-4000

On 12/3/07, Erik de Castro Lopo <mle+la@mega-nerd.com> wrote: > I just checked and there is nothing needed in configure.ac. > > In the Makefile.am that creates the shared library you need to add > "-no-undefined" to the LDFLAGS variable like this: > > libspeex_la_LDFLAGS = -no-undefined @WHATEVER_WAS_THERE_BEFORE@ Which symbols will it export? I think default

On Sat, Nov 1, 2008 at 2:40 PM, Aymeric Moizard <jack at atosc.org> wrote: > The vcproj file provided for 2005 in 1.2rc1 does not include > _USE_SSE when compiling the project for "Release_SSE". This > define is only used when compiling under "Release_Dynamic_SSE". > > Is this just because the vcproj file is wrong or is it because > this #define must not

so, having a speex frame, how do i know where is each sample if i don't know how many bits per sample are being used. Isn't there any info besides the data ? On Wed, Jul 15, 2009 at 7:21 PM, Alexander Chemeris < Alexander.Chemeris at sipez.com> wrote: > Hi, > > Speex RTP payload does not have any header (except RTP header), > as per speex-rtp RFC. > > On Wed, Jul

On 12/13/07, Jean-Marc Valin <jean-marc.valin@usherbrooke.ca> wrote: > Did you test what happens if you only enable arm4 assembly? Sure. I tested with "--enable-arm4-asm" and there was no difference. > Also, if you can do some investigation, it would be useful to check what bit > of assembly is causing the crash. Can you disable one at a time and check? ok. I'll try

Hi Alexander, > Here is first attempt. I'm sending it here for review - am I understand > you correctly? If general approach is correct, I'll change code to use > modes from modes.c. I haven't tested, but it looks sane. Just a few comments: - printf("\tERROR not enough bits left after wb\n"); this is actually now an error. It just means you got to the end of the

On 7/27/07, Ivo Emanuel Gon?alves <justivo@gmail.com> wrote: > On 7/24/07, Arseny Krasutsky <dtiger@mail.ru> wrote: > > So I can send this binaries to you if you want to place it online. > > I'm sure people need it :-) > > I do not know Jean-Marc's position on this -- it's his project, so I > don't want to meddle -- but if he does not oppose, I

IIRC, under ARM, I believe I was having issues with --without-libogg. I resorted to just downloading libogg sources, setting up my cross-compilation environment, and cross compiling it per the general build directions (./configure, make, make install), then went back to building speex -- everything worked like a charm for me then. So -- Conrad. *Make sure* that you have libogg cross-compiled and

Hi, I'm trying to get speex working on an ARM board (ARM926EJ-Sid(wb) core, ARM 5TE architecture) and getting segfaults if build with "--enable-fixed-point --enable-arm5e-asm" options. If I use just "--enable-fixed-point", then it runs fine, but once I add "--enable-arm5e-asm" it start crashing (I use testenc to test it). Further investigation showed, that it

I pulled the test directory from 2003, but everything else from 2005. The 2005 files have more ?cross-compiling? targets than the 2003 ones. I fixed the various missing files in the new 2008 projects (misc.c and one other other are gone now). The only thing you could do which would make them more compact would be to get rid of the subdirectories under each vs-version. There is no real need for

On 12/3/07, Stefan Reuther <streu@gmx.de> wrote: > John Miles wrote: > > What's wrong with a plain old .bat file, or even an NMAKE .mak file? > > Ship two files, debug.bat and release.bat, and call it good. > > > > It is best to leave project-file creation up to individual users, > > in my opinion. > > I second that. When I played around with Speex

For clarity I attached modified testenc.c I used to test my code. On 2/14/08, Jean-Marc Valin <jean-marc.valin@usherbrooke.ca> wrote: > > I also think that having rame_num.c in libspeex, code size could be > > reduced and simplified slightly by using speex_skip_wb_frame() in > > nb_decode() instead of duplicating code. > > Well, the code is a bit different (e.g.