16 Replies
• What's your exact discord.js
npm list discord.js and node node -v version?
• Post the full error stack trace, not just the top part!
• Show your code!
• Explain what exactly your issue is.
• Not a discord.js issue? Check out #useful-servers.that error normally indicates that the data youre passing is too big.
What exactly are you trying to play?
well i honestly don't know how long it was because it was a direct voice audio buffer
bot just listens to users in voice
that shouldn't have happened..?
so it was a one time only error? or does it occur often?
uh logs are kinda full from it
at least 15 times in row
this is receiving code
unfortunately im not too familiar with voice receiving.
If you could possibly find out how much data is being decoded/encoded there? as i how long the audio buffers are.
ill try to log them today and will ping you if i find out, btw can my opus configuration encoder effect that?
it shouldnt
hm kay, just wasnt sure about those constructor values on encoder
the error was emitted by prism-media (which discord.js uses internally for audio encoding and decoding) when it was trying to spawn a new ffmpeg process.
those seem right
yeah noticed that, but now just have to find cause and debug it
where exactly could i check that..?
by just putting log length into stream.on('data') or?
iirc buffer.lenght could give some information
dont remember the exact properties so double check that
if it errors down, not sure how could i log size without logging every time
also its Buffer.byteLength
still didnt figure how to catch it
ill try to internally wrap line in catch and log properties available