similar to: Packet loss concealment and G729

Hi, I am an engineering student in IIT Guwahati, India. Currently, as a summer project I am working on 'packet loss concealment in voip scenario'. I am eager to know what PLC methods are used at receiver end of speex decoder. And if I could develop some more efficient method I could able to contribute to the speex. Actually, I searched the whole speex manual but failed to find what

Hi all, I am developing a VoIP application and have used SPEEX for that purpose; I successfully managed to port the codec in fixed-point to an ADSP-21364 processor, and the codec works fine in narrowband, wideband and ultra-wideband mode. Currently, I have chosen, in accordance with the speex manual, a 20 ms frame size in each of these modes: in other words, the input buffer for speex was set to

Hi, I would like to know which method uses Speex to conceal the loss of packets. I've reviewed the code and haven't found anything. Thanks in advance. Iago Soto. -------------- next part -------------- An HTML attachment was scrubbed... URL: http://westfish.xiph.org/pipermail/speex-dev/attachments/20040614/bfa135e0/attachment.htm

Hello I've been using VoIP over a not so reliable net: I usually get a 5% to 10% packet loss and a very high jitter. I tried several codecs and parameters, and the only thing left to test is PLC (Packet Loss Cancellement). Have the astesrisk and digium people implemented PLC?, Are they implmementing it now? and, if not, Where can i find an implementation? Thanks in advance -- Jorge

Hi, I'm a developer currently using the speex codec in a VOIP application of ours.. It sounds amazing, especially at wideband.. my question is how do I force it to do a concealment? We have a low latency application, and based on the current API, I'm guessing concealment only kicks in when a packet is lost.. However, our jitter buffer knows when a packet is missing, and I'd like to

Thanks for the reply. I think I'm beginning to understand but can you clarify a bit more. 1) I am confused on "trade error-free quality" part. Basically the encoder is doing something to the encoded data by looking at the SPEEX_SET_PLC_TUNING parameter? 2) How does the receiver side determine whether the packet loss occured or not? It seems only way is assigning

hi, i'd like to ask for a suggestion for implementing PLC (packet lost concealment). right now, i don't have PLC applied in my application. when voice data arrive from the network, i just play it right away. does having PLC require that you play something every interval? like if im expecting a voice packet say every 20ms, then i play something at that rate. either the packet that came

Hi, I've try to enable the new loss concealment code with celt-0.6.1. I've run "configure --enable-new-plc" but I've got a missing plc.c file while compiling. It is also missing for version 0.6.0. Can you release this missing file? Thank you, Pascal CRC

Hi,I want to know how to do to work PLC of Asterisk. Anyone plz help me. PLC (Packet Loss Concealment) is included in Asterisk,I read at voip-info.org or release note. And I see in codecs.conf, "genelicplc" setting. So I put codecs.conf in '/etc/asterisk' ,and wrote "genericplc => true". And I worked Asterisk and tested. I think PLC like this. When I send 3

Hi, I have read the mailing list archives and have a question regarding PLC (packet loss concealment).

Hi everyone, I'd like to announce CELT 0.7.1, which improves the quality of the packet loss concealment (PLC), but does not change the rest of the codec. For this reason it is the first release NOT to break bit-stream compatibility with the previous release (0.7.0). But I promise not to do it again, the next CELT release will likely break compatibility once again. Note that the PLC

Hi I get an error popping up when the call ends as follows: DBD::mysql::db do failed: Unknown column 'callstart' in 'field list' at /var/lib/asterisk/agi-bin/astcc.agi line 90, <STDIN> line 32. Does anyone else get this same thing? Looks as if my database table is wrong, or something else is up...not sure Thanks Clive

> Ok, what you suggest sound logical to me. Currently, I > have done a small trick to prevent this problem. What > I did is that whenever windows request a voice packet > from me and if I do not have the voice packet, I > repeat the previous packet. Hence, all the breaking > portion is filled with previous packet. This trick > seems to work so far. I am not sure what is the

Hi everyone, I'm happy to announce that Opus 1.5 has just been released. Opus 1.5 is the first release to make extended use of ML in the encoder and decoder. You can read all the details in our demo page at: https://opus-codec.org/demo/opus-1.5/ Major changes since 1.4 include: - Significant improvement to packet loss robustness using Deep Redundancy (DRED) - Improved packet loss

I've been working on improving packet loss concealment in my VoIP client -- I hadn't actually realized speex performed some PLC until I was looking at nb_decode(). There are two things I'd like to do, and I think both will require some modification to nb_decode() and nb_decode_lost(). - I'd like to have my frames overlap by some number of samples. This is intended to reduce the

I've been working on improving packet loss concealment in my VoIP client -- I hadn't actually realized speex performed some PLC until I was looking at nb_decode(). There are two things I'd like to do, and I think both will require some modification to nb_decode() and nb_decode_lost(). - I'd like to have my frames overlap by some number of samples. This is intended to reduce the

Hi Jean, > Actually, Speex has Packet Loss Concealment (PLC) > builtin. If a packet > is missing, instead of repeating the previous one, > just try decoding by > passing NULL instead of the SpeexBits struct. > Thanks, I have made the above changes and the effect seems to be better now. > > I think jitter buffering is more correct way to > solve > > this problem

And it turns out there was a missing meson file in the original release so here's 1.5.1 with the file added: https://downloads.xiph.org/releases/opus/opus-1.5.1.tar.gz Cheers, Jean-Marc On 2024-03-04 11:26, Jean-Marc Valin wrote: > Hi everyone, > > I'm happy to announce that Opus 1.5 has just been released. Opus 1.5 is > the first release to make extended use of ML in

Hi, We are planning to use Speex as the speech codec for a VoIP application. 1) May I know how Speex compared with GIPS codec? It seems that Google, Yahoo, and Skype are licensing from GIPS. Are there any good benchmarking or fair comparisons? 2) In particular, how is the jitter buffer control for Speex in response to intermitent poor connection hiccups? Is it robust enough to smooth out

FYI, the README file section on building for Windows says to see the README.md files in the cmake or meson subdirectories, but there are no README files in either of those subdirectories. -----Original Message----- From: opus <opus-bounces at xiph.org> On Behalf Of Jean-Marc Valin Sent: Monday, March 4, 2024 12:52 PM To: opus at xiph.org Subject: Re: [opus] Opus 1.5 is out -- now with ML