Re: Intent to ship WebRTC RTCRtpReceiver contributing and synchronization sources

2017-12-07 Thread Nico Grunbaum
Answers can be found inline. -Nico On 12/7/17 12:45 PM, Boris Zbarsky wrote: On 12/6/17 3:22 PM, Nico Grunbaum wrote: It is in nightly now, and we intend to ship these interfaces in 59. Chrome shipped a partial implementation[3] of getContributingSources() in 59. Edge has partial support[4

Re: Intent to ship WebRTC RTCRtpReceiver contributing and synchronization sources

2017-12-06 Thread Nico Grunbaum
://bugs.chromium.org/p/chromium/issues/detail?id=703122=2 [4] https://msdn.microsoft.com/en-us/library/mt502507(v=vs.85).aspx [5] https://bugzilla.mozilla.org/show_bug.cgi?id=1419900 [6] https://github.com/w3c/webrtc-pc/pull/1668#issuecomment-346951615 -- Nico Grunbaum On 12/6/17 5:42 AM, Boris Zbarsky wrote

Intent to ship WebRTC RTCRtpReceiver contributing and synchronization sources

2017-12-05 Thread Nico Grunbaum
-rtcrtpreceiver [2] https://w3c.github.io/webrtc-pc/#dom-rtcrtpreceiver-getstats() Cheers, Nico Grunbaum -. --. ___ dev-platform mailing list dev-platform@lists.mozilla.org https://lists.mozilla.org/listinfo/dev-platform

Re: More ThinkStation P710 Nvidia tips (was Re: Faster gecko builds with IceCC on Mac and Linux)

2017-11-02 Thread Nico Grunbaum
For rr I have an i7 desktop with a base clock of 4.0 Ghz, and for building I use icecc to distribute the load (or rather I will be again when bug 1412240[0] is closed).  The i9 series has lower base clocks (2.8 Ghz, and 2.6Ghz for the top SKUs)[1], but high boost clocks of 4.2 Ghz.  If I were