Skip to content
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

Workaround script for Intel 3,4 & 5th Gen resume with h.265 #147

Closed
pbathuk opened this issue Jan 2, 2018 · 2 comments
Closed

Workaround script for Intel 3,4 & 5th Gen resume with h.265 #147

pbathuk opened this issue Jan 2, 2018 · 2 comments

Comments

@pbathuk
Copy link

pbathuk commented Jan 2, 2018

Hi,

Not sure if this sits here, but I use plex for kodi ALOT, like all my media needs (except live TV), however because I have a 4th Gen intel NUC there is a known issue where by resuming a h.265 file will crash kodi, plex for kodi, because it uses the same video engine, is also affected.

There is a simply workaround that can be used to get around this, I have implemented it in my player.py (from developer branch) and wanted to share, incase others have the same issue.

It requires : import time as it sleeps the script for 5 seconds, to ensure that the video has started.
Then its a simply change to the below def:

def playVideo(self, video, resume=False, force_update=False, session_id=None, handler=None):

Changing the bottom line to :

  self._playVideo(0, force_update=force_update)
  if resume:
    time.sleep(5) 
    util.DEBUG_LOG('player skipping to resume offset')
    self.handler.seek(video.viewOffset.asInt())

I hope this helps some people.. the same could be implemented into kodi, but I am not sure how to edit that code yet...

Feel free to close this down if wrong / or delete etc.
Would be interested to see if there is a smarter way todo the above to fix the above issue (referenced here: )

https://forum.kodi.tv/showthread.php?tid=248859

(edited code formatting - ruuk)

@ruuk
Copy link
Contributor

ruuk commented Jan 6, 2018

That thread mentions Kodi 15.2. Currently only Kodi 16+ is supported for the add-on. What version of Kodi are you running?
It is possible the next release of the add-on will fix the issue, because I have added some changes to the timing of the initial seek. Other than that it's really something that needs to be fixed in Kodi if it's still an issue in the current version.

I'm closing this, but I'm still interested to know your Kodi version.

@ruuk ruuk closed this as completed Jan 6, 2018
@pbathuk
Copy link
Author

pbathuk commented Jan 6, 2018

Hey,
It actually impacts 17.x as well, I am running 17.6 and have the issue.
Thanks for looking at it.

Fyi the issue is actually a driver issue, which intel have accepted, however they won't fix it on the older gen models due it being out of development cycle, therefore I build this to work around that Dev bug.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants