mirror of
https://github.com/livekit/livekit.git
synced 2026-03-31 04:35:40 +00:00
79cdc2df2e
* Unify muted and unmuted migration paths. If dynacast had disabled all layers, after a migration, the client did not restart publish (it is akin to muted track). That failed migration because migration state machine waits for unmuted tracks to be published (i. e. server has to receive packets). If a migrating track is in muted state, server does not wait for packets. It synthesises the published event and catches up later when packets actually come in. Just treating all migrations as the erstwhile muted case. Sythesise publish whether track is muted or not. In the unmuted case, packets might arrive soon after whereas in muted case, it will depend on when unmute happens. This is tricky stuff. So, will need good testing. * use muted from track info