Displaying 20 results from an estimated 1000 matches similar to: "Opus complexity and VOIP for mobile devices"
2015 Mar 04
2
adaptive bandwidth
Thanks Dragos,
I assume I will be setting those parameters during initialization of
encoder right?
Question is, if connection gets too lossy, how will opus adapt to it? Can
it automatically shift bitrate down to minimize impact?
Mark from IRC suggests that the app has to be aware of the losses and
change it on the fly.
Has anybody on the list tried this?
Kelvin Chua
On Wed, Mar 4, 2015 at 5:53
2015 Mar 04
0
adaptive bandwidth
Hi Kelvin,
The audio bandpass setting is only configurable when the encoder is instantiated (eg: start of a Voip call ) , but you can change the bitrate anytime.For example if you can read incoming RTCP packets , you can check if there's reported packet loss , and then lower the bitrate accordingly.Yes, the app has to be aware of the packetloss ?percentage.
Cheers,Dragos
From: Kelvin
2014 Dec 16
1
Estimating bitrate during a real-time voip call
Hi Dragos,
The issue is that not all packet loss maybe congestion related. Often,
reducing bitrate seems to have no impact on improving packet loss.
Thanks,
Manpreet.
On Tue, Dec 16, 2014 at 2:09 AM, Dragos Oancea <droancea at yahoo.com> wrote:
>
> Hi
>
> You can start a VOIP call with 50 kbps bitrate and reduce the bitrate if
> there is packet loss. You know if
2014 Feb 27
1
OPUS_SET_MAX_BANDWIDTH does not have expected results
Hi All.
I am seeing the following unexpected behavior with
OPUS_SET_MAX_BANDWIDTH. I expect that setting this to
OPUS_BANDWIDTH_NARROWBAND would give similar results to passing an 8Khz
sample rate stream, but OPUS_SET_MAX_BANDWIDTH has almost no effect with
any settings.
My test data has 4Khz bandwidth. I am testing the opus encoder (latest
versions) with the following opus_encoder_ctl
2015 Feb 05
2
VOIP: FEC and NARROWBAND
Hello,
Is FEC supposed to work in NARROWBAND mode ?(with maxaveragebitrate=12000; maxplaybackrate=8000 ) ?I am having some confusing results, it appears that FEC is enabled in the encoder, but the decoder cannot find any packet with FEC.
I am also wondering if this piece of code is correct (webrtc):
/* The following is to parse the LBRR flags. */? if (opus_packet_parse(payload,
2015 Feb 06
0
VOIP: FEC and NARROWBAND
At this bitrate the encoder likely decides that it's better to put all
the bits in the normal packet than use FEC. When you enable FEC it
steals a lot of bits from the non-FEC content. Also, the use of FEC
depends on the reported percentage of packet loss. The more loss there
is, the lower the threshold for enabling FEC. Overall, the encoder
attempt to make the best decision on a
2014 Dec 16
0
Estimating bitrate during a real-time voip call
Hi
You can start a VOIP call with 50 kbps bitrate and reduce the bitrate if there is packet loss. ?You know if there's packet loss if you receive RTCP .?Linphone does this .
Regards,Dragos Oancea
From: Manpreet Singh <manpreets7 at gmail.com>
To: opus at xiph.org
Sent: Tuesday, December 16, 2014 7:54 AM
Subject: [opus] Estimating bitrate during a real-time voip call
Hi,
2015 Mar 04
2
adaptive bandwidth
I am using libopus for my implementation. I wonder if anybody in the list
have any experience on how to make libopus dynamically adjust its bitrate?
On Mar 3, 2015 10:42 PM, "Benjamin Schwartz" <benjamin.m.schwartz at gmail.com>
wrote:
> It sounds like your software isn't adjusting the opus bitrate in response
> to network conditions. For example, many WebRTC
2015 Feb 24
2
Questions regarding OPUS_APPLICATION_AUDIO vs OPUS_BANDWIDTH_NARROWBAND
I have an audio device whose 'driver' gives me Opus encoded frames using
OPUS_APPLICATION_AUDIO and max bandwidth set to OPUS_BANDWIDTH_NARROWBAND.
How does Opus encoder decide the center point of the 4K bandpass filter?
Is it done frame by frame?
--
Tony
-------------- next part --------------
An HTML attachment was scrubbed...
URL:
2015 Mar 04
0
adaptive bandwidth
Hi Kelvin,
You can use something like :opus_encoder_ctl(enc,OPUS_SET_BITRATE(bitrate));opus_encoder_ctl(enc,OPUS_SET_MAX_BANDWIDTH(bandpass));
bandpass is the audio bandpass?, eg: OPUS_BANDWIDTH_WIDEBAND .
You will need to calculate the codec bitrate from the available network bitrate (by taking into account the size of the IP+UDP+RTP headers which is 40 bytes ) .
By default the audio bandwidth
2015 Feb 24
0
Questions regarding OPUS_APPLICATION_AUDIO vs OPUS_BANDWIDTH_NARROWBAND
Can you explain what you mean by "center point"?
Jean-Marc
On 24/02/15 11:30 AM, Tony wrote:
> I have an audio device whose 'driver' gives me Opus encoded frames
> using OPUS_APPLICATION_AUDIO and max bandwidth set to
> OPUS_BANDWIDTH_NARROWBAND. How does Opus encoder decide the center
> point of the 4K bandpass filter? Is it done frame by frame?
>
> --
2020 Jun 11
1
OPUS encoded data size and bandwidth of encoder
Hey, I am having trouble with the size of the encoded bytes by Opus. I am
also having issue with the Bandwidth ctl.
Here is the scenario.
If I encode 16khz sampled audio:
opus_encoder_ctl(enc,OPUS_SET_MAX_BANDWIDTH(OPUS_BANDWIDTH_WIDEBAND))
opus_encoder_ctl(enc, OPUS_GET_BANDWIDTH(&x)) = 1102
opus_encoder_ctl(enc, OPUS_GET_MAX_BANDWIDTH(&x)) = 1103
average encoded size = 120 bytes
if I
2016 Jun 13
0
Patches for adding 120 ms encoding
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 =
2016 Jun 27
0
Antw: Re: Patches for adding 120 ms encoding
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;
+
2019 Feb 20
0
Fwd: Custom mode
---------- Forwarded message ---------
From: Peter Svensson <petersvenss85 at gmail.com>
Date: tis 19 feb. 2019 kl 20:43
Subject: Re: [opus] Custom mode
To: Emily Bowman
Hi Emily !
Thank you for responding.
I think my problem is not (yet) with OPUS itself. Encoding at complexity
0 takes 1.6ms ( 4.342ms at complexity 10 !) and decoding takes 1.9ms.
3.5ms, out of my 4.096ms budget, is
2016 Jun 12
2
Patches for adding 120 ms encoding
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
2012 Sep 10
11
Cleanup/build improvement for opus
Hello all,
after FOMS I decided to take a look at the opus library and I found
that I could improve a bit the build system and cleanup the code a
little bit.
Most of the changes to the code has been suggested by my two tools
cowstats and missingstatic (part of the ruby-elf gem if you care).
HTH,
Diego
2016 Jun 28
1
Patches for adding 120 ms encoding
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
2014 Dec 16
3
Estimating bitrate during a real-time voip call
Hi,
Although this maybe considered out of scope here, but I'll ask anyway.
Opus has remarkable flexibility for changing encoder bitrate during a call.
Are there any suggestions about how bandwidth/capacity between the two
endpoints can be measured/estimated during a call so that the outgoing
bitrate can be adjusted accordingly?
Thanks,
Manpreet.
-------------- next part --------------
An
2016 Jun 27
2
Patches for adding 120 ms encoding
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>