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
{{ message }}
This repository has been archived by the owner on Jul 12, 2023. It is now read-only.
It takes the AudioPlayer around 800-900ms to fully buffer before finally playing in a voice channel. This is up from <100ms from older versions of Discord.js, using the dispatcher.
I have used tweetnacl and libsodium-wrappers, I have created AudioResources from both local files and remote, latency has not improved.
Steps to reproduce:
Use new Date() immediately after a connection to a voice channel, and again on('stateChange') from buffering to playing. Note the difference is ~900ms.
This bug also often results in the first 800ms or so of audio not being played. My workaround is setting the audio resource volume to inline and adjusting it when I want it to mute or not
Sign up for freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Issue description
It takes the AudioPlayer around 800-900ms to fully buffer before finally playing in a voice channel. This is up from <100ms from older versions of Discord.js, using the dispatcher.
I have used
tweetnacl
andlibsodium-wrappers
, I have created AudioResources from both local files and remote, latency has not improved.Steps to reproduce:
new Date()
immediately after a connection to a voice channel, and againon('stateChange')
from buffering to playing. Note the difference is ~900ms.Code sample
@discordjs/voice version
0.7.5
Node.js version
v16.13.0
Operating system
Windows
Priority this issue should have
Low (slightly annoying)
The text was updated successfully, but these errors were encountered: