2016-09-12, 08:47 PM
2016-09-16, 03:59 AM
slikvik55 Wrote:I've spent the last few days testing this. Sorry, I missed this earlier I did not try 16.1, but I did install 17b1 for Windows and it did work just fine with Pause Live TV enabled. Thanks again for reporting the issue to the Kodi team
2016-09-21, 07:54 AM
@sub
Is it possible you could chime in here: http://trac.kodi.tv/ticket/16900#comment:3 As I half expected, it's been suggested that its a addon problem and not a Kodi issue (the ticket has been closed). We're now in danger of this being left in limbo and never getting fixed :eek: If you would kindly just point out to him that it's likely not an addon issue (given it works on other platform builds) that would be great. (Unless, of course, his comment about closing the socket when switching to software mode is actually the issue - something that is likely to not happen on Windows) Thanks
2016-09-21, 08:24 AM
slikvik55 Wrote:@subUnfortunately his comment #3 on the ticket doesn't really tell me anything useful, and I've go no idea what's different about Kodi on FireTV.
2016-09-21, 01:51 PM
(This post was last modified: 2016-09-21, 02:30 PM by mrdally204.)
Crap,
I was just coming to let you know a comment was left on this. Keep in mind it's not just Fire TV but all of Android. sub, I am more then willing to test some things for you if you have any interest troubleshooting this issue.
2016-09-22, 08:20 AM
There was the suggestion to see if the issue is repeatable with other PVR backends. I've been testing out MediaPortal, and it does not have any of these channel switching issues that we see with NextPVR on the Fire TV. I know that's not definitive, but it does suggest there is something going on with how timeshifting is being handled by the NextPVR backend and/or addon that isn't playing well with the Android builds of Kodi.
Edit: I have no desire to switch to MediaPortal...it has issues of its own that still make NextPVR the best option for my setup.
2016-09-22, 08:26 AM
Hopefully some developer that has a Fire TV, and uses NextPVR, can use the source code NextPVR addon (available on git) to do some digging and try to work out what's different on this platform. Personally I've got no idea how you'd even build or install a Fire TV build - I know absolutely zero about this platform.
2016-09-22, 08:10 PM
would a wireshark capture be of any benefit? I don't have any coding skills but I can follow a wireshark tutorial Any other tools like this that can capture what is happening that might give more insight ?
2016-09-22, 09:05 PM
sub Wrote:Hopefully some developer that has a Fire TV, and uses NextPVR, can use the source code NextPVR addon (available on git) to do some digging and try to work out what's different on this platform. Personally I've got no idea how you'd even build or install a Fire TV build - I know absolutely zero about this platform. I have a FTV but it uses software or now deinterlacing and is not really a good client for NextPVR. I am also not interested in testing on a platform where forks are prefered wand I can't even use my x-newa pluigin. The comments about Android not working are probably incorrect. As I posted earlier I believe the Kodi problem is the delays in the mpeg2 software deinterlacing, and that seems to be confirmed on the notes the Kodi logs. Looking at the web and necord logs there is a problem in this scenario that kills a tuner that requires a restart but I can't explain how to duplicate it yet. Martin
2016-11-17, 02:00 PM
Just an update on this issue. It appears to be fixed in the latest nightly I tried 11/15. Channel surfing is working once again
|
|