Jda: DefaultAudioSendSystem not sending audio on 3.7.0

[dgcole]

General Troubleshooting

• [X] I have checked for similar issues.
• [x] I have updated to the [latest JDA version][download].
• [X] I have checked the branches or the maintainers' PRs for upcoming features/bug fixes.

Issue

Issue Type

• [X] Bug Report
• [ ] Feature Request

Description

Just as the title says, voice is silently broken in 3.6.0_378 and up. Both my own bot and the lavaplayer demo bot are otherwise working and do not show any errors, yet there is no sound being sent through Discord.

[MinnDevelopment]

Please update your version. We are currently on 3.7.0_382.

[dgcole]

I am using 3.7.0_382 with it being broken there too. I went back and observed that 3.6.0_378 is the update that broke it.

[MinnDevelopment]

Please be more specific about what your issue is, rather than "it doesn't work".

[dgcole]

There is no sound whatsoever coming from the bot, nor is the green ring lighting up. I've verified in the debugger that voice frames are still being sent fine by lavaplayer, and the only thing that is changed to break it is a jda update.

[MinnDevelopment]

I'm having absolutely no issues sending audio with lavaplayer on the latest version, so please investigate further because you are the only one here that can find the problem.

I have tested with java 8 and 10, both work for me.

[MinnDevelopment]

Ok I think I know your problem, I will investigate further when I have more time. In the meantime try using jda-nas.

[dgcole]

Oh, well thanks for the quick help. It's not actually a pressing problem, I can remain on 377 for the foreseeable future. I just noticed a problem and wanted to report it.

If it helps at all I just tried running both my bot and the lavaplayer demo bot on a raspberry pi running the latest raspbian and java 9 with the same results as on my windows 10 pc running java 10.

edit: Using jda-nas fixed it, although it is not an option on ARM.

[MinnDevelopment]

Is the problem resolved on build 3.7.0_384?

[dgcole]

As far as I can tell everything is working on 3.7.0_384. Thanks for the quick fix!