Are we now using github for discussions relating to WG consensus?? The problem with maxFramerate is that it can result in two simulcast streams with the same frame rate - which is the reason why track cloning doesn't work. For example, setting maxFramerate on one stream to 7.5 and another to 15 does not work if the frame rate coming from the camera is < 7.5. In fact one could argue that there is no need for maxFramerate in the encoding parameters at all - just use constraints if that's what you want. On Nov 4, 2015, at 7:29 PM, Mathieu Hofman <notifications@github.com<mailto:notifications@github.com>> wrote: I thought we converged to agreeing maxFramerate was enough, and that a framerateScale might be weird for source with variable framerate, e.g. screensharing. As an application developer, max-framerate is what I want. — Reply to this email directly or view it on GitHub<https://github.com/w3c/webrtc-pc/pull/353#issuecomment-153914946>.Received on Thursday, 5 November 2015 00:44:11 UTC
This archive was generated by hypermail 2.4.0 : Friday, 17 January 2020 19:18:10 UTC