- From: Jim Barnett <Jim.Barnett@genesyslab.com>
- Date: Fri, 20 Sep 2013 13:01:43 +0000
- To: Harald Alvestrand <harald@alvestrand.no>
- CC: "public-webrtc@w3.org" <public-webrtc@w3.org>
Yes, you're right. I'd forgotten that. But applyConstraints can be called at any time, and always replaces any existing constraints with the newly specified ones. We can certainly define 'output' constraints for Track and use applyConstraints to apply them. Isn't the problem renegotiation or inefficiency? If you call addStream with stream-level constraints and then applyConstraints to tweak the constraints at the Track-level, the Track-level constraints might force an immediate renegotiation, which would be ugly. Conversely, if you call applyConstraints first, addStream's constraints might overwrite them. Could we handle this by prioritizing Track constraints above the addStream constraints? - Jim -----Original Message----- From: Harald Alvestrand [mailto:harald@alvestrand.no] Sent: Friday, September 20, 2013 3:32 AM To: Jim Barnett Cc: public-webrtc@w3.org Subject: Re: [rtcweb] Constraints on a track in a a given PC On 09/20/2013 12:38 AM, Jim Barnett wrote: > What if Track supported applyConstraints? It does. But that manipulates the "input" constraints (those specified at getUserMedia time), not the "output" constriants (those specified at AddStream time).
Received on Friday, 20 September 2013 13:02:10 UTC