similar to: Another release: Valin 3.0 is out!

Hi everyone, I'm pleased to announce the new and improved Valin 2.0, codename "Alexandre", released March 7th, featuring: - 6 lbs (2.7 kg) at birth - Pretty face - Built-in crying algorithm Screenshots are available at http://people.xiph.org/~jm/alexandre/ . Note that this new release is not open-source and only has two "users". Both co-authors are fine, but tired at

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

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

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.

>> Oh, your table looked fine. I think it's mine that was wrong for the >> "null mode" (which nobody ever uses I guess!). > > I'm not sure, but I guess it may be used in VBR or DTX mode? > At least that's why I kept it. Of course it *can* be used (and needs fixing). It just seems few people did :-) > So, what's the next step towards

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, Is there any way to determine frame size in bits or bytes of encoded frame in WB mode for given quality? That is I need to know how many bits encoded frame will occupy in RTP packet. I see SPEEX_SUBMODE_BITS_PER_FRAME request, but it works like this only for NB mode, and for WB mode it return size of WB "subframe" (?) only. -- Regards, Alexander Chemeris. SIPez LLC. SIP VoIP, IM

----- Original Message ----- From: "Conrad Parker" <conrad at metadecks.org> To: "Vincent Burel" <vincent.burel at vb-audio.com> Cc: "Jean-Marc Valin" <jean-marc.valin at usherbrooke.ca>; <speex-dev at xiph.org> Sent: Thursday, November 13, 2008 1:18 AM Subject: Re: [Speex-dev] SPEEX on iPhone ? > 2008/11/13 Vincent Burel

Alexander Chemeris wrote: > Hi, > > On 5/27/08, Thorvald Natvig <thorvald at natvig.com> wrote: > >> And here's a patch for Intel Math Kernel Library. This allows commercial >> users of Speex to use a high-speed FFT library that isn't GPL'd. (You do >> need to pay for it though). This is 3 times faster than the default FFT in >> speex, and

Hi Jean-Marc

Hi all, 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 to windows too) If anyone could point it out, I would appreciate it. - Tim -----Original Message-----

Skipped content of type multipart/alternative-------------- next part -------------- A non-text attachment was scrubbed... Name: speex_vs2008.diff Type: application/octet-stream Size: 165590 bytes Desc: speex_vs2008.diff Url : http://lists.xiph.org/pipermail/speex-dev/attachments/20071127/08917736/speex_vs2008-0001.obj

CONGRATULATIONS!!!!!! :-D That's really great.... a question, does the built-in crying algorithm work properly with the de-noiser? i found that sometimes late at night (2 a.m. usually) they start to make really strange noises, someone on this thread suggested that resetting the state with a call to mother_breast_feeding() works but i haven't got it to work.... LOL..... Cheers....

Alexander Chemeris a ?crit : > Hi Jean-Marc, > Is your proposition that ever this code will be written in terms > of internal Speex bits it will be included into libspeex still in force? yes. I'd like to include that if someone writes it using SpeexBits. Cheers, Jean-Marc

Alexander Chemeris wrote: > On 2/16/08, Jean-Marc Valin <jean-marc.valin@usherbrooke.ca> wrote: >>> 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. >

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

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

Jean-Marc Valin 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 don't practice "release early, release

David Hogan a ?crit : > That said, we don't use the supplied project. We simply compile in > the speex .c files. You could easily replace the Win32 build files > with a readme showing which .c files NOT include in your project > file. > > If you'd like, I'd be happy to produce a readme file on how to make a > VC project file for speex. Although this approach would

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