fix(voice): screen share releases audio connection so Streamer owns voice session
The dank074 Streamer creates its own WebRTC voice connection, but Discord allows only ONE voice session per user. When VoiceController (audio) was already connected, the Streamer join hung forever (never got VOICE_SERVER_UPDATE). Now: 1. ScreenShareController takes releaseVoice/restoreVoice callbacks. 2. Before joining, it disconnects the @discordjs audio connection via VoiceController.disconnectGuild. 3. Streamer joins + streams GoLive. 4. After the stream ends, restoreVoice reconnects the audio connection so mic/listen keep working. 5. media.handler wires these via a new setVoiceController accessor from commandHandler; VoiceController is the single source of truth. Also adds caller-bound timeouts & safe .catch() everywhere so a stream failure can never become an unhandledRejection again.
This commit is contained in:
@@ -86,6 +86,9 @@ export class CommandHandler {
|
||||
this.mediaHandler = new MediaHandler(client, () =>
|
||||
voiceController.getStatus(),
|
||||
);
|
||||
// Give media handler access to disconnect/reconnect voice around screen
|
||||
// share (GoLive needs its own WebRTC connection).
|
||||
this.mediaHandler.setVoiceController(() => voiceController);
|
||||
this.guildHandler = new GuildHandler(client);
|
||||
this.moderationHandler = new ModerationHandler(client);
|
||||
|
||||
|
||||
Reference in New Issue
Block a user