New issue
Advanced search Search tips
Note: Color blocks (like or ) mean that a user may not be available. Tooltip shows the reason.

Issue 1181 link

Starred by 32 users

Issue metadata

Status: Started
NextAction: ----
OS: ----
Pri: 3
Type: Enhancement

Show other hotlists

Hotlists containing this issue:

Sign in to add a comment

Use internal PLC in Opus

Reported by, Dec 3 2012

Issue description

Feature description (please include a link to the functional spec):

Opus has an internal PLC that help update the state of the coder in case of packet losses. The function is currently not used in WebRTC, but would enhance quality performance in case of lossy networks.

Project Member

Comment 1 by, Jul 2 2013

Status: Started
Work started on calling the PLC for updating the decoder state.
Project Member

Comment 2 by, Aug 27 2013

Labels: Dev-QAReview-No
Project Member

Comment 3 by, May 13 2014

NetEq3 supported Opus PLC, but NetEq4 don't. Needs to be added to NetEq4.
Project Member

Comment 4 by, Jun 30 2014

Labels: Area-SignalProcessing
Project Member

Comment 5 by, Dec 3 2014

Labels: EngTriaged IceBox Area-Audio
Are we calling Opus PLC in NetEq4 now?
Project Member

Comment 6 by, Dec 3 2014

No, this feature is not implemented yet.
Project Member

Comment 7 by, Oct 5 2016

Components: -SignalProcessing
Project Member

Comment 8 by, Oct 13 2017

Labels: Pri-3
Is this still valid/relevant?
Project Member

Comment 9 by, Oct 13 2017

Yes, it is.
does webrtc use opus PLC instead of expand/merge of neteq now?
Project Member

Comment 11 by, May 31 2018

No, it does not.

This bug is actually about calling the Opus PLC simply to let the decoder know that packets were lost, so that it can recover from the state fault faster.

Comment 12 Deleted

Sign in to add a comment