2017-09-12, 16:47
(2017-09-11, 14:48)noner Wrote: Its definitely one of the dependencies, not sure which one. On relaunch of kodi and reinstall of the skin, all the dependencies get installed correctly, and the skin switches. Its only the first time, and only on Android.
I will go home and check if any of the logs are still there but I doubt it, this was a few days ago, but I can always do an uninstall of everything and try it again
It could be that it couldn't find Marcel's repo, and it froze and crashed because of it. The second time it managed to do so, and everything went as it should?
(2017-09-11, 18:47)repulse Wrote: Sorry to ask here, but as it's a genius place i think i'll get some answer.
Is there any way to play random video at random position ? Like simulate zapping channel on TV...
I've already achieved random movie through a smartplaylist, but not at random position...
I think it might be possible, but at an add-on level. I presume that it can be done through the same mechanism with which Kodi achieves the resume feature. I guess that it would require some non-random values that would simply be selected in a random fashion. In effect, when one would click on an item it would "resume" it from one of the points in time drawn out by the algorithm. This is all pure theory, I've no idea how to do it in Python.
(2017-09-12, 00:15)soufianb Wrote: So I've done that and still same problem. Will include some pictures.
https://drive.google.com/file/d/0B4XsgL5...p=drivesdk
https://drive.google.com/file/d/0B4XsgL5...p=drivesdk
As you can see. Small preview. Blacked out screen. The channels are there if I scroll up and down.
Same problem with non moded version.
Appreciate your help
I've just tested it myself, and it works as it should with the PVR Demo Client. This looks like something strange is happening with the PVR backend. The second image in particular looks as if the video itself cannot distinguish its own borders. It minimises and blackens everything else as if it were also a video signal. As I seem to recall, there were hardware issues with some Nvidia Tegra devices, which disallowed such behaviour, but I'm not sure if that applies here.
I've done some digging that might circumvent that, at least in theory. There should be an update soon containing that potential fix.