The bug is caused by the incorrect RTP timestamp and sequence numbers set for the newly created tracks. This has been introduced during the simulcast implementation to make on-demand subscriptions (unlike the previous non-simulcast version that created local tracks upon reception of remote tracks and added the same track to each participant who tried to subscribe to other participant's feeds).
This goes along with the RTP rewriting story, so must be implemented anyway.
The bug is caused by the incorrect RTP timestamp and sequence numbers set for the newly created tracks. This has been introduced during the simulcast implementation to make on-demand subscriptions (unlike the previous non-simulcast version that created local tracks upon reception of remote tracks and added the same track to each participant who tried to subscribe to other participant's feeds).
This goes along with the RTP rewriting story, so must be implemented anyway.