-
-
Notifications
You must be signed in to change notification settings - Fork 40
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
VoiceNext stopped working due to change in protocol #508
Comments
Does this still occur? Might be a problem with Discord. I'm not aware of any changes since we're still using the default voice gw version which is so old, it won't really be changed anyways, normally. |
Yes this problem still occurs. It should be fully replicable (happens 100% of time) |
ah damn it |
I don't but i could set it up test stuff with Makoto with pretty minimal effort (basically just adding vn and a few test commands) |
Can confirm this happens with IncomingAudio enabled. Tested with: [SlashCommand("test", "Test.")]
public async Task Test(InteractionContext ctx, [Option("test", "test"), MinimumValue(1), MaximumValue(2000)] int number)
{
try
{
var guild = ctx.Guild;
var channels = await guild.GetChannelsAsync();
var voiceChannel = channels.First(x => x.Id == 1036569241488474192ul);
var voiceNext = ctx.Client.GetVoiceNext();
var audioConn = await voiceNext.ConnectAsync(voiceChannel);
audioConn.UserJoined += (conn, args) =>
{
Log.Debug("User {user} joined", args.User.Username);
return Task.CompletedTask;
};
audioConn.UserSpeaking += (conn, args) =>
{
Log.Debug("User {user} speaking", args.User.Username);
return Task.CompletedTask;
};
audioConn.VoiceReceived += (conn, args) =>
{
return Task.CompletedTask;
};
}
catch (Exception ex)
{
Log.Error(ex, "Error");
}
} @Lulalaby I don't think we ever fixed incoming audio, did we? @Licho1 For the time being, if you do not need incoming voice data you can disable that and no exception will be thrown anymore. If you do, you'll need to wait for us to fix it (or make a PR to fix it, if you'd like). I'll take a look at it today but i can't promise anything, i have basically no idea about VoiceNext. |
Thanks! So it seems that discord has changed something. I have no idea how this protocol works, is there some documentation for voice protocol? Or is it all reverse engineered? |
The only thing i can tell from my testing is that the issue lies in AudioSender, some method that looks to be a workaround for out of order packets, i'm not really sure at all. Tried playing around with it earlier but got nowhere really. I'm not really experienced with this kind of stuff unfortunately, so that was to be expected (and neither do i have the motivation to actually try and learn it atm). As for docs this seems to be the only docs. I'd assume you'd the same for receiving as sending just backwards. We'll have to wait for Lala to fix it (or for me to sit my ass down and learn lol). We're gonna fix this one way or another, probably |
@Licho1 dumb idea, but could you try |
I have forgotton to mention, it didn't fix it. Bug still persist in 10.6.6.-nightly-018 |
Summary
VoiceNext cannot receive messages
Reproduction Steps
Minimal Reproducible Code
Expected Results
In the past identical code worked
Actual Results
Exception occurs
System Information
Not relevant, windows 11
Checklist
Additional Context
No response
The text was updated successfully, but these errors were encountered: