Upon starting a livetv, the skin boolean Player.HasAudio is true, until livetv begins playback. Then Player.HasVideo becomes true. For me this is literally 1sec.
Depending on your network setup and speed of the backend, this time would likely increase.
A couple of issue in kodi;
1. Start a livetv channel, while that is playing in the background go into the pvr radio section and play a channel. Kodi shows the VideoFullScreen.xml for an audio only stream.
1. Start a radio channel, while that is playing in the background go into the livetv section and play a channel. Kodi shows MusicVisualisation.xml for about two second then switches to VideoFullScreen.xml.
Something seems a bit off on how the Player.HasAudio and Player.HasVideo booleans are filled when beginning playback. Not sure if this is a kodi or backend issue.
I have tried this both NextPVR and Mediaportal backends.
If you drop this custom overlay in any skin xml folder you can see the values being filled as you start live tv.
https://1drv.ms/u/s!AmyR0RLRGBmugrsiTJxE...w?e=nDH4J3
I could likely find some sort of skin workaround, but i really think the issue is in the backend or kodi core.
Depending on your network setup and speed of the backend, this time would likely increase.
A couple of issue in kodi;
1. Start a livetv channel, while that is playing in the background go into the pvr radio section and play a channel. Kodi shows the VideoFullScreen.xml for an audio only stream.
1. Start a radio channel, while that is playing in the background go into the livetv section and play a channel. Kodi shows MusicVisualisation.xml for about two second then switches to VideoFullScreen.xml.
Something seems a bit off on how the Player.HasAudio and Player.HasVideo booleans are filled when beginning playback. Not sure if this is a kodi or backend issue.
I have tried this both NextPVR and Mediaportal backends.
If you drop this custom overlay in any skin xml folder you can see the values being filled as you start live tv.
https://1drv.ms/u/s!AmyR0RLRGBmugrsiTJxE...w?e=nDH4J3
I could likely find some sort of skin workaround, but i really think the issue is in the backend or kodi core.