URGENT: Upgrade to mediasoup-client 3.15.0 ASAP

Announcements
1

mediasoup-client 3.15.0 has been released and everyone should upgrade to it ASAP.

In Chrome M140, the way codec payload types and RTP extension IDs are assigned in the local SDP will dramatically change and will break assumptions made by mediasoup-client internals. In current Chrome Canary (version 141) this is already true, so literally mediasoup-client doesn’t work on it.

The new version 3.15.0 of mediasoup-client fixes this problem.

PLEASE UPGRADE ASAP

4 Likes
2

For those not using the client and went custom, what would the results be, should we do some tune-ups?

3

I cannot know. It depends on what those custom clients do. Just follow the rationale in the GH issue and PR and do the same if needed.

4

Nothing to do with the IDEAL/EXACT params chrome pushed the other week for GUM (getusermedia) selection?

5

I don’t know which changes you mean but gUM is completely unrelated to this topic, plus mediasoup-client doesn’t invoke gUM at all.

1 Like
6

This topic was automatically closed after 2 days. New replies are no longer allowed.