Cog-Creators / Red-DiscordBot

A multi-function Discord bot
https://docs.discord.red
GNU General Public License v3.0
4.72k stars 2.3k forks source link

[Audio] Players restored from persistqueue at 100% volume #6217

Open aikaterna opened 1 year ago

aikaterna commented 1 year ago

What Red version are you using?

3.5.2

What were you trying to do?

Working on testing something.

What did you expect to happen?

For the Player to be restored for the guild I was in, and for the volume to be set from history or Config.

What actually happened?

The Player was restored, but at 100% volume. Maybe a volume call after the restore, which in this case was

2023-07-28 06:51:30.558  INFO 853978 --- [   XNIO-1 I/O-1] lavalink.server.io.SocketServer          : {"op": "play", "guildId": "133049272517001216", "track": "QAAApAIAN1tFbGVjdHJvXSAtIEZhdnJpZ2h0IC0gR3JlZW4gU3Rvcm0gW01vbnN0ZXJjYXQgUmVsZWFzZV0AE01vbnN0ZXJjYXQ6IFVuY2FnZWQAAAAAAAUJEAALbGNVVU5ETGxmTUkAAQAraHR0cHM6Ly93d3cueW91dHViZS5jb20vd2F0Y2g/dj1sY1VVTkRMbGZNSQAHeW91dHViZQAAAAAAAAAA", "noReplace": false, "startTime": "105260", "pause": true}

after the reconnect from Red-Lavalink.

How can we reproduce this error?

  1. Be able to kill the Lavalink process
  2. Have audioset persistqueue on
  3. Play a song
  4. Reduce the volume noticeably
  5. Kill the Lavalink process
  6. Restart the Lavalink process
  7. The queue and song that was playing are restored after a restart at 100% volume

Anything else?

No response

Flame442 commented 11 months ago

Same issue as #6204?