This message was deleted.
# sdk-rust
s
This message was deleted.
šŸŽ‰ 2
q
Great, I'm going to merge the gst-plugins-rs MR then !
šŸ™Œ 2
šŸ‘ 1
šŸŽ‰ 1
Do I need to react to the server telling the publisher to mute? whats the expected behaviour
Also, how is the connection quality metric computed? I'm getting a bad quality even on local network
d
for mute, you can pause publishing. the server would have already marked it as muted to avoid forwarding to other clients
as for connection quality, it's likely due to: • publisher not sending the right simulcast layers (for example, if it's signaling 3 layers, but only pushing bits for 1). This typically indicates congestion on the publisher's side • packet losses (could be coming from unhandled NACKs)
q
What are you expecting on nack? I'm not sending any layers in the addtrackrequest (webrtcsink doesn't have simulcast support yet)
What does pause publishing mean? Change the direction of the stream to inactive in an sdp update? Or just stop sending media packets?
d
the latter - just stop sending packets. (it'll just use a bit more bandwidth if left alone, which is also fine)
on NACK, we expect the same packets to be retransmitted with the same SSRC. This will be an issue over the internet, but I'm not confidence this is the issue since you are testing over localhost
if you can send me the server logs, I can take a look!