similar to: Fixed point modules in floating point

On 11/03/2017 05:48 AM, Vega G wrote: > I was testing floating point  Opus encoder. But it's calling few > functions which are implemented in fixed point . I tried to find > corresponding floating point functions in source. But not available. > Please help me on this. The same code does both fixed-point and floating-point. If you define FIXED_POINT, then the macros and types

I've been browsing around the speex-1.10 source tree. Firstly I see 'float' is still used in many places. Can't we change them all to the appropriate type (spx_wordxx_t or similar) defined in arch.h ? Secondly I see there is a lot of duplication regarding real-valued constants. One way would be to say: #ifndef FIXED_POINT #define CONSTANT(x) (x) #else #define CONSTANT(x)

I've noticed that the nb decoder uses floating point in several places even when using FIXED_POINT. I don't have to deal with lost packets, so I'm mainly interested in innov_gain and pgain in no transmission mode (nb_celp.c around line 1272) and g and exci in vocoder mode (around line 1557). Is there a reason that these places must use floating point, or would it be possible to

Need to adjust scale for floating input. diff -NaurbB a/libspeex/resample.c b/libspeex/resample.c --- a/libspeex/resample.c 2013-12-20 17:40:27.326576921 +0500 +++ b/libspeex/resample.c 2013-12-20 17:40:16.918577087 +0500 @@ -915,7 +915,7 @@ if (in) { for(j=0;j<ichunk;++j) #ifdef FIXED_POINT - x[j+st->filt_len-1]=WORD2INT(in[j*istride_save]); +

Hi Peter, Can you say a little bit more about what you're doing exactly with the information you're exposing and how? unfortunately, I don't have a concrete proposal in mind right now. That's in part because I don't quite understand the use case, but also because it's really hard to expose this kind of information in a way that both avoids breaking application with new

Hi Drew, On 10/10/17 02:29 PM, Drew Allen wrote: > 2) Someone on this list might know better than I do on that one, but for > the new _ctl_va_list() calls, I believe the convention is for va_start() > and va_end() to appear in the caller rather than in in the va_list() > function itself. > > *My understanding is that it's impossible to pass ellipsis to another >

Please compare samples: http://www.ivo.pl/ivo2/sound/krwawa_org.wav http://www.ivo.pl/ivo2/sound/krwawa_fixed.wav http://www.ivo.pl/ivo2/sound/krwawa_float.wav krwawa_org.wav is original file. Both output files was created using same program by compressing from wav to speex, then decompressing from speex to wav (using speex_encode_int and speex_decode_int). Only difference was used speex

Hi Drew, Here's some comments on your patch (in no particular order): 1) I see that it's adding an #include of stdarg.h to opus_multistream.h Is that left over from the previous version? 2) Someone on this list might know better than I do on that one, but for the new _ctl_va_list() calls, I believe the convention is for va_start() and va_end() to appear in the caller rather than in in

Hi Jean-Marc, > Can you confirm I'm understanding everything correctly? You encode > with > the same encoder and then decode with either A) blackfin assembly and > fixed-point or B) fixed-point only on Blackfin. Then A) sounds bad and > B) sounds good. If you do the same in narrowband, it sounds OK. Is > that > correct? If that's the case, it's *probably* some

Hello Jean-Marc, > Could you try mixing the encoders and decoders (encode with one > version, > decode with the other) to see whether the problem is in the > encoder, the > decoder or both. I tested that,and the results are: The fixedpoint+blackfin encoder used together with the fixedpoint-only decoder produces an bad sounding file (for all the combinations for quality

Hi, I found this message concerning VAD and was wondering whether VAD has been ported to fixed-point in the latest version? Thanks, SingHui ---------- Forwarded message ---------- From: Jean-Marc Valin <Jean-Marc.Valin@usherbrooke.ca> Date: Jul 22, 2005 1:02 AM Subject: Re: [Speex-dev] Fixed-point To: gue baja <gue_baja@yahoo.com> Cc: speex-dev@xiph.org Hi Baja, Here's a quick

Hello Daniele It would be worthwhile to attach an external serial flash or USB thumb drive, if the intent is store data. This allows for far more flexibility in storage Regards Amit On Fri, Aug 26, 2016 at 11:02 AM, Jean-Marc Valin <jmvalin at jmvalin.ca> wrote: > On 26/08/16 11:40 AM, Daniele Barzotti wrote: > > You're right! I forgot to say that I need only the encoder

I am setting up dovecot 1.0-rc15 as a proxy. When I try to log in, I get errors such as the following: Dec 4 17:39:23 vega dovecot: Dovecot v1.0.rc15 starting up Dec 4 17:39:24 vega dovecot: auth-worker(default): mysql: Connected to localhost (ad_mail) Dec 4 17:39:31 vega dovecot: auth(default): client in: AUTH 1 PLAINservice=POP3 lip=xx.xx.xx.xx rip=xx.xx.xx.xx

Hi, I have a big big problem. I compiled Samba 3.2.6 for Solaris 8 and 10. Environment is Windows 2003 SFU. So far it looked like everything works as expected. Under Solaris 8 i get all groups of a user. Under Solaris 10 I can only see the primary group set under the Unix Attributes Tab in W2k3. I have compiled with the following settings: ./configure --with-ads --with-krb5=/opt/VEGA

I see there are still some floating point operations left in the codec init(ialization) code. Changing that code to fixed point is not only difficult (due to the trigonometric functions etc) but may also degrade the precision. Here is an idea whereby we can easily precompute (record) all those values on a powerful processor and then use (replay) them on an embedded processor / DSP. The only

Hi Peter, There's two main issues with a patch like the one you're proposing. First, the data is only valid when SILK is being used and is essentially undefined in CELT mode. The second issue is that by exposing internals, it makes it impossible to improve these algorithms since it would break API compatibility. I'm not fundamentally against trying to expose some information, but

Do you receive RDS objects from unknown (untrusted) sources? ?? If not - the security issue is a non-issue as I understand it. On Thu, 16 May 2024, 16:21 Vega, Ann (she/her/hers) via R-help, < r-help at r-project.org> wrote: > I help to coordinate the USEPA's R user group. We have over 500 members > and our security officer has required us to update to R version 4.4.0 >

Hi Jean-Marc, thanks a lot for your reply. > Well, the first question is whether you want encoding, decoding, or > both. If there's one you don't need then you can remove that > (unfortunately, there's no easy way right now). You're right! I forgot to say that I need only the encoder side (and only for voice). My application have to acquire a 16bit 8KHz PCM stream and

Hello, I've just joined the list. I'm interested in helping on the fixed-point version of Speex. If there is anyone currently directing this work, would they please contact me and let me know how I can help. Thanks, -paul -- "Democracy is two wolves and a lamb voting on what to have for lunch. Liberty is a well-armed lamb contesting the vote ... If you make yourselves sheep,

Hello, first of all, sorry for the joke in the subject ;-) I have successfully update the speex library my software was using from 1.1.12 to 1.2beta1 (1.1.13). It is a VoIP software, where i set preprocessor VAD on and use the result of speex_preprocess() to determine if there is voice activity. I must say that it works fine...since i have update to the new version. Ive been testing, and