Everything is working pretty good, except switch feature. We use switch to change subscribers’s stream from one publisher to another, and it works great for local publishers, but with remotes, after we make a switch, stream did not receive any packets for a long time (10seconds to 2minutes).
Here is two screens, one for subscriber then local publishers switches, and one for remote. As I see, everytime I switch local publisher, subscriber got keyframe, stream changes, and we receiving packets. For remote, you can see no packets for some time. We think it may be correlated to keyframes somehow, but didn’t know what to debug now.
Maybe you can guide us, how to debug this problem?
I’m not aware of any issue there, but I haven’t checked myself. In theory, remote publishers are identical to local publishers, since the struct is the same, and so are addressed the same way. The keyframe theory is only valid if data is indeed coming in, but you see nothing because a keyframe hasn’t arrived yet: if no data is sent at all, it’s a different issue. You can check if switching audio works, since that doesn’t need keyframes.
Lorenzo, I think you was right - it’s not video specific issue, here is audio case - it’s the same, everything good for locals, and drops for remotes. Right now we will try to find bug, since it’s reproduced every time for us, I let you know if we find something.
If you have some ideas where to start, I will be grateful to hear it.
We found difference in logs for “good” switch and “bad”. Bad has these errors (in subscriber), once they gone - we start receiving packets. Good switches doesn’t have these errors.
Mh this makes me suspect that some RTP rewriting isn’t happening when you switch, but I don’t see why, since RTP packets from remote publishers go through janus_videoroom_incoming_rtp as the ones from local publishers, and switch is a subscriber request that should work the same way no matter the source . Can you open an issue on Github so that we can track it there next week? Thanks!
