search for: downshifting

Because a wideband signal has both a narrowband part and a wideband part the first part of the wideband decode is to call the narrowband decode. In the fixed point version the signal generated from the narrowband decode is downshifted at the end. In this same version the wideband then upshifts the signal by the same amount. I would like to do away with the downshift on the narrowband side

Is there a way to tell during the NB decode if it was kicked off by the SB decode? I would like to avoid saturating and packing the output of the NB decode, only to unpack it for the SB. Thanks. -Fritz

This is perhaps a naive question, but what is the recommended manner of testing a helper method in rspec? I have created a simple string manipulation function and I want to write some tests for it. It it were a script then I would just add if __FILE__ == $0 and add the tests below that but I do not feel that this is the best way to handle a rails helper. The code (I said it was simple) :

Great news! yay! I downshifted to dovecot 0.99-14 and pop server is working! Finally a pop-server and postfix and all! And no Courier! or Qmail! Whatever changed in the 1.0 release regarding MySQL is broken, and is working in the .99-14 release. I can finally use my mail server! :-) I'll keep an eye out for the 1.x stable release, hopefully it will have MySQL support working. Maybe

Hi It pretty works for 16 bits samples but not for 24 bits samples. In fact, I am going to implement opus on ADSP-21489 (DSP processor from Analog Devices), I compiled "celt directory" from opus 1.1 and used "opus_custom_demo.c". It hasn't any problem with 16 bits samples but when I use 24 bits samples , there is no output audio. opus_decoder will still generate 16 bits

...there to work with it. Go read the code in client.c and tune it to your fit your needs ;-) Ive said it before and ill say it again Icecast Rocks!!!! -- Venlig hilsen/Kind regards Thomas Kirk ARKENA thomas(at)arkena(dot)com http://www.arkena.com <p>BOFH excuse #287: Telecommunications is downshifting. --- >8 ---- List archives: http://www.xiph.org/archives/ icecast project homepage: http://www.icecast.org/ To unsubscribe from this list, send a message to 'icecast-request@xiph.org' containing only the word 'unsubscribe' in the body. No subject is needed. Unsubscribe message...

I made yet another new wiki page documenting the mail configuration file. Looks really nice. We can all start working on improving the docs in this file and eventually merge the docs here back into the example config file. http://wiki.dovecot.org/moin.cgi/MainConfig -- Marc Perkel - marc at perkel.com Spam Filter: http://www.junkemailfilter.com My Blog: http://marc.perkel.com

Hi Linfeng, On 15/02/17 04:05 PM, Linfeng Zhang wrote: > The original celt_fir() is a little bit messy. It has 2 branches chosen > by #ifdef SMALL_FOOTPRINT. Yeah, I agree that the #ifdef SMALL_FOOTPRINT in celt_fir() is a bit of overkill since it's not saving much code space. I just pushed a commit that gets rid of it, also refactoring the #else case a bit (see below). > For

was: [icecast] what's happening here? <p>The list doesn't seem any more stagnant than the website ;-) Seriously, the lack of current news on the website must have a turning-away effect for curious folks checking www.iccast.org out. There's a recent post from 18 days ago, but there was a "no news" dry spell between August 7 2001 and April 10 2002! During this time I

Hi Jean-Marc, The original celt_fir() is a little bit messy. It has 2 branches chosen by #ifdef SMALL_FOOTPRINT. For floating-point, the 2 branches are identical (except the operation sequence of accumulating x[i] to sum, which is not a big deal). For fixed-point, the 2 branches are different. I separate them into 2 functions: the new celt_fir(), and celt_fir_permit_overflow() which is the

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Hi. I'm getting the following error at random intervals on my TE410P with Asterisk CVS-03/30/04-11:49:01-CEST. I have two spans active, one connected to my Telco, the other to a Siemens PABX. Both spans display this behavior at random intervals. All calls are dropped when this happens. Spans are not necessarily in use when this happens.