similar to: Opus 1.0.2 is out

I am specifically using Celt Wideband (48kHz) over WiFi multicast that naturally leads to lost packets and am trying to minimize the impact to the audio. I implemented PLC but the audio it produces is robotic. Have I implemented PLC correctly? Checking the waveform it is using the previous received waveform to fill in a missing packet but not the full waveform so it has to repeat. Basically,

Hi Jean-Marc, Thank you. Yes, we do need both channels independent. So, if we encode each channel separately, we will be sacrificing the compression ratio we would achieve with stereo encoding, correct? So, based on what you say here is my understanding. Please confirm this is correct or not: 1) If we use fec, we can reduce cross-talk but increasing bitrate. However, that should result in

Thank you. Very helpful. > On Jan 27, 2017, at 12:40 PM, Jean-Marc Valin <jmvalin at jmvalin.ca> wrote: > > On 27/01/17 12:29 PM, Jon Lederman wrote: >> Thank you. Yes, we do need both channels independent. So, if we >> encode each channel separately, we will be sacrificing the >> compression ratio we would achieve with stereo encoding, correct? > > Not

On 27/01/17 12:29 PM, Jon Lederman wrote: > Thank you. Yes, we do need both channels independent. So, if we > encode each channel separately, we will be sacrificing the > compression ratio we would achieve with stereo encoding, correct? Not necessarily. Stereo makes two assumptions: 1) It assumes the two channels are somehow correlated 2) It assumes the two channels are meant to be

Hi, One other question I was wondering about. Is the reason that we hear the crosstalk with fec and packet loss percentage>0 is that Opus uses information from the left channel to try to error correct the right channel and vice versa? I am trying to understand the origin of the crosstalk. Thanks. -Jon > On Jan 27, 2017, at 12:29 PM, Jon Lederman <jon at soniccloud.com> wrote: >

On 27/01/17 12:16 PM, Jon Lederman wrote: > When you say that with fec enabled, the threshold is increased, do > you mean the bitrate - i.e., you need higher bitrate with fec enabled > to suppress crosstalk? Correct. Another effect I forgot to mention is that Using FEC will actually force SILK/hybrid rather than CELT, so it's possible that disabling FEC makes you use CELT, which

Thanks for your comments, Ralph and Jean-Marc. Please find attached the amended patch: - decodes a sequence of input packets rather than just one (I'm planning on using the Opus test vectors as the seed corpus) - decides on decoder setup and FEC independently of the packet data - uses Opus functions to parse ToC Cheers, Felicia On Sun, Jan 29, 2017 at 9:48 PM Jean-Marc Valin <jmvalin at

Hi, I just released Opus 1.3-beta. This is a beta release towards the upcoming Opus 1.3. Changes include: - The spec fixes in RFC 8251 are now enabled by default - Improvements to the VAD and speech/music classification using an RNN - Improvements to stereo speech coding at low bitrate - Added support for ambisonics projection using mapping 3 (disabled by default) - Fixes to the CELT PLC

Hi all, I try to enable FEC in the encoder using the macro OPUS_SET_INBAND_FEC and I set the packet loss percentage to a constant value of 30%, using the macro OPUS_SET_PACKET_LOSS_PERC. Please find my encoder settings below: opus: encoder fmtp (maxplaybackrate=8000;maxaveragebitrate=24000;sprop-stereo=1;cbr=1;useinbandfec=1;usedtx=1) opus: encode bw=narrow bitrate=24000 fch=auto vbr=0 fec=1

Hi Felicia, Overall the patch looks good to me and it's a pretty reasonable starting points. Some minor comments below. On 10/02/17 02:44 PM, Felicia Lim wrote: > - decodes a sequence of input packets rather than just one (I'm planning > on using the Opus test vectors as the seed corpus) I remember from experimenting with AFL that it didn't like the test vectors because they

What do you mean by "implement"? You're just using the Opus built-in PLC (passing NULL), right? The PLC generally attempts to find periodicity and replicate it. I guess if your signal isn't periodic it can lead to a repetition that isn't great. It's something that could probably be improved in the PLC. Cheers, Jean-Marc On 08/25/2015 01:21 PM, Scott Boekweg wrote:

Hello everyone, I have been having trouble utilizing the PLC function (I think). In older versions (0.7.1) a pointer to NULL did the trick, but with code from the tip of the GIT repository, this method causes the codec to crash on the C55x fixed point platform. I have not determined where the crash occurs. I have also attempted to pass in an array of zero's and this creates an echoey, reverby

Hi Mark, Jean-Marc, Thanks for your comments. On Sun, Jun 12, 2016 at 6:34 AM Mark Harris <mark.hsj at gmail.com> wrote: > Hi Felicia, > > A few comments: > > > - /* CELT can only support up to 20 ms */ > > subframe_size = st->Fs/50; > > - nb_subframes = frame_size > st->Fs/25 ? 3 : 2; > > + nb_subframes =

1 is the way to use FEC. But: How do I know if this *previous* packet contains FEC information? If not, I want to fallback to invoking PLC for obtaining samples. Or does the decode_fec call automatically use PLC internally as a fallback if FEC is not available? Thanks! --001a113aba02fce1df050d475c7b Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable <div

Hi! A note on style: Looking at this chunk of the patch -- @@ -382,9 +382,15 @@ int main(int argc, char *argv[]) frame_size = sampling_rate/25; else if (strcmp(argv[ args + 1 ], "60")==0) frame_size = 3*sampling_rate/50; + else if (strcmp(argv[ args + 1 ], "80")==0) + frame_size = 4*sampling_rate/50; +

Thanks. When you say that with fec enabled, the threshold is increased, do you mean the bitrate - i.e., you need higher bitrate with fec enabled to suppress crosstalk? Also, can you make any recommendations to decide whether to use fec or not? We are trying to tune the parameters appropriately. Audio quality and reduction of crosstalk are critical for us. Thanks again. Jon Sent from my

Hi Felicia, A few comments: > - /* CELT can only support up to 20 ms */ > subframe_size = st->Fs/50; > - nb_subframes = frame_size > st->Fs/25 ? 3 : 2; > + nb_subframes = frame_size/subframe_size; This will use six 20ms frames to make a 120ms packet, even for SILK-only mode where frames can be up to 60ms. For SILK, two 60ms frames would be a more

Hello, We have a use case where we want to record an opus RTP stream to a .opus file. We want to fill in any gaps in the stream, and we also want to take advantage of inband FEC whenever possible. The ogg/opus draft describes[1] how to fill in gaps by generating zero-byte frames, but I do not understand how (and if) FEC can be used. Is this possible, and if so, what is the recommended way of

Hi Ulrich, thanks for the suggestion. My concern is that one of the valid inputs is "2.5", which would require conversion to an int, e.g. x10, but doing something like this would start to affect the code readability. On Mon, Jun 27, 2016 at 3:02 PM Ulrich Windl < Ulrich.Windl at rz.uni-regensburg.de> wrote: > Hi! > > A note on style: Looking at this chunk of the patch

Attached is the amended second patch. It now extends the multistream API as well to 80/100/120 ms and incorporates changes based on Mark's comments. Thanks, Felicia On Mon, Jun 13, 2016 at 4:21 PM Felicia Lim <flim at google.com> wrote: > Hi Mark, Jean-Marc, > > Thanks for your comments. > > On Sun, Jun 12, 2016 at 6:34 AM Mark Harris <mark.hsj at gmail.com>