similar to: Speex mailing list migrating to xiph.org

Hello I'm working about audio and video codecs. I'm making a research about the state-of-the-art in coding technologies. My question is about the speex codec 1.0. I would like to know the name of the algorithms that it uses.(LPC,CELP..). It uses more or less the same algorithm for narrowband and wideband? Finally i would like to ask about future codec developement projects. Thanks

Hi, I have recently been receiving the following errors when using rsync to update my centos local repositories; rsync: send_files failed to open "/7/atomic/x86_64/repo/tmp/tmp.HBjcIF" (in centos): Permission denied (13) rsync: send_files failed to open "/7/atomic/x86_64/repo/tmp/tmp.SWIH0I" (in centos): Permission denied (13) I have checked and the user that runs the

See my latest photos, updates and friends on Bebo. Click to view my profile. http://www.bebo.com/in/8704684199a654704098b135 ...................................................................... This email was sent to you at the direct request of Silvia Pfeiffer <silviapfeiffer1 at gmail.com>. You have not been added to a mailing list. If you would prefer not to receive invitations

Hi, just to let you know that unstable version 1.1.1 is out. It includes the latest fixed-point changes which can be enabled with --enable-fixed-point (as configure option) or -DENABLE_FIXED_POINT (for win32). The port is not complete, but most of the floating-point operations have been converted. Please give it a try and report any difference with previous versions (both for float and

Hello, Our CentOS public mirror synchronization is failing since yesterday, with the log files showing the following "Permission denied" messages. It seems that my server is not able to access some of the files; any leads on to how to resolve it? rsync: send_files failed to open "/7.4.1708/atomic/x86_64/repo/tmp/tmp.3PYmPD" (in centos): Permission denied (13) rsync:

> Am I right with the assumption, that currently you have to enable > processor specific optimizations with compile/configure options? > > How difficult would it be to add support for runtime CPU detection? > Is this a feature you might consider adding? Pretty complicated because of some annoying decisions taken by the gcc team. The problem is that gcc won't let you use

Hello! The question is: "Does Speex support multiple channels?" Speex is reported to encode only mono and stereo signals. But I found 'nb_channel' defined in <speex_header.h> among the Public Attributes. Does this mean that it is also possible to store more than two channels in one single speex-file? Maybe it will be possible in the next future...? TIA -- Mch --- >8

Hi everyone, I'm glad to announce officially that Speex has joined the Xiph.org foundation (the ones behind Vorbis). The new web page is located at www.speex.org and the code is now licensed under Xiph's BSD-like license. As you noticed, the mailing list is now speex-dev@xiph.org I'd also like to announce the release of the first beta for the upcoming 1.0 release. The API and

> Is it a problem if all the files are compiled with -march=pentium3 > ? The patch that we sent in already detects in the configure.in script > which system you are on and sets a define correctly, i.e. _USE_SSE. Well, if what you want is auto-detection, turning on -march=pentium3 means that the code will crash on anything lower than a pentium3. Not really useful. Of course,

Le mar 18/11/2003 à 17:39, Allen Drennan a écrit : > Speaking of video conferencing in conjunction with Speex, we are > currently beta testing a solution we developed that offers multi-point, > multi-party video and audio using the Speex engine for voice. > > http://www.wiredred.com/downloads/ecsetup.exe > > The fair and good audio settings are Speex narrowband, high quality

This portion of the RFC is gramatically incorrect and confusing: The RTP payload MUST be padded to provide an integer number of octets as the payload length. These padding bits MUST be all zero. This padding is only required for the last frame in the packet, and only to ensure the packet contents ends on an octet boundary. <p> -- Ben Greear <greearb@candelatech.com>

Hi, I'm about finished developing a QuickTime component that supports Speex (on MacOS X and Windows).. As it is now the user can set complexity (SPEEX_SET_COMPLEXITY) and quality (SPEEX_SET_QUALITY / SPEEX_SET_VBR_QUALITY) and to wether to use VBR or not. Will these options make it possible to produce all combinations of bitrates/qualities? Or should I also use

Hi, Speex is getting close to beta4, which I'd like to be feature-complete (or as close as possible). That's why I'd like to ask if anyone here has needs for a feature that hasn't been implemented yet. If so, please let me know. For those interested, here's what's going to be in beta4. First, the VBR code has been greatly improved and now works good with wideband too.

Hi, I am working with libspeex api. I would like compare the size of speex file encoded with libspeex and the size of speex file encoded with speexenc. For example, I encode with speexenc (narrowband, quality 1) a wav file of 1.43 MB (17 seconds) output a spx file weight 21KB, for other hand I encode with libspeex the same wav file with same characteristics in arm processor, pocket pc and the

FYI, the Asterisk software PBX <http://www.asterisk.org/> has now incorporated my recent patches to support dynamic RTP payload types. As a consequence, its SIP implementation now supports Speex, so if you have a Speex-compatible SIP client, you can use it to make calls using Asterisk. Some caveats: - Only narrowband (8 kHz) Speex is currently supported; not wideband. (Unfortunately,

Hmm, what these instructions do? (I know nothing about ARMs; I have some knowlege about x86 assemblers and programming). Cant we use pure standard C++ or Java? Does Speex work with fixedpoint math? (As far as I know Java on 6600 has no builtin floatingpoint, there is emulation class somewhere on the net, but it is probably painfully slow.) I do not know if this processor has builtin

Hi everyone, I've just released version 1.1.4. This includes some code cleanup and improvements to the fixed-point port and SSE optimizations. All the SSE code has been converted to intrinsics and some new functions have been implemented with SSE. Overall, the speed has been increased by up to ~30% with SSE. Jean-Marc -- Jean-Marc Valin, M.Sc.A., ing. jr. LABORIUS

At 07:55 PM 3/11/03, Jean-Marc Valin wrote: > > - Only narrowband (8 kHz) Speex is currently supported; not > > wideband. (Unfortunately, the assumption that audio sample rate == 8 kHz > > is riddled throughout the Asterisk code.) > >Perhaps it's still possible to send wideband, while telling Asterisk >it's narrowband (the bit-stream is such that you can decode

Hi, Speex is progressing and I've started thinking about the next 1.2 release (don't hold your breath). Though the bit-stream won't change, the API likely will. The API for 1.1.x already differs from 1.0.x because the speex_encode and speex_decode now use shorts instead of floats. Now, since I'm changing the API anyway, I thought I might as well fix things that might be annoying

> Date: Fri, 05 Dec 2003 13:22:53 -0500 > From: Jean-Marc Valin <Jean-Marc.Valin@USherbrooke.ca> > > I think I see what you mean, though I haven't been able to listen to > your wma file (not everyone has a wma decoder). The problem probably > only lies in the VBR tuning for wideband which hasn't received much work > yet. One way to check that is to encode in