New issue
Advanced search Search tips

Issue 920630 link

Starred by 11 users

Issue metadata

Status: Unconfirmed
Owner: ----
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
 Issue 920631  has been merged into this issue.
Labels: Needs-Triage-M73
Labels: Needs-Feedback Triaged-ET
Thanks for filing the issue...

Tried to reproduce the issue on reported chrome version 73.0.3664.3 using Ubuntu 17.10. Attaching screen-cast for reference.
Steps: 
------
1. Launched reported chrome 
2. Opened given html file and followed steps as per comment #0.
As we have observed that the audio Level stays zero when clicked both transceiver audio and track audio 

@Reporter: Could you please check the attached screen-cast and let us know if we missed anything from our end.

Thanks.!
920630.webm
2.2 MB View Download
the video show that you weren't asked for audio device permissions. Did your setup not have an audiodevice? To reproduce the issue with this html it is necessary to initialize an audio-mediastream this way. If you try on a machine with at least a default audio device you should be able to reproduce the issue.

I just tried disabling all my audio devices and I was not prompted by chrome to give input device permissions either.
I recorded a screencast of my own
sorry, broken file, again
Screencast 2019-01-11 11:46:39.mp4
917 KB View Download

Sign in to add a comment