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
Dropped frames #209
Comments
I've responded to the thread. Doesn't look like an addon issue to me. |
Opening a stream in VLC also works fine so it's an issue of the combination Kodi + addon. As I understand from the thread something has to be changed in the addon? |
I'm not sure yet, I'd have to test it myself. It's odd that no one else has reported the issue. |
verified, reverting xbmc/xbmc@5cadf11 |
@FernetMenta ^^^ ? |
@ksooo I already mentioned this. Don't call SetSpeed on the backend if speed did not change |
I'd prefer core not hammer on client telling it to SetSpeed over and over when it did not change :) |
@FernetMenta I agree to what @MrMC said. Changing the add-on to not call the backend if nothing has changed is nevertheless a good idea. But I would like if core could be optimized as well. |
I would rather kick this hack completely out of core. This is a very specialized behaviour player should not bother with. Only a few network streams require to be paused when you stop reading for a longer period. Ideally this behaviour is handled by demuxer/inputstream itself. |
Another option would be to ignore SetSpeed requests in tvheadend itself if the speed hasn't changed, but for backward compatibility I guess we'll have to do it in the addon. I'll try to whip up a PR. |
I already submitted a pr to kodi |
Verified xbmc/xbmc#9555 works on slow tvh pvr servers. Someone needs to verify that the reason for xbmc/xbmc#3377 is still ok. |
@FernetMenta thanks a lot! @Snippo in the future, never trust @fritsch when he says something is tvheadend's fault. He'd blame his cold coffee on it if he got the chance ;-) |
I have the TVHeadend server local to the client so that makes no difference. However, I get problems only after like 30 seconds. Maybe it happens sooner for remote clients. @Jalle19 Haha ok. I'm glad it got solved. Thanks. @FernetMenta Is this also fixed in your fork? Because I believe the VAAPI build is based on that? |
what ? no love for me for dogging it down :) |
@Jalle19 my ratio is still arround 90% - meaning: 90% of the bugs are in deed tvh bugs, measuring over the past 4 years. But I am happy that I am wrong this time, cause it means your software gets better and better :-) |
@MrMC Thanks to everyone who helped ;). Without you it would still be a "TVHeadend bug" haha. @fritsch Any clue when it gets added to fernet's branch? At the moment I'm still using a build of 2 weeks ago but I'll update when this bug fix is added. Also, I compiled it myself from fernet's branch, this makes no difference right? (I'm using Arch linux) |
fritsch suggested it might be an issue with TVHeadend, but I think the problem might be in the addon.
The stable version of Kodi works without dropped frames, but using the latest nightly (+addon) there are a lot of dropped frames when watching Live TV.
The relevant logs can be found in this post: http://forum.kodi.tv/showthread.php?tid=231955&pid=2288583#pid2288583
Also, TVHeadend doesn't show any errors or other unexpected behaviour.
The text was updated successfully, but these errors were encountered: