@hevet
Currently this is the case, a reset is required for the extended volume configuration to work. The audio object is only configured once at startup.
I'll have a look at the configuration description maybe there is an inaccuracy there and correct it if I can, maybe even in the version I'm already testing with full websockets.
As for the problem of titles, I have not noticed it at home. They are displayed correctly, unless the station uses a strange character coding, then "bushes" appear in place of Polish characters. If the station broadcasts a long "stationstext", it is scrolled and you have to wait a while.
What browser are you using? If you have many tabs open, Chrome, for example, often puts the tabs to sleep and then java script and websocket no longer work after a while.
Currently this is the case, a reset is required for the extended volume configuration to work. The audio object is only configured once at startup.
I'll have a look at the configuration description maybe there is an inaccuracy there and correct it if I can, maybe even in the version I'm already testing with full websockets.
As for the problem of titles, I have not noticed it at home. They are displayed correctly, unless the station uses a strange character coding, then "bushes" appear in place of Polish characters. If the station broadcasts a long "stationstext", it is scrolled and you have to wait a while.
What browser are you using? If you have many tabs open, Chrome, for example, often puts the tabs to sleep and then java script and websocket no longer work after a while.