Open robvnl opened 4 years ago
By accident I discovered the track info is updated each new track again when I disconnect and connect to the network while the webpage chorus2 is active and playing a stream. As soon as I choose (another) radio stream it again shows the first track info and from then it stays frozen again.
on top of above, I noticed when I disconnect/connect the network I see a message "lost websocket connection" and right after the websocket connection is established again. The stream keeps updating the track information. There is a relation here with the websocket connection that causes the issue, as it looks. I cannot imagine I am the only one who hits this problem. I have reproduced the same in different browsers and on windows, Linux. Also with another raspberry running the same versions but a 2B. Same behavior....
this will be related to the polling I assume
Hi Malard, Maybe. But I I don't think so. It is more getting the track info from the stream when it changes. It's still an issue with Kodi 19.5. Same workarounds. It doesn't matter on which platform or which browser. The official Kodi app on iphone doesn't have the problem. Either directly on the TV screen it behaves as expected.
When using kodi (not chorus) does things update correctly, if its correct somewhere in kodi then either the JSONRPC needs to be fixed, or if its not that then chorus. However if the issue is in kodi or the JSONRPC then this ticket is in the wrong repo
Hi Malard, thanks for looking into it. I has been a while, but looking into the issue it has to be in Chorus, not Kodi. Currently I have Chorus 19.x-2.4.8 on Kodi 19.5 at a Rasp4B with LibreElec 10.0.4. Since Kodi at the Rasp, and the official app on my phone, updates the stream info correctly, it has to be in Chorus. To what repo I should address this you think? It would be great when a developer can fix this. I don't think I am the only one who hits this.
I will need to setup radio side of kodi (which i've honestly never done before), as you've said the official app is updating then that confirms its not the JSONRPC at fault. So i can mirror your setup, what have you configured, what radio station etc
Great you want to reproduce this. I think not any radio station giving track info will be seen by chorus, only at the first when you load it, then it stays on that info. Anyway this is my setup, I have some playlists stored on the rasp4 here:
rasp4media:~/radio # pwd
/storage/radio
rasp4media:~/radio # ls -l
total 8
-rw-r--r-- 1 root root 2822 Jun 3 2020 RadioTunes - Favorites - 2020.pls
-rw-r--r-- 1 root root 2469 Jan 21 2020 RadioTunes_-_Favorites_-_2017_patched.pls
-rw-r--r-- 1 root root 1580 Feb 7 2021 Radio_Streams_2021.m3u
rasp4media:~/radio #
From my webbrowser logged in with Chorus at the rasp I go to Browser -> folder Radio -> Pick a playlist. Radio Tunes are paid streams and I cannot give such a stream without breaking conditions with Radio Tunes. But when I pick "Radio Streams 2021.m3u" and choose "Radio 6 Soul and Jazz" it is a public radio station with track information. This stream is in the Netherlands, not sure if it will be blocked in countries outside of Europe, this is the stream info:
#EXTINF:0,Radio 6 Soul & Jazz
#EXTVLCOPT:network-caching=1000
http://icecast.omroep.nl/radio6-bb-aac
I'm curious if you can reproduce this. Thank you very much in advance.
I have noticed above tiny problem and searched a lot about an eventual config setting but could not get it solved. I wonder what I am doing wrong, and if not, this might be erroneous behaviour.
When I open a music album and I start it, all works fine, it updates the music information such as the track name it is playing. I.e. it refreshes the current track information each playing track. So, in the webbrowser, the info is updated.
However, the above doesn't work with radio streams. I open a playlist with radio streams from the browser in Chorus2. This playlist is retrieved from the local storage, e.g.: /storage/radio/RadioTunes - Favorites - 2017.pls. I can open and play a stream from the list. All working perfectly good. After opening the stream it displays the current "artist and songname". What it doesn't do is refresh/update the "artist and songname" when the next track is started, the first taken track information stays frozen while next songs continue to play.
The problem is not in the stream itself. It does work with the Kodi app on my phone and it does work in Kodi when I watch it at the TV.
I have tried this with Chrome and even from a Windows with Edge. Same issue. The workaround is:
Currently I have Chorus version 18.x-2.4.6 on Kodi 18.6 (out of the box from LibreELEC 9.2.1 on a RaspBerry 4B). My client is Firefox verson 76 at Linux Mint 19.3.
Ideas about this are more than welcome! Many thanks in advance.
Expected Behavior
Here is a clear and concise description of what was expected to happen:
Actual Behavior
Possible Fix
To Reproduce
Steps to reproduce the behavior:
1. 2. 3.
Debuglog
The debuglog can be found here:
Screenshots
Here are some links or screenshots to help explain the problem:
Additional context or screenshots (if appropriate)
Here is some additional context or explanation that might help:
Your Environment
Used Operating system:
note: Once the issue is made we require you to update it with new information or Kodi versions should that be required. Team Kodi will consider your problem report however, we will not make any promises the problem will be solved.