• 1(current)
  • 2
  • 3
  • 4
  • 5
  • 7
  •   
v18 Timeshift and NextPVR on the latest Nightlies
#1
Hi All,

I'm using the latest nightly (have tried a few builds over the last week) and i'm finding Timeshifting and NextPVR extremely flaky.

Is there any way of improving the experience?  NextPVR Client Version is 3.3.3.  I'd read there was an official API for Timeshifting, just curious if this has been implemented yet.

I'm experiencing Kodi Hangs when I go backwards and long delays going forward.  Still not sure what the 2nd "Timeshifting Bar" is supposed to represent at this point is all.

Cheers and love both Kodi and NextPVR, so looking forward to the improvements for the upcoming Beta 1 release.
Reply
#2
(2018-07-17, 12:12)deadlast Wrote: I'd read there was an official API for Timeshifting, just curious if this has been implemented yet.
Yes, the NextPVR addon is using the official API for timeshifting. Support for this was implemented a couple of months ago by mikeb8591. Hopefully he'll see your post and be able to look into it for you.
Reply
#3
Here's a good log example of the issue:
https://paste.ubuntu.com/p/cScP9Zjhts/

To replicate this, with 17.6, I can pause a show, come back, press play and skip forward to wherever, or even skip back to wherever and its pretty responsive.

with Kodi 18, If I do the same its very slow to catch-up/respond and If i try and go backwards, kodi usually hangs until it crashes out eventually.

I've also noticed LiveTV in Kodi 18 seems to have noticeable interlacing that I don't notice with 17.6.   Its obviously easy to rollback to 17.6, but hoping I can give usable data to assist in resolving/improving the issues.

Cheers Kodi and NextPVR developers Smile
Reply
#4
and here is a Debugging Level log for the issue:
https://paste.ubuntu.com/p/T9KTDqtKpk/
Reply
#5
I'm experiencing a similar bad experience with V18 as well (7/19).  Using this on a Shield tv with Oreo update installed.  I do not seem to get "disconnected from the tuner", but the streams eventually hang.  Attached is a debug log.  Hope this helps 


https://dl.orangedox.com/nMox4U
Reply
#6
As a follow-up to this, which may show in the logs, everytime I watch live tv, about 5-10 seconds after a channel starts playing, there is a kodi progress bar and and a stutter, then another kodi progress bar followed by a slight longer stutter and then the picture seems to reprocess, sometimes it looks like the picture is good, then after the 2nd stutter, it looks like it loses some/all of its de-interlacing.  After this its usually stable (other than rewinding larger timeframes), but the kodi progress bar pops up at random for seemingly no reason.

See none of this on Kodi 17 FYI, so I don't believe its infrastructure/backend TV config related.  

To clarify, by Kodi progress bar, I means the Progress Circle that appears.
Reply
#7
(2018-07-23, 16:15)mrdally204 Wrote: I'm experiencing a similar bad experience with V18 as well (7/19).  Using this on a Shield tv with Oreo update installed.  I do not seem to get "disconnected from the tuner", but the streams eventually hang.  Attached is a debug log.  Hope this helps 


https://dl.orangedox.com/nMox4U

In your case, it appears the render pipeline stalled, but no further calls were made to the addon for more data.

These lines :

16:34:36.974 T:18446744071921658224 DEBUG: AddOnLog: NextPVR PVR Client: ReadLiveStream:1817 bufsize: 32768
16:34:36.974 T:18446744071921658224 DEBUG: AddOnLog: NextPVR PVR Client: TimeshiftBuffer::Read() 32768 @ 10911744
16:34:36.974 T:18446744071921658224 DEBUG: AddOnLog: NextPVR PVR Client: ReadBytes: returning 32768

represent a completed Read transaction from the addon. This is the last one in the log, but in the next section of log :

16:34:36.975 T:18446744071921658224 DEBUG: CVideoPlayer::SetCaching - caching state 2
16:34:36.975 T:18446744071921658224 DEBUG: CDVDClock::SetSpeedAdjust - adjusted:0.000000
16:34:36.975 T:18446744072018708848 DEBUG: CDVDAudio::Pause - pausing audio stream
16:34:36.975 T:18446744071921658224 DEBUG: CVideoPlayer::SetCaching - caching state 3
16:34:36.975 T:18446744071921658224 DEBUG: CDVDClock::SetSpeedAdjust - adjusted:0.000000
16:34:36.976 T:18446744072018708848 DEBUG: CDVDAudio::Resume - resume audio stream
16:34:36.977 T:18446744071836780912 DEBUG: ActiveAE - start sync of audio stream
16:34:36.983 T:18446744071892842864 WARNING: CRenderManager::WaitForBuffer - timeout waiting for buffer
16:34:36.986 T:18446744071921658224 DEBUG: CVideoPlayer::SetCaching - caching state 0
16:34:36.986 T:18446744071921658224 DEBUG: CDVDClock::SetSpeedAdjust - adjusted:0.000000
16:34:36.986 T:18446744071921658224 DEBUG: CDVDClock::SetSpeedAdjust - adjusted:-0.050000
16:34:36.988 T:1797745008 DEBUG: GLES: Extension Support Test - GL_EXT_texture_format_BGRA8888 YES
16:34:37.038 T:18446744071892842864 WARNING: CRenderManager::WaitForBuffer - timeout waiting for buffer
16:34:37.107 T:18446744071836780912 WARNING: Previous line repeats 1 times.
16:34:37.108 T:18446744071836780912 DEBUG: ActiveAE::SyncStream - average error of 128.135832, start adjusting
16:34:37.167 T:18446744071892842864 WARNING: CRenderManager::WaitForBuffer - timeout waiting for buffer

it starts buffer timeouts without requesting further data from the addon.

You might experiment with trying other renderers, if you have them, or disabling passthru audo stream if you're using that. I've seen both these settings involved in these kinds of errors here (RPI platform).

Thanks!
Reply
#8
Tested again with Alpha 3 with pass through audio and time shift disabled.  Still seeing some lockups on Nvidia Shield running Oreo.  Log file attached

https://dl.orangedox.com/kO1mfV
Reply
#9
Is there anything I can do to help test a few things on my end?  I'd love to help make this as good as it can possibly be.  If there is something to be tried or a new build to test I am ready and willing Smile  Thanks for looking!
Reply
#10
(2018-08-10, 22:39)mrdally204 Wrote: Is there anything I can do to help test a few things on my end?  I'd love to help make this as good as it can possibly be.  If there is something to be tried or a new build to test I am ready and willing Smile  Thanks for looking!
 As an update to this, happy to assist on the Windows 10 x64 side of house and more recently the NVIDIA Shield as well (Got it 2 days ago), experiencing the same issues as mrdally204 where it freezes up.
Reply
#11
(2018-08-06, 16:28)mrdally204 Wrote: Tested again with Alpha 3 with pass through audio and time shift disabled.  Still seeing some lockups on Nvidia Shield running Oreo.  Log file attached

https://dl.orangedox.com/kO1mfV

This bit from the log:

21:14:40.728 T:18446744071828732272 DEBUG: Previous line repeats 8 times.
21:14:40.728 T:18446744071828732272 DEBUG: ActiveAE::SyncStream - average error of 740.681862, start adjusting
21:14:40.814 T:18446744072048580976 DEBUG: AddOnLog: NextPVR PVR Client: ReadLiveStream:1817 bufsize: 16384
21:14:41.115 T:18446744072094693744 DEBUG: Previous line repeats 17 times.
21:14:41.116 T:18446744072094693744 WARNING: CRenderManager::WaitForBuffer - timeout waiting for buffer
21:14:41.136 T:18446744072048580976 DEBUG: AddOnLog: NextPVR PVR Client: ReadLiveStream:1817 bufsize: 16384

is pretty interesting. I think the renderer is saying the a/v is 740 seconds out of sync. If that's correct, I think the timeouts because it's looking for a buffer containing a specific timecode.

The plugin appears to be continuously delivering data during this period, so I don't believe it's the source of this problem.

I see this kind of issue on the Leia RPI build when I use the MMAL (hw) renderer and have passthru audio enabled. Selecting the other hw renderer (OMX) or disabling passthru makes it go away.

Not sure what could be causing it on your platform.

Thanks!
Reply
#12
(2018-08-06, 16:28)mrdally204 Wrote: Tested again with Alpha 3 with pass through audio and time shift disabled.  Still seeing some lockups on Nvidia Shield running Oreo.  Log file attached

https://dl.orangedox.com/kO1mfV

Are you connected via ethernet or wireless, to the backend?

Thanks!
Reply
#13
My media player as well as my network tuners (hdhomerun extend) and NextPVR are all hooked up to gigabit Ethernet.

Thanks
Reply
#14
(2018-08-14, 02:15)mrdally204 Wrote: Hooked up to gigabit Ethernet.

Thanks
 In my case, Gigabit connected from Nvidia Shield to the NextPVR Server.

I'll see if I can capture the debug logs now that I've got a File Explorer in place to transfer the logs.
Reply
#15
Same type of issue here. Lots of choppiness in Kodi using the nextpvr add-on but plays beautifully if I use the standalone app for the hdhomerun
Reply
  • 1(current)
  • 2
  • 3
  • 4
  • 5
  • 7
  •   
 
Thread Rating:
  • 0 Vote(s) - 0 Average



Logout Mark Read Team Forum Stats Members Help
Timeshift and NextPVR on the latest Nightlies00