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
ISSUE: Bot will never begin playing audio because the "player" object will never emit 'stateChange'
PERCEIVED CAUSE: A state change is not being emitted until "player.play()" is called, which will emit the stateChange event that performs "attachRecorder()".
Although a subscription is added, that in itself is not enough to emit a state change or cause the player to begin playing. In the example, following connection.subscribe(player), a new line with "player.play()" should be added.
Code sample
No response
Package version
v13.7
Node.js version
16.12
Operating system
Windows
Priority this issue should have
Medium (should be fixed soon)
Which partials do you have configured?
Not applicable (subpackage bug)
Which gateway intents are you subscribing to?
Not applicable (subpackage bug)
I have tested this issue on a development release
No response
The text was updated successfully, but these errors were encountered:
Which package is this bug report for?
voice
Issue description
See:
voice-examples/radio-bot/src/bot.ts
Line 105 in 266d250
ISSUE: Bot will never begin playing audio because the "player" object will never emit 'stateChange'
PERCEIVED CAUSE: A state change is not being emitted until "player.play()" is called, which will emit the stateChange event that performs "attachRecorder()".
In the example, the following code is as follows:
Although a subscription is added, that in itself is not enough to emit a state change or cause the player to begin playing. In the example, following connection.subscribe(player), a new line with "player.play()" should be added.
Code sample
No response
Package version
v13.7
Node.js version
16.12
Operating system
Windows
Priority this issue should have
Medium (should be fixed soon)
Which partials do you have configured?
Not applicable (subpackage bug)
Which gateway intents are you subscribing to?
Not applicable (subpackage bug)
I have tested this issue on a development release
No response
The text was updated successfully, but these errors were encountered: