Open Bug 1043521 Opened 10 years ago Updated 2 years ago

Set/respect Opus fmtp parameters

Categories

(Core :: WebRTC: Signaling, defect, P4)

Product:
Core
Component:
WebRTC: Signaling
Platform:
x86_64
Linux
Type:
defect

Tracking

()

Blocking Flags:
backlog webrtc/webaudio+

People

(Reporter: derf, Unassigned)

References

(Depends on 2 open bugs)

Details

Currently we provide no fmtp parameters in SDP we generate, and ignore all fmtp parameters sent to us.

We should set the sprop-* fmtp parameters for Opus properly based on the streams we are sending, and honor the requests in receiver fmtp parameters as much as possible.

The current draft specification for the fmtp parameters is in <http://tools.ietf.org/html/draft-ietf-payload-rtp-opus>.

This is a meta bug. I will file specific bugs for each of the individual pieces.
Depends on: 1043536
Depends on: 1043543
Even worse, the MediaPipelineReceiveAudio object scales down the playout audio stream to 16000 Hz and mono regardless of the number of channels or the decoder's sampling frequency.
backlog: --- → webRTC+
Rank: 38
Priority: -- → P3
Mass change P3->P4 to align with new Mozilla triage process.
Priority: P3 → P4
Severity: normal → S3
You need to log in before you can comment on or make changes to this bug.