W3C home > Mailing lists > Public > public-webrtc@w3.org > August 2012

Re: [Bug 18485] Change DTMF API to be on PeerConnection

From: Martin Thomson <martin.thomson@gmail.com>
Date: Wed, 15 Aug 2012 09:03:31 -0700
Message-ID: <CABkgnnUz1kJoibrJxr9wz2NG=BEoXqQmUDrBYY8HHA25NbpJtg@mail.gmail.com>
To: bugzilla@jessica.w3.org
Cc: public-webrtc@w3.org
On 15 August 2012 01:38,  <bugzilla@jessica.w3.org> wrote:
> --- Comment #5 from Harald Alvestrand <harald@alvestrand.no> 2012-08-15 08:38:15 UTC ---
> Based on further discussion, a need has been identified to play back tones in
> synchronity with the DTMF signals going out.

I've been following this, but I didn't reach that conclusion.

Providing audio feedback to a user when a button is pressed is
commonplace and evidently useful for some applications.  (Personally,
I find it irritating - the first customization I make on any PC is to
turn of all forms of audible feedback.)

That doesn't immediately mean that adding audible feedback to another
media stream is an obvious conclusion.  The only argument presented
for synchronization was to make echo cancellation easier to implement.
 Given that this is only one potential source of sounds that could
cause echo, I'm not sure how this actually makes it easier anyhow.

If we wanted synchronization with an incoming stream, wouldn't that be
based on when the remote peer heard the tones and not when we sent
them?  That's the only other reason for that level of synchronization
I can imagine (and it's an awful reason if you start thinking about
corner cases).

Received on Wednesday, 15 August 2012 16:04:00 UTC

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