Closed djp952 closed 6 years ago
I was able to correct this behavior as well as the poor behavior of in-progress recorded TV streams for version 1.2.6. Will leave this out here until I get some feedback and close it if the feedback is positive.
Marking this as closed. In general the functionality worked OK but needed a tweak to better handle a transition that occurs when an in-progress recording finishes on the back end. HDHomeRun RECORD stops sending a "live" stream and sends a "recorded" stream which changes the Content-Range headers.
Not sure if this is the same issue as reported above, but on all of my devices (gen 2 sticks, gen 2 fire tv boxes, and nvidia shield tv) fast forwarding a recorded stream beyond 2x seems to get kodi confused and causes it to take 10 or more seconds to recover from fast forwarding when resuming normal playback. Audio starts right away, but video stays frozen on the last updated frame for 10 seconds or so, then syncs up with the audio and everything seems normal.
I have attached a debug log I captured during a test of this. Not sure how I can help, but I'm willing to do anything to assist in troubleshooting. This is the last thing I need to be able to confidently replace cable boxes with HD HomeRun Primes, Kodi, and the PVR/DVR plugin.
From the SiliconDust forums:
This is probably something that can be improved; the client is currently limiting how far into the future Kodi can request on a seek operation. I believe with some tinkering I can improve this by letting Kodi ask for whatever it wants and let the RECORD engine handle it as best it can. I will also test reporting an infinite length to Kodi for Live TV streams, IIRC that caused a problem at some point which was why I started tracking the "seen" length instead.
The code has changed/improved a lot since the last time I played with this, so I think it's reasonable to mark this as a bug/defect and work on it from that perspective.