TS3AudioBot
TS3AudioBot copied to clipboard
Playlist Stops for other source plays
Describe the bug When I play a playlist and play a song from another source in the playlist (YouTube, Radio Stream), the playlist will stop playing
To Reproduce !list play xzz !play https://www.youtube.com/watch?v=sqIwwV1bYaM !next (Or wait until the song is over)
Version Version: 0.11.0-alpha.32 Branch: develop CommitHash: 082be9fdad20e02a082689d60c2829c53c37a818
Platform Windows 10 Pro 64Bit
Log
2019-11-14 17:51:57.0291| INFO||Setup.LogHeader [============ TS3AudioBot started =============]
2019-11-14 17:51:57.0817| INFO||Setup.LogHeader [ Date/Time: Donnerstag, 14. November 2019 17:51:57
2019-11-14 17:51:57.0974| INFO||Setup.LogHeader [ Version: 0.11.0-alpha.32/develop/082be9fd
2019-11-14 17:51:57.1041| INFO||Setup.LogHeader [ Platform: Windows 6.2.9200.0 (64bit)
2019-11-14 17:51:57.1041| INFO||Setup.LogHeader [ Runtime: .NET Framework 4.0.30319.42000 ServerGC:False GC:SustainedLowLatency
2019-11-14 17:51:57.1041| INFO||Setup.LogHeader [ Opus: libopus 1.2.1-fixed (x64)
2019-11-14 17:51:57.1271| INFO||Setup.LogHeader [==============================================]
2019-11-14 17:51:57.5635| INFO||Bot.InitializeBot Bot "default" connecting to "XX.XX.XX.XXX"
2019-11-14 17:51:58.1295| INFO||WebServer.StartWebServer Started Webserver on port 58913
2019-11-14 17:51:58.2812| INFO|0|Bot.OnBotConnected Bot "default"(0) connected.
2019-11-14 17:52:08.0904| INFO|0|Bot.OnMessageReceived User Abu requested: !list play test
2019-11-14 17:52:08.1612| WARN|0|RightsManager.ReadFile Right "cmd.list.save" is not registered.
2019-11-14 17:52:08.7118| WARN|0|WebWrapper.ToLoggedError Web error: [403] Forbidden
System.Net.WebException: Der Remoteserver hat einen Fehler zurückgegeben: (403) Unzulässig.
bei System.Net.HttpWebRequest.GetResponse()
bei TS3AudioBot.Helper.WebWrapper.GetResponse(Uri link, Action`1 body, TimeSpan timeout)
2019-11-14 17:52:11.8210| WARN|0|Bot.LoggedUpdateBotStatus Fehlende Berechtigungen.
2019-11-14 17:52:13.5811| INFO|0|Bot.OnMessageReceived User Abu requested: !play [URL]https://www.youtube.com/watch?v=1QTOpTZRvnU[/URL]
2019-11-14 17:52:13.9476| WARN|0|WebWrapper.ToLoggedError Web error: [403] Forbidden
System.Net.WebException: Der Remoteserver hat einen Fehler zurückgegeben: (403) Unzulässig.
bei System.Net.HttpWebRequest.GetResponse()
bei TS3AudioBot.Helper.WebWrapper.GetResponse(Uri link, Action`1 body, TimeSpan timeout)
2019-11-14 17:52:16.8444| WARN|0|Bot.LoggedUpdateBotStatus Fehlende Berechtigungen.
2019-11-14 17:55:34.4012| INFO|0|PlayManager.StopInternal Song queue ended: Es konnte kein nächster Song gespielt werden.
2019-11-14 17:55:34.4241| WARN|0|Bot.LoggedUpdateBotStatus Fehlende Berechtigungen.
That's not a bug but working as intended.
When you call !play ... or !list play ... that play call will replace the playback queue (You can check the playback queue with !info)
If you want to append the song use !add ... however that will add to the end of the playback queue
But I can not remember that it was like this? Because eig., It was always like this, when I played a playlist, I could add a song per !Play and after the song ran the playlist again?
Yes it changed with the bigger playlist/api rework
Can you do that so that you can enable and disable it?
Or is that no longer possible?
How would you expect it to work? When playing a single song should it
- (Current behaviour) replace playlist, then jump to and play (ex: spotify)
- inserted after the current song, then jump to and play (similar to the old one)
- be added at the end then jump to and play (ex: vlc)
- replace the current song and play (ex: ?)
- other ?
If you can give me a good reasoning I can see whether I can get an option for that back
I would be happy about the obsolescence again: "inserted after the current song, then jump to and play (similar to the old one)" again because I have had a very good experience with it or you do it so the listing can be decided by yourself in the config (playlist type: spotify, inserted, vlc, ...)
Something new ?
Right now people are screaming for perm via api (#651) but i'll see If I can squeeze it somewhere in