similar to: opus_celt_inband_fec_mode

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

The -inbandfec option means that the encoder is *allowed* to use FEC, not that it has to. The final decision is based on the bitrate and the percentage of packet loss (and a few minor factors). If you're not seeing a difference, it means that given the options you're using, the encoder thinks actually using FEC would result in worse quality. Cheers, Jean-Marc On 08/05/17 07:11 PM,

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

Dear Opus community, I have a question about the SILK inband FEC. I am using the opus_demo (opus-1.2-alpha) for testing opus codec, and when I choose the "-inbandfec" option I get the exactly the same results when I don't add it to the command line. Are these results logical? Thank you in advance. Best regards, Ayoub. *--------------------BOUZIANE AyoubPhone : (+212) 633 092 157*

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: >

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 =

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

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

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; +

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 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

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

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>

The patch prevents KEIL MDK compile warnings, like:   warning:  #1035-d: single-precision operand implicitly converted to double-precision Actually ARM Cortex-M4F has only a *single precision* (float) FPU. It's suit for all platforms. See the comment at the begin of patch file. Sincerely Forrest Zhang -------------- next part -------------- Specify the floating point constant with single

--- win32/VS2015/opus.vcxproj | 2 ++ win32/VS2015/opus.vcxproj.filters | 6 ++++++ 2 files changed, 8 insertions(+) diff --git a/win32/VS2015/opus.vcxproj b/win32/VS2015/opus.vcxproj index d9aaa03..f55ea37 100644 --- a/win32/VS2015/opus.vcxproj +++ b/win32/VS2015/opus.vcxproj @@ -852,6 +852,7 @@ <ClInclude Include="..\..\celt\vq.h" /> <ClInclude

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

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA256 I believe what you want is called Opus custom (OPUS_CUSTOM in the code). With that you can compile only the contents of the celt/ directory and use it like the old CELT. Jean-Marc On 07/06/2015 06:48 PM, Andrew Lentvorski wrote: > Is there a configuration or compile flag that lets me disable the > SILK portion of the codec and use CELT

I saw the custom API, but nothing explicitly says "CELT-only" just "custom sample rate and frame size". I'll dig further now that you've pointed me in a direction. Thanks, -a On 7/6/15, 6:18 PM, Jean-Marc Valin wrote: > -----BEGIN PGP SIGNED MESSAGE----- > Hash: SHA256 > > I believe what you want is called Opus custom (OPUS_CUSTOM in the > code).

I?m trying to build Opus (git master) for iOS, and it doesn?t build unless I disable the ARM assembly. It looks like the problem is that Apple?s assembler doesn?t support all the assembler directives that the GNU assembler does. I suspect this is a combination of the fact that Apple platforms are Mach-O rather than Elf, and just the fact that Apple?s assembler is extremely divergent from the

Thanks to Jean-Marc and Tim explaining 'git rebase -i' to me, I've factored my reorganization of the Opus Intrinsics configury into a number of hopefully more comprehensible (and thus more reviewable) pieces. This applies to the current tip of Opus Master in git. Viswanath's Ne10 changes require some slight modification to apply on top of these patches, but nothing major.