Kodi v18 (Leia) testbuilds

[jakenl]

(19th Feb, 2019 05:59 AM)Nachteule Wrote:  

(19th Feb, 2019 05:17 AM)jakenl Wrote:  Thanks, I found the updates today and installed them. After a reboot (just to be sure), I ran an audio album. However, it still has the same behavior as described before. I checked all symptoms, including a pause-play after 25 minutes into the album: again after 5 minutes the screensaver thing. The update doesn't seem to solve the issue.

Hmmm, seems I misunderstood you completely. Probably I did not have read your previous post correctly, bc there was a screensaver issue with an external script.

Now I have read your post many times, but unfortunately I do not understand exactly what the problem is

Ouch, bad description from my side, by reading your response.

I will try again:
While playing audio/video, Kodi shares that status, so other, external, devices can interact with that.

Kodi 17:
Play an audio album or movie: During the whole album/movie, the status would be 'audio' or 'video'. Good

Kodi 18:
Play movie: during the whole movie, the status remains 'video'. Good
Play audio: after 5:00 minutes, Kodi status broadcast changes to 'screensaver' (while the audio keeps playing, with the littlest interruption at the 5:00 minute sign). This status remains until the next track at some point after 5:00 minutes will start. After that the Kodi status will remain 'Audio' until the end of the whole album, no matter how long it takes. (During that whole album the screen will be 'dim', so that part is OK, just it's broadcasting is wrong
Pause Audio and restart: 5:00 minutes after restart, the screensaver status becomes active again. Also reset to 'Audio' by the first new track after those 5 minutes.

After the audio album is finished, the Kodi status should change to screensaver indeed, but it doesn't do that, while the actual screensaver (dim) is 'on'.

Since I use the 'screensaver' status in Domoticz to decide whether my receiver may be turned off, it did so promptly after these 5 minutes

Don't hesitate to ask again. The issue is easy to 'experience', but needs a lot of words to describe. Sorry for that.