New issue
Advanced search Search tips

Issue 920631 link

Starred by 2 users

Issue metadata

Status: Duplicate
Merged: issue 920630
Owner: ----
Closed: Jan 10
Cc:
Components:
EstimatedDays: ----
NextAction: ----
OS: Linux
Pri: 2
Type: Bug



Sign in to add a comment

WebRTC Stats audioLevel only work when using addTrack in legacy stats api

Reported by marten.k...@logmein.com, Jan 10

Issue description

UserAgent: Mozilla/5.0 (X11; Ubuntu; Linux x86_64; rv:64.0) Gecko/20100101 Firefox/64.0

Steps to reproduce the problem:
0. open attached html file
1. start transceiver audio
2. audioLevels are both 0
3. reload
4.start track audio
5. audioLevels differ

What is the expected behavior?
audioLevel should not be zero in standard and legacy api both when using transceiver api and track api

What went wrong?
WebRTC Stats audioLevel only work when using addTrack in legacy stats api (only legacy, not standard stats), not when using transceiver API (neither legacy nor standard stats).
AudioLevel stays zero.

AddTrack + Legacy => works
AddTrack + Standard => stays zero

AddTransceiver + Legacy => stays zero
AddTransceiver + Standard => stays zero

Did this work before? N/A 

Does this work in other browsers? N/A

Chrome version: 73.0.3664.3 (Official Build) dev (64-bit)  Channel: stable
OS Version: 18.04
Flash Version:
 
audioLevelBug.html
4.9 KB View Download
Cc: phanindra.mandapaka@chromium.org
Labels: Triaged-ET
Mergedinto: 920630
Status: Duplicate (was: Unconfirmed)
This issue seems to be similar to Issue: 920630, hence merging into it and marking it as Duplicate.

Thanks..!

Sign in to add a comment