-
-
Notifications
You must be signed in to change notification settings - Fork 1.1k
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
SimulcastConsumer cannot switch layers if initial tsReferenceSpatialLayer disappears #492
Comments
This is not really related to PR #450. The same issue would happen if client starts sending stream 0, then immediately stops it without sending RTCP Sender Report, then in mediasoup we try to switch to stream 0. Since we don't have RTP Timestamp for stream 1 (the previous one in the SimulcastConsumer) we cannot switch to stream 0. Will fix it in next days. |
Sure. The fix we have tested looks like this:
This seems to work well in our tests. |
Thanks, we need some time to review this (we have some other pending work yet). |
Can you please create a PR? |
Yes, happy to do so. It might be in a couple of days due to other commitments. |
👍 |
…tialLayer disappears" (versatica#492) * Set tsReferenceSpatialLayer later, only after receiving an RTCP Sender Report. * Track and carry forward offset from tsReferenceSpatialLayer.
tsReferenceSpatialLayer disappears" (versatica#492) * Set tsReferenceSpatialLayer later, only after receiving an RTCP Sender Report. * Track and carry forward offset from tsReferenceSpatialLayer.
…sReferenceSpatialLayer disappears
Bug Report
SimulcastConsumer cannot switch layers if initial tsReferenceSpatialLayer disappears
Your environment
Issue description
The problem happens if the higher spatial layer is never resumed. For example:
The text was updated successfully, but these errors were encountered: