-
Notifications
You must be signed in to change notification settings - Fork 42
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Redefinition of framerateScale and resolutionScale #137
Comments
Here is a proposed revised definition: framerateScale of type double resolutionScale of type double Here is a revision of the examples: Example 11 Example of 3-layer temporal scalability encoding Example of 3-layer temporal scalability with all but bottom layer disabled Example 12 Example of 3-layer spatial simulcast Example of 3-layer spatial simulcast with all but bottom layer disabled Example of 2-layer spatial simulcast combined with 2-layer temporal scalability Example 13 Example of 3-layer spatial scalability encoding Example of 3-layer spatial scalability with all but bottom layer disabled Example of 2-layer spatial scalability combined with 2-layer temporal scalability |
w3c#93 Clarified onerror usage in sender and receiver objects, as noted in: w3c#95 Clarified SST-MS capability issue noted in: w3c#108 Clarification of send() and receive() usage as noted in: w3c#119 Changed ICE state diagram as noted in: w3c#122 Removed getParameters methods and changed send() method as noted in: w3c#136 Changed definition of framerateScale and resolutionScale as noted in: w3c#137 Substituted "muxId" for the "receiverId" as noted in: w3c#138 w3c#140 Clarified the setting of track.kind as described in: w3c#141 Added SSRC conflict event to the RTCRtpSender, as described in: w3c#143 Addressed the "end of candidates" issues noted in: w3c#142 w3c#144
As discussed at the July 20, 2014 ORTC CG meeting, if we define framerateScale and resolutionScale as inverse fractions, we can eliminate some of the rounding issues.
The text was updated successfully, but these errors were encountered: