The last section that seems to set this true is the onNewIntent section. In addition, that may not be the code where the above "Visible behind request" gets triggered since in both the visible and invisible play the log immediately prior is not a DEBUG level log. It appears to be caused by either resuming from a screensaver or on playback start. The latter seems to apply equally to both the video that works and the video that doesn't. The XBMC code that logs that message is in XBMCApp.cpp line 443. I don't yet have any samples of affected files that can be shared (part of the incomplete nature of this report.) Transcoding the video to the SAME CODEC with ffmpeg results in a playable file. Copying the video of affected files verbatim causes the problem to follow the video. This does not seem to be format or codec specific. On some videos that used to play fine, Kodi 18.2 will seem to play them, but no video appears.įor as-yet unknown reasons, in the debug log on affected videos I get:ĭEBUG: GOT ANNOUNCEMENT, type: 1, from xbmc, message OnPlay I have been unable to collect enough information for a proper bug report, but what I've found so far is interesting enough that I thought I'd see what everyone else thought. So if this "CWebServer: Stopped" is the reason why apps like Yatse wont work any longer, why is the WebServer stopping and why not restarting again?
#ADVANCED MCE REMOTE MAPPER OPEN EXE MOVIE#
> In this situation I would assume that my boy turned on TV via traditional remote control and then started a movie also via CEC (without Yatse etc.).
Out of nowhere, some services stopped suddenly (also WebServer). When I then just restart Kodi GUI (it is an option in Kodi 18.2 under CoreElec 9.0.2 on my Odroid C2), after restart it works again. However I still can use traditional remote control (CEC) and use Kodi.
#ADVANCED MCE REMOTE MAPPER OPEN EXE ANDROID#
Sometimes, Yatse (my android remote control app) tells me that Kodi is offline (not reachable).
0 kommentar(er)
