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
Please describe the problem you are having in as much detail as possible:
I have a sound bot, that joins a channel, plays an audio file and leaves the channel again.
If the user asks the bot to join this channel too soon after it disconnected, the bot joins the channel, but the channel.join() in the code rejects with a VOICE_CONNECTION_TIMEOUT Error after 15 sec . Then it is impossible to either join or leave the channel again. but technically the bot joined the channel and is still in there.
The sequence of triggering sound commands has to be really fast to reproduce this issue. Even some delays <300 ms are enough on my setup to let this work like expected.
Include a reproducible code sample here, if possible:
I noticed, that issuing multiple channel.join() commands after the crashes in a catch block, make the bot leave the channel after sending the file stream. But in this case the audio in discord is not hearable. I just lets the bot disconnect from the channel after the finish event. After that everything is back to normal.
Here is another code sample of the same function of my workarounds that worked for me so far, but seem a bit hacky since it uses a static delay.
constguildOptions=newMap();asyncplay(sound,channel){returnawaitnewPromise(async(resolve,reject)=>{if(!channel.joinable||!channel.speakable){return}if(!guildOptions.has(channel.guild.id)){guildOptions.set(channel.guild.id,{});}letoptions=guildOptions.get(channel.guild.id);letconnection;try{if(options.connection&&options.connection.status===4){if(options.disconnectTime){// ensures a delay of 300 ms between the last leaving event before joining againconsttimeToWait=Math.max(0,300-Math.abs(moment().diff(options.disconnectTime)))if(timeToWait>0){log.debug(`waiting ${timeToWait} ms`)awaitnewPromise((resolve)=>{setTimeout(resolve,timeToWait)})}}}connection=awaitchannel.join()}catch(err){try{channel.join()connection=awaitchannel.join()}catch(e){channel.leave()reject();return;}}if(options.dispatcher){options.dispatcher.off('finish',options.callback);}if(options.resolve){options.resolve();}options.resolve=resolveoptions.connection=connection;letreadStream;try{readStream=dbManager.getFileStream(sound.file);}catch(e){connection.disconnect();reject();return;}letdispatcher=connection.play(readStream,{volume: .5,highWaterMark: 1});options.callback=()=>{setTimeout(()=>{options.dispatcher.off('finish',options.callback);options.disconnectTime=moment();connection.disconnect();resolve();},100)}dispatcher.on('finish',options.callback);options.dispatcher=dispatcher;})}
Further details:
discord.js version: 12.0.2 / 12.1.1
Node.js version: 12.3.1
Operating system: Ubuntu 18.04 / CentOS 7
Priority this issue should have – please be realistic and elaborate if possible: Maybe 4/10
I have also tested the issue on latest master, commit hash:
The text was updated successfully, but these errors were encountered:
We're working on a new implementation of Discord's Voice API that has better playback quality and is more reliable than what we currently support in Discord.js v12 - check it out at https://github.com/discordjs/voice!
The new library solves many of the issues that users are facing, and as part of this, we're dropping built-in support for voice in our next major release. We have a PR (#5402) that adds native support for our new voice library - once this PR is merged, this issue will be closed.
You can still use our new voice library before that PR lands - just take a look at our music bot example to see how to get started upgrading your voice code. By using the boilerplate music player in the example, you can make it even easier to upgrade your code.
Note that the PR above only reduces some of the boilerplate code you'd otherwise have to write - you do not have to wait for the PR to be merged to start using the new voice library.
If you have any questions about this, feel free to:
Make an issue if you have found a bug in the new voice library
Use GitHub Discussions or join our Discord server (we have a new channel, #djs-new-voice, specifically for this!) to ask general questions about the library, give feedback on the library, and get support with upgrading to it
Please describe the problem you are having in as much detail as possible:
I have a sound bot, that joins a channel, plays an audio file and leaves the channel again.
If the user asks the bot to join this channel too soon after it disconnected, the bot joins the channel, but the channel.join() in the code rejects with a
VOICE_CONNECTION_TIMEOUT
Error after 15 sec . Then it is impossible to either join or leave the channel again. but technically the bot joined the channel and is still in there.The sequence of triggering sound commands has to be really fast to reproduce this issue. Even some delays <300 ms are enough on my setup to let this work like expected.
Include a reproducible code sample here, if possible:
I noticed, that issuing multiple
channel.join()
commands after the crashes in a catch block, make the bot leave the channel after sending the file stream. But in this case the audio in discord is not hearable. I just lets the bot disconnect from the channel after the finish event. After that everything is back to normal.Here is another code sample of the same function of my workarounds that worked for me so far, but seem a bit hacky since it uses a static delay.
Further details:
The text was updated successfully, but these errors were encountered: