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

Issue 596098 link

Starred by 3 users

Issue metadata

Status: WontFix
Owner: ----
Closed: Mar 2016
Cc:
Components:
EstimatedDays: ----
NextAction: ----
OS: Chrome
Pri: 2
Type: Bug



Sign in to add a comment

Audio codec(Opus, iSAC16k ) bitrate in peerconnection audio only call on device Sentry is below expected range

Project Member Reported by srcv@chromium.org, Mar 18 2016

Issue description

Chrome version: 50.0.2661.37 / 7978.20.0 dev
Device: Sentry

Steps to reproduce:

1. Browse to https://webrtc.github.io/samples/src/content/peerconnection/audio/
2. Open the javascript console (alt+cmd+j or ctr+shift+j) and watch for any errors
3. For each codec in the dropdown menu and Press 'Call'
4. Observe the bitrate graphs for each codec: 
a. For 'Opus' codec, the Bitrate graph shows values ranging between 10 and 30 kbps (not in the expected range of ~40kbps) 
b. For 'iSAC 16k' codec, the Bitrate graph shows values ranging between 10 and 15 kbps (not in the expected range of ~30 kbps)
c. For G722 codec, the Bitrate graph shows values ranging around 70kbps d. For PCMU codec, the bitrate graph shows values ranging around 70kbps
5. Observe that the Packets sent per second graph shows nonzero values
(working as expected)

Expected results:
Opus:
Bitrate range: ~40 kbps
Packets sent per second range: ~50 packets

iSAC 16k
Bitrate range: ~30 kbps
Packets sent per second range: ~35 packets

G722
Bitrate range: ~70 kbps
Packets sent per second range: ~50 packets

PCMU
Bitrate range: ~70 kbps
Packets sent per second range: ~50 packets

Actual results:
Opus:
Bitrate range: 10-30 kbps 
Packets sent per second range: ~50 packets

iSAC 16k
Bitrate range: 10-15kbps
Packets sent per second range: ~35 packets

G722
Bitrate range: ~70 kbps
Packets sent per second range: ~50 packets

PCMU
Bitrate range: ~70 kbps
Packets sent per second range: ~50 packets

 
Device_sentry_webrtc_internals_dump.txt
131 KB View Download

Comment 1 by srcv@chromium.org, Mar 18 2016

Status: WontFix (was: Untriaged)
Now tracking in partner tracker #51372.

Sign in to add a comment