- From: westhawk <thp@westhawk.co.uk>
- Date: Thu, 31 May 2018 19:30:10 +0200
- To: Peter Thatcher <pthatcher@google.com>
- Cc: Harald Alvestrand <harald@alvestrand.no>, public-webrtc@w3.org
Received on Thursday, 31 May 2018 17:30:39 UTC
> On 31 May 2018, at 18:58, Peter Thatcher <pthatcher@google.com> wrote: > > If they want to use SCTP for sending media or use RTP for data channels even if it's "wrong" because no one else does that, I’ll note that both of these things are already possible by mistreating the WebAudioAPI :-) Which brings me to the other guarantee the browser should give - The various APIs should interact in reasonable and unsurprising ways. So for example you should continue to be able to take a mediaStream from webRTC, run it though webaudio (mixing it with a UserMedia stream) and then plug the result into a media stream recorder and have something reasonable happen. Enhancements that aren’t easily pluggable with the rest of the browser’s awesome capabilities are of questionable value IMHO. T.
Received on Thursday, 31 May 2018 17:30:39 UTC