-
-
Notifications
You must be signed in to change notification settings - Fork 30
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Video stop after 1 sec when using Clone Default Skin #66
Comments
Honestly, I've been considering removing that clone skin function entirely. It isn't a proper clone since it seems to move some aspects of the skin around and hide others, and I feel like it's not a good idea to be modifying skins like that. Plus with whatever skin changes have happened between Kodi 18 and Kodi 19, it's likely to have even more weird behavior in the future if it doesn't get some serious attention. There's plenty of third party skins available that support customizing the home screen that I'm just not sure it's worth maintaining this feature, though I'm open to being convinced otherwise. |
Hello, |
Do you have logs of when it fails? I can't imagine how it's possible for a skin to be breaking playback, but this should give a good idea of how. |
Hello, Here are the logs :
|
I have the same problem with recent JellyCon versions, WITHOUT using the Clone Skin: Video playback stops after a second. This happens with 0.4.4 on two different boxes: One is running Kodi 18.9 (Leia, Python 2), the other one runs 19.1 (Matrix, Python 3). In both cases, I see an error like this:
On the Leia box, JellyCon 0.3.1 works fine (there's no 0.3.x for Matrix). I'm running Jellyfin 10.7.5 at the moment. I'm not sure whether the problem might be related to a Jellyfin upgrade in the last weeks. I don't use JellyCon regularly. It feels strange that the movie is played for a few moments (like a second) but then stops. |
Also having this problem when using any skin. No videos play successfully when using JellyCon, they all stop after about a second. Edit: Made a new issue for it. Seems to be caused by starting playback from within context menu |
Interestingly, I have the opposite issue as @krutburken . I can play every item without issues if I play it via the context menu for that item but not if I view the info page and use the play button there. Edit: Here is a full debug log. I'm not sure if the issue started happening after using the clone skin feature once. I didn't try it before using the feature after a fresh install but the log was captured after changing back to the original estuary skin because playback on the cloned skin also didn't work on the info page. (Don't mind the time skip of about 2 hours, I didn't set the timezone correctly) |
So unfortunately, I can't fix this. Or not willing to, take your pick. I've been messing with it for the last few hours and it's not working at all for me on Kodi 19.4. When I try to run it, the only entry in the nav menu I get is 'Addons'. No media is available. The skin cloner works by copying all of the default Estuary files, and then overwriting some of them with customized versions. But the skin files are constantly changing with every Kodi update, so it's a moving target of reverse engineering XML and frankly it's miserable work. Unless somebody else wants to work through it and get it working for Kodi 19 (and we'll have to do it again for Kodi 20 in the future), I'm likely going to remove the skin cloning feature in the next major release. I'm just not able to put forth the time and effort to maintain the skin cloner in it's current form. If somebody does want to work on this, then here's a starting point:
|
Describe the bug
After using the fonctionnality "Clone default skin", when I want to play a video, it starts for a second and then the video stops.
To Reproduce
Expected behavior
It should play the video without problem.
System (please complete the following information):
Additional context
Even when I go back to the old skin, the videos no longer work. I have to uninstall and reinstall Kodi completely.
The text was updated successfully, but these errors were encountered: