search for: 32767.0

Hi list, I'm trying to figure out how to do the most compatible implementation that will work with as many versions of Speex as possible. I am streaming multi frame Speex blocks over a TCP connection which works fine as long as the version of Speex is the same on both sides. When using a newer Speex (1.1.?) to encode and an older version to decode (1.0.5), it does not work. The encoder

> 16 bit ints have a range of -32768 to 32767. If you divide > -32768 by 32767.0 you end up with -1.00003051850948 which > is a bad thing. > > Try normalizing with a value of 32768.0. No. Speex expects values in the +-32767 range, not +-1.0. Just converting from int16 to float *is* the right thing to do. Jean-Marc -- Jean-Marc Valin <Jean-Marc.Valin@USherbrooke.ca>

On Saturday 10 April 2010 21.51.55 Jean-Marc Valin wrote: > All version after 1.0 are compatible with each other and with 1.0. Hi Jean-Marc and thanks for the quick reply. I have now looked at this further and got the idea to hard code the number of frames in the decoder temporarily as a test and voil?, it works! The problem seem to be some incompatibility in the termination handling. After

Dear all, I have one simple question. I understand that speex_encode and speex_decode takes float * as an arguement to encode and decode the sound. However, when I get the PCM data from the sound card under win32, it is a just 16 bit array. May I know how do I convert this 16 bit value to speex float format and to convert back? Is there got any routine to do this? YueWeng

Dear all, First, my aim is to achieve VoIP using VBR and DTX under Win32. I face a problem using speex 1.0.4 and need some help. My voice is ok and no background noise when I do NOT normalize 16 bit value to floating value. Normalized means dividing the 16 bit value by 32767. Turning on VBR is also ok but DTX has no effect. However, the speak is has a continous background beep sound AFTER I

All version after 1.0 are compatible with each other and with 1.0. Jean-Marc On 2010-04-10 15:44, Tobias wrote: > Hi list, > > I'm trying to figure out how to do the most compatible implementation that will > work with as many versions of Speex as possible. I am streaming multi frame > Speex blocks over a TCP connection which works fine as long as the version of > Speex is

The main difference is not that much in the bit-stream but in the API. In earlier versions you had to append the terminator manually, whereas I modifed later versions to do it automatically in case programmers forgot (there was no reason not to do so). Jean-Marc On 2010-04-11 05:23, Tobias wrote: > On Saturday 10 April 2010 21.51.55 Jean-Marc Valin wrote: >> All version after 1.0

Hmmm... sorry i mislead you Tay... i didn't realise my encoder (libfishsound) was again shifting the data i gave it back to being 32767 based internally. Zen. ----- Original Message ----- From: "Jean-Marc Valin" <Jean-Marc.Valin@USherbrooke.ca> To: "Tay YueWeng" <yueweng@yahoo.com> Cc: "speex" <speex-dev@xiph.org> Sent: Wednesday, December

This issue I am encountering seems to only happen on multi-socket machines. It also does not help that the only multi-socket box I have is an Romley-EP (so two socket SandyBridge CPUs). The other SandyBridge boxes I''ve (one socket) are not showing this. Granted they are also a different model (42). The problem is that when I run ''perf top'' within an SMP PVHVM guest,