A mechanism to detect missing input (mic) audio data has been implemented in Chrome[1]. After around 15 seconds of no input audio data, the audio track and its source will be stopped and the ‘ended’ event is fired[2].
The reason for this is that the stream typically doesn’t recover from this state. The application can choose what to do, for example try to restart the input stream or inform the user that there is a problem.
This change will be in M60.
Regards,
Henrik
[1] https://chromium.googlesource.com/chromium/src/+/021d9e05dc8384ba3d5f7c1c1834ee0bf9fd3e5c
[2] https://w3c.github.io/mediacapture-main/#event-mediastreamtrack-ended
Complete mute of mic input device results in no change in track status even after 30 seconds.
Has this change been withdrawn?
Withdrawing would actually be preferable as this behaviour would have unpredictable impact on many applications where user muting preference are unknown.
If this is implemented, then we will have to instruct users to only use our application mute mic function and never their system or audio peripheral mute.
Agree, it would be good to understand the motivation for the idea of assuming the track can be ended, just because it has had no signal for an arbitrary period of time.
--
---
You received this message because you are subscribed to the Google Groups "discuss-webrtc" group.
To unsubscribe from this group and stop receiving emails from it, send an email to discuss-webrtc+unsubscribe@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/discuss-webrtc/fd482671-e0c0-473e-861a-9aa70042e8a3%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
The track "ended" event fires when the remote sends us a SDP in which
a sending audio/video track has been removed. That's AFAIK the only
way to signal that a remote track has definitely ended.
--
---
You received this message because you are subscribed to the Google Groups "discuss-webrtc" group.
To unsubscribe from this group and stop receiving emails from it, send an email to discuss-webrtc+unsubscribe@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/discuss-webrtc/CALiegfmwpyOkZsh8g-R6_uaDGXVeCFMd0QFnDfJ1RDZmbQWMww%40mail.gmail.com.
* Detection is done in AudioInputDevice as this corresponds to a physical device which is what we want to detect missing callbacks for. * When detected we call CaptureError() on the capturer, which stops the source and puts the track in ended state and fires the ended event.
To view this discussion on the web visit https://groups.google.com/d/msgid/discuss-webrtc/CAOKXErqyzhX7RN-5-GiUy2%3DPciwxoS%3DJyrzi4GURApV%3DFraYkg%40mail.gmail.com.
Yeah, I think the commit message confirms that:* Detection is done in AudioInputDevice as this corresponds to a physical device which is what we want to detect missing callbacks for. * When detected we call CaptureError() on the capturer, which stops the source and puts the track in ended state and fires the ended event.Best Regards,
Silvia.
On 30 Jun. 2017 8:29 pm, "Dag-Inge Aas" <dagi...@appear.in> wrote:
Not to answer on behalf of Google here, but I'm 99% sure that this is related to the infamous Chrome Audio bug that has been plaguing OSX users for some years now. That is that Chrome will for some reason fail to obtain the microphone but still resolve with the microphone track, so that you believe you have a microphone input, but it is in fact silent.
More details here: https://bugs.chromium.org/p/webrtc/issues/detail?id=4799
On Fri, Jun 30, 2017 at 10:37 AM, Warren McDonald <warren....@gmail.com> wrote:
Agree, it would be good to understand the motivation for the idea of assuming the track can be ended, just because it has had no signal for an arbitrary period of time.
--
---
You received this message because you are subscribed to the Google Groups "discuss-webrtc" group.
To unsubscribe from this group and stop receiving emails from it, send an email to discuss-webrt...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/discuss-webrtc/fd482671-e0c0-473e-861a-9aa70042e8a3%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
--
---
You received this message because you are subscribed to the Google Groups "discuss-webrtc" group.
To unsubscribe from this group and stop receiving emails from it, send an email to discuss-webrt...@googlegroups.com.
To unsubscribe from this group and stop receiving emails from it, send an email to discuss-webrtc+unsubscribe@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/discuss-webrtc/d1212d49-df6e-459b-b7f3-9df7ce891f4b%40googlegroups.com.