Browse Source
As it is a required parameter. Don't unnecessarily send a second SPEAKING payload after connecting to voice We do need to send a SPEAKING payload in order to set our SSRC value after connecting to voice, yet that can be with a `state` of 0 (SpeakingState.none). There is no reason to send 2 packets; one marking ourselves as speaking, and then not speaking.pull/9302/head
committed by
GitHub
1 changed files with 6 additions and 1 deletions
Loading…
Reference in new issue