You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
With the latest master (a6eda12 at the time of writing) voice receive appears to be wonky — the example 10_voice_receive doesn’t work as advertised.
We narrowed it down to an issue with discord and how they appear to handle (or not handle) initialization of voice connections. Essentially an implementation of AudioReceivers speaking_update will fire if you add print statements or other work to it, but the voice_packet function doesn’t seem to do anything.
The workaround that was figured out for now is to send audio using the bot on connection to a voice channel; after that, incoming packets seem to log as you’d expect.
It sounds like JDA has a similar bug logged so I don’t think it’s necessarily a serenity thing, but we may want an answer for this, even if it’s just “This is known, send a packet first”.
The text was updated successfully, but these errors were encountered:
With the latest master (a6eda12 at the time of writing) voice receive appears to be wonky — the example 10_voice_receive doesn’t work as advertised.
We narrowed it down to an issue with discord and how they appear to handle (or not handle) initialization of voice connections. Essentially an implementation of
AudioReceiver
sspeaking_update
will fire if you add print statements or other work to it, but thevoice_packet
function doesn’t seem to do anything.The workaround that was figured out for now is to send audio using the bot on connection to a voice channel; after that, incoming packets seem to log as you’d expect.
It sounds like JDA has a similar bug logged so I don’t think it’s necessarily a serenity thing, but we may want an answer for this, even if it’s just “This is known, send a packet first”.
The text was updated successfully, but these errors were encountered: