New issue
Advanced search Search tips

Issue 883289 link

Starred by 3 users
Status: Assigned
Owner:
hbos@chromium.org
Cc:
ar...@chromium.org
Components:
EstimatedDays: ----
NextAction: ----
OS: ----
Pri: 3
Type: Bug

Blocked on:
issue webrtc:10186
issue 893158

Show other hotlists

Hotlists containing this issue:
WebRTC-1.0-Spec-Compliance


Sign in to add a comment

Implement RTCRtpSynchronizationSource.voiceActivityFlag

Project Member Reported by hbos@chromium.org, Sep 12 
As of M73 we have getSynchronizationSources() ( https://crbug.com/883287 ), including audioLevel (https:// https://crbug.com/893172 ).

The only thing that is missing is voiceActivityFlag. We should add it.

Spec: https://w3c.github.io/webrtc-pc/#dom-rtcrtpsynchronizationsource-voiceactivityflag

Comment 1 by hbos@chromium.org, Jan 9 

 Issue 893159  has been merged into this issue.

Comment 2 by hbos@chromium.org, Jan 9

Blocking: 893158

Comment 3 by hbos@chromium.org, Jan 9

Blocking: -893158

Comment 4 by hbos@chromium.org, Jan 9

Blockedon: 893158

Comment 5 by hbos@chromium.org, Jan 9

Blockedon: -883287

Comment 6 by hbos@chromium.org, Jan 9 

It looked like this was available in the lower layer:
https://cs.chromium.org/chromium/src/third_party/webrtc/audio/channel_receive.cc?sq=package:chromium&dr=CSs&g=0&l=594

But it turns out we almost always send the value "true" (depending on codec), making the default Chrome to Chrome connections not able to rely on this.

Comment 7 by hbos@webrtc.org, Jan 9

Blockedon: webrtc:10186

Comment 8 by hbos@chromium.org, Jan 11

Description: Show this description
►

Sign in to add a comment