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

Issue metadata

Status: Archived
Last visit 18 days ago
Closed: Nov 2017
NextAction: ----
OS: ----
Pri: 3
Type: Bug

Sign in to add a comment

There is noise when L16+FEC is applied.

Project Member Reported by, Aug 17 2012

Issue description

What steps will reproduce the problem?
1. Start a loopback test with any L16 codec
2. enable FEC on that channel

What is the expected output? What do you see instead?
The audio should be normal. But instead you can hear some intermittent noise(kind of bubble effect).

Please use labels and text to provide additional information.
There is no such noise when testing other codec+FEC or no FEC with L16.
Tested with newest webrtc on Win/Linux

Project Member

Comment 1 by, Aug 17 2012

Labels: -Pri-2 Pri-3
Hi Turaj,

Could you continue to follow up this issue? Set to low priority though.

Comment 2 by, Aug 17 2012

Sure, I'll take a look at it.

Comment 3 by, Aug 13 2014

Labels: Area-SignalProcessing
Project Member

Comment 4 by, Dec 11 2014

Labels: EngTriaged IceBox
Project Member

Comment 5 by, Feb 19 2015

This is a really old thread.

@braveyao, is this still valid? What FEC did you mention from the beginning?
Project Member

Comment 6 by, Feb 25 2015

The FEC mentioned here is the FEC set with API VoECodecImpl::SetFECStatus(), which used to set FEC to all the codecs. 
I see that in latest trunk, now only the codec which has internal FEC could be enabled by this API, otherwise it would return failure. So there is no way to enable FEC to L16 any more. Is this design of new ACM? If so, then I suppose this issue could be closed.
Project Member

Comment 7 by, Oct 5 2016

Components: Audio
Project Member

Comment 8 by, Oct 5 2016

Components: -SignalProcessing
Project Member

Comment 9 by, Nov 7 2017

Status: Archived (was: Assigned)
[Bulk edit] This issue hasn't been modified the last twelve months -> archiving.

If this is still a valid issue that should be open, please reopen again.

Sign in to add a comment