similar to: 4kbps sounds robotic on TMS320C64

Tried your fixed_generic.h change but that didn't help. Andy ----- Original Message ---- From: Andy Ngo <ndno72-speex@yahoo.com> To: Jean-Marc Valin <jean-marc.valin@usherbrooke.ca> Cc: speex-dev@xiph.org Sent: Wednesday, December 12, 2007 4:13:35 PM Subject: Re: [Speex-dev] 4kbps sounds robotic on TMS320C64 Jean-Marc, Yes, fixed-point is enabled (#define FIXED_POINT in

Hi, I'm currently working on the TI DaVinci processor, which has an ARM926 processor and a TMS320C64+ DSP in it. I have been using Speex 6kbps (narrowband, quality=2, complexity=1, perceptual_enh=0) on the DSP C64+ side without any issues; the voice sounds very good for such a low bandwidth requirement. However, recently, I tried out the 4kbps mode (changing quality to 1) on the DSP and it

Sorry everyone, but I figured it out; it's working now. The problem was in my monoToStereo and stereoToMono functions (the Linux OSS driver on the ARM side only supports stereo so I had to convert it to mono before feeding it to Speex); also I had an alignment issue with my buffers I was using on the DSP side. Thanks Jim/Jean-Marc for your help! Regards, Andy ----- Original Message ----

Hi Jean-Marc, I have tested Speex in fixed-point mode on my PC without clicking noise. As I mentioned below, I tested Speex in fixed-point mode running natively on the ARM side of the DaVinci without click noise. I only get the clicking noise when running Speex on the DSP side. For the TI C64+ DSP on the DaVinci processor, the TI-specific switches doesn't do much other than defining the

Hi, I've been trying to get Speex to compile and run on the DSP of TI's new DaVinci System-On-Chip processor, which has both an ARM (ARM926) and a DSP (C64+, based on the C6400). I used the latest code (1.2beta) and followed the example in the speex- 1.2beta1/ti/speex_C64_test trunk to build the Speex library for the DSP. Basically I have a loopback application on the ARM that samples

What do you mean by "implement"? You're just using the Opus built-in PLC (passing NULL), right? The PLC generally attempts to find periodicity and replicate it. I guess if your signal isn't periodic it can lead to a repetition that isn't great. It's something that could probably be improved in the PLC. Cheers, Jean-Marc On 08/25/2015 01:21 PM, Scott Boekweg wrote:

I am specifically using Celt Wideband (48kHz) over WiFi multicast that naturally leads to lost packets and am trying to minimize the impact to the audio. I implemented PLC but the audio it produces is robotic. Have I implemented PLC correctly? Checking the waveform it is using the previous received waveform to fill in a missing packet but not the full waveform so it has to repeat. Basically,

We have an application that plays a variety of sound files on one leg of a call (generated by a call file). We've been told that the party listening to the audio files intermittantly hears "robotic" sounding audio (on/off during the same call). Anyone have ideas on cause? These calls are on an internal network (lots of network bandwidth), and from a server running 99% idle.

Hello, in celt/celt_encoder.c line 369, the 'b' argument to MAX16 can sometimes be greater than what can be represented by a 16bit integer. The default definition of MAX16 is type-less, but I am working on an architecture with hardware support for min/max of 16bit. Changing the default definition to take advantage of this hardware changes the result of that computation. Please consider

Hi everyone, I'm trying to encode/decode with speex, when I do not, the audio is loud and clear, but when I encode/decode to test audio quality, I get a really poor audio quality and a robotic sound. Here's my init audio method : #define AUDIO_QUALITY 10 - (void) initAudio { try { //SPEEX CONFIG speex_bits_init(&bits_in);

Hi, I am trying to natively compile LLVM on a ARM virtual machine ( which I am running through QEMU) but getting the error as mentioned in previous mail. VM is running ARM926 which according to ARM architecture, has vfp support. Do some changes need to me made in LLVM distribution to make it run on ARM platforms Thanks --Kapil On Fri, Sep 25, 2009 at 5:16 AM, Xerxes Rånby <xerxes at

>> I was wrong, it is the encoder that is not working, and it stopped >> working >> in build 11103. The log message for this build is "another 640 bytes >> removed from the encoder state (using the input data instead of copying >> it >> to st->frame/st->inBuf)". Only nb_celp.c/h are changed in this build. >> What >> I am seeing

.. And a version without the API changes. -------------- next part -------------- Index: libspeex/resample_sse.h =================================================================== --- libspeex/resample_sse.h (revision 0) +++ libspeex/resample_sse.h (revision 0) @@ -0,0 +1,128 @@ +/* Copyright (C) 2002-2008 Jean-Marc Valin + * Copyright (C) 2008 Thorvald Natvig + */ +/** + @file resample_sse.h +

Hi, Here's the (hopefully) final version of the resampler, now always using st->mem as the buffer area. It only allocates buffers on the stack when it's necesarry to convert the output between int and float. -------------- next part -------------- Index: include/speex/speex_resampler.h =================================================================== ---

Hi, I am using 1.2beta2 on a C5416 doing narrowband in the decode function I am having a problem with the execution of my program vectoring off to random interrupts that are not used. I have tracked down the error to the highpass function called in nb_decode -very close to the end of the function-context: it is called here: ln 1719 for me if (st->highpass_enabled) highpass(out,

Hello, I've just caught a strange crash in speex_echo_state_init routine. It happened only on one WinXP machine, while on others using XP, Vista and 7 everything is fine. Crash occures in mdf.c line 434: st->spec_average = DIV32_16(SHL32(EXTEND32(st->frame_size), 15), st->sampling_rate); Got any ideas or should I provide more information of the OS? Thanks a lot!

> I was wrong, it is the encoder that is not working, and it stopped working > in build 11103. The log message for this build is "another 640 bytes > removed from the encoder state (using the input data instead of copying it > to st->frame/st->inBuf)". Only nb_celp.c/h are changed in this build. What > I am seeing out of the decoder is an extremely low signal

Hi, My company just recently bought a TI DaVinci development board and I'm trying to port Speex to run on it. The TI DaVinci chip has an ARM926 processor and a TMS320C64+ DSP in it. I was able to get Speex somewhat working on a TMS320VC5510 about a year ago but I was wondering is there anything special I need to do to get Speex working on the TMS320C64+ DSP in the DaVinci chip. I

Hello everybody, I'm working on implementing the speex codec on ARM966E @ 96Mhz. For the encoding I found that 20ms of sample voice takes 13ms to be encoded. The goal of my project is to built an VoIP application based on ARM966E but with the actually performance it's not possible :( My question is what is approximately the speex encoding time with narrowband mode on ARM9 (ARM926 or

7. Take an Asterisk training course and become a dCAP. As for "we have try to solve it but we're lack of asterisk knowledge" - would you get a plumber to service your car? Why not employ (as in 'pay money') somebody to investigate this further. As Satish pointed out - QoS type issues take a lot of debugging and that usually has to be done on-site. BTW - I doubt any of