search for: 96db

...the qualify_frequency as you suggested and it does appear that I have something configured incorrectly?. <--- Transmitting SIP request (483 bytes) to UDP:0.0.19.196:5060 ---> OPTIONS sip:64.2.142.93 at 5060 SIP/2.0 Via: SIP/2.0/UDP xxx.xxx.xx.xxx:5060;rport;branch=z9hG4bKPjcea63914-b8d1-483d-96db-11968abab704 From: <sip:e31d5809-f26a-4219-8365-70931428072b at xxx.xxx.xx.xxx>;tag=7cfab3ba-73de-4243-9967-d1e6a5e7b0b4 To: <sip:64.2.142.93 at 5060> Contact: <sip:e31d5809-f26a-4219-8365-70931428072b at xxx.xxx.xx.xxx:5060> Call-ID: 7ba766bf-363b-47d0-a388-62a58d1df88d CSeq: 337...

...ny point. I have now replaced all steps up to including the estimation of the LPC filter coefficients with integer code. That is about a quarter of the total work completed, I would say. One problem that i encountered is the high dynamic range of the results of the autocorrelation function. Think 96db squared. -> 192 dB ;) That is not very desirable when used as input for further processing. I have most precision issues pretty well under control until before I enter the Levinson Durbin algorithm. The Levinson Durbin routine is where things go bad. I am currently losing 2 dB of SNR when I app...

...st (483 bytes) to UDP:0.0.19.196:5060 ---> > Well, THAT's not right. Did you obfuscate the 0.0.19.196 or is that how it really is? Are you NATed? > OPTIONS sip:64.2.142.93 at 5060 SIP/2.0 > > Via: SIP/2.0/UDP > xxx.xxx.xx.xxx:5060;rport;branch=z9hG4bKPjcea63914-b8d1-483d-96db-11968abab704 > > From: <sip:e31d5809-f26a-4219-8365-70931428072b at xxx.xxx.xx.xxx > >;tag=7cfab3ba-73de-4243-9967-d1e6a5e7b0b4 > > To: <sip:64.2.142.93 at 5060> > > Contact: <sip:e31d5809-f26a-4219-8365-70931428072b at xxx.xxx.xx.xxx:5060> > > Call-ID:...

...y __int64 or long long datatypes at any point. If possible, it would be nice to restrict ourselves to 32x32->64 multiplies, so the code could run on almost any architecture. > One problem that i encountered is the high dynamic range of the > results of the autocorrelation function. Think 96db squared. > -> 192 dB ;) That is not very desirable when used as input for > further processing. One thing to note here is that it is only the "relative values" that count for the auto-correlation. That is, you can normalize it by autocor[0] and get the same results. That should...

...end an email to rubyonrails-talk+unsubscribe-/JYPxA39Uh5TLH3MbocFF+G/Ez6ZCGd0@public.gmane.org To post to this group, send email to rubyonrails-talk-/JYPxA39Uh5TLH3MbocFF+G/Ez6ZCGd0@public.gmane.org To view this discussion on the web visit https://groups.google.com/d/msgid/rubyonrails-talk/6022fac4-96db-40d5-8364-9ebbc72411ae%40googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.

...laced all steps up to including the estimation of > the LPC filter coefficients with integer code. That is about a > quarter of the total work completed, I would say. > > One problem that i encountered is the high dynamic range of the > results of the autocorrelation function. Think 96db squared. > -> 192 dB ;) That is not very desirable when used as input for > further processing. > > I have most precision issues pretty well under control until before > I enter the Levinson Durbin algorithm. The Levinson Durbin routine > is where things go bad. I am currently...

Hi, I think that it would be a good thing to know more about those 2 projects (and also the future patent free format). I think that many people as me know about Lame, but not about Vorbis, and vice-versa. It would be fine that someone (perhaps the maintainer) of every project would introduce to both group of people those projects. 2 things would be interesting (to my mind): - to know about the

Not sure why, but Vitelity changed the settings to IP based authentication on me. Here's the new sip.conf settings they sent me. type=friend dtmfmode=auto host=64.2.142.93 allow=all nat=yes canreinvite=no trustrpid=yes sendrpid=yes When I use these settings to originate calls using the sip.conf they sent me, everything works. Action: Originate ActionID: S8 Channel: