Cog-Creators / Cog-Creators/Red-DiscordBot

[Audio] Players restored from persistqueue at 100% volume

Open
#6,217 1 comment 0 reactions 0 assignees View on GitHub
Category: Cogs - Audio Status: Needs Triage Type: Bug
Dominant language
Python
Stars
5.7k
Forks
2.5k
Avg merge
6d 16h
Merged PRs (30d)
1

Description

### 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_

Contributor guide

Open the contributing guide

Assessment

This issue has not been assessed yet.

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.