-
-
Notifications
You must be signed in to change notification settings - Fork 338
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
update WebRTC.framework to M87 #545
Conversation
I tried this branch out, getting the issue of all incoming streams having the same video feed when using janus, this does not occur when using master or the task/7.0.0 branch. |
…srtc into task/8.0.0
@akilude thx, i merged master on 8.0.0 like i did previously on 7.0.0: cc @numerized |
merged master from 6.0.14 |
Task/8.0.0 upgrade to WebRTC M87
…srtc into task/8.0.0
I will rebase master after 6.0.17, Typescript is 6.1.0 and 8.0.0.will land Transceiver and Typescript while 7.0.0 is short lived for M79 will be followed by M86 or M87 if released by Chromium then. |
* Create native class for transceivers. * Extend js class for transceivers. * Add RTCPeerConnection.addTransceiver. * Set up basic callback for sending native state to js.
* Invoke the native transceiver stop function. * Allow setting direction from JS. * State event for updating the JS state.
* Added PluginRTCRtpTransceiver#stringToDirection() * Fixed typo rendonly -> sendonly.
* Instead of having permanent ID's for the JS -> Transceiver association, just have transient ones until the next transceiver state update. Until better solution can be found. * Reduce complexity of transceiver constructor.
* Update sender parameters along with transceivers. * Parse and pass along sendEncodings when doing addTransceiver.
WIP: Task/589/implement addtransceiver
WebRTC M84 Release Notes https://groups.google.com/forum/#!msg/discuss-webrtc/MRAV4jgHYV0/5019yB-HAwAJ
Testing
To test
task/8.0.0
branch