W3C home > Mailing lists > Public > public-webrtc-logs@w3.org > October 2018

[webrtc-pc] DTMF scheduling is subject to JS queueng delays

From: Harald Alvestrand via GitHub <sysbot+gh@w3.org>
Date: Mon, 01 Oct 2018 10:36:26 +0000
To: public-webrtc-logs@w3.org
Message-ID: <issues.opened-365401767-1538390185-sysbot+gh@w3.org>
alvestrand has just created a new issue for https://github.com/w3c/webrtc-pc:

== DTMF scheduling is subject to JS queueng delays ==
Not a request for change, but a check that this is what we wanted to say:

Currently, the "playoutTask" in DTMF describes that the PlayoutTask is executed on the main thread, and that the "ontonechange" event as well as scheduling of the next tone is fired from within the PlayoutTask.

This means that if the "playoutTask" is delayed for any reason (such as main thread congestion), the next tone will be delayed - we can't guarantee the inter-tone gap, just that it will be at least as long as specified.

This issue is just to ask "is that OK".

Please view or discuss this issue at https://github.com/w3c/webrtc-pc/issues/1997 using your GitHub account
Received on Monday, 1 October 2018 10:36:27 UTC

This archive was generated by hypermail 2.4.0 : Friday, 17 January 2020 19:22:07 UTC