TV Guide and playback problems

[DParsons 4]

I've got the logs with dates from this afternoon since I've been here testing this out and a screenshot of the CPU event. The CPU event happened again today, I was switching channels a lot remotely until it stopped responding quickly. I was trying to make it happen as I don't usually switch channels all of that much or use it for all that long remotely on average. So it looks like I can make that happen but this is the first time I was able to make it happen. It was exactly the same as I described before, it just started to work again properly about five minutes before this post.

logs.7z

Edited November 26, 2016 by DParsons

[Luke 37008]

What CPU event are you referring to? What is NRecord.exe? I do notice some timeouts in there when attempting to contact the next pvr web service.

[DParsons 4]

It is the issue I had posted on the NextPVR forum. Link below.

 

http://forums.nextpv...0827#post510827

 

nrecord.exe is the exe file nextpvr uses when recording. This happens only when streaming live tv with emby and nextpvr as the dvr backend. 

Edited November 27, 2016 by DParsons

[emveepee 112]

I think the Emby dev's need to figure out why they are spamming the server with calls to the GetTimersAsync() function
 

2016-11-26 13:43:36.2343 Info HttpClient: HttpClientManager POST: http://localhost:8866/public/ManageService/Get/SortedFilteredList?sid=0066ce8b4830424182569417f10dc712
2016-11-26 13:43:36.3243 Info App: [NextPvr] Start GetTimer Async, retrieve the 'Pending' recordings
2016-11-26 13:43:36.3243 Info HttpClient: HttpClientManager POST: http://localhost:8866/public/ManageService/Get/SortedFilteredList?sid=0066ce8b4830424182569417f10dc712
2016-11-26 13:43:36.3923 Info App: [NextPvr] Start GetTimer Async, retrieve the 'Pending' recordings
2016-11-26 13:43:36.3923 Info HttpClient: HttpClientManager POST: http://localhost:8866/public/ManageService/Get/SortedFilteredList?sid=0066ce8b4830424182569417f10dc712
2016-11-26 13:43:36.4563 Info App: [NextPvr] Start GetTimer Async, retrieve the 'Pending' recordings
2016-11-26 13:43:36.4563 Info HttpClient: HttpClientManager POST: http://localhost:8866/public/ManageService/Get/SortedFilteredList?sid=0066ce8b4830424182569417f10dc712
2016-11-26 13:43:36.5253 Info App: [NextPvr] Start GetTimer Async, retrieve the 'Pending' recordings
2016-11-26 13:43:36.5253 Info HttpClient: HttpClientManager POST: http://localhost:8866/public/ManageService/Get/SortedFilteredList?sid=0066ce8b4830424182569417f10dc712
2016-11-26 13:43:36.5953 Info App: [NextPvr] Start GetTimer Async, retrieve the 'Pending' recordings
2016-11-26 13:43:36.5953 Info HttpClient: HttpClientManager POST: http://localhost:8866/public/ManageService/Get/SortedFilteredList?sid=0066ce8b4830424182569417f10dc712
2016-11-26 13:43:36.6634 Info App: [NextPvr] Start GetTimer Async, retrieve the 'Pending' recordings
2016-11-26 13:43:36.6634 Info HttpClient: HttpClientManager POST: http://localhost:8866/public/ManageService/Get/SortedFilteredList?sid=0066ce8b4830424182569417f10dc712
2016-11-26 13:43:36.7294 Info App: [NextPvr] Start GetTimer Async, retrieve the 'Pending' recordings
2016-11-26 13:43:36.7294 Info HttpClient: HttpClientManager POST: http://localhost:8866/public/ManageService/Get/SortedFilteredList?sid=0066ce8b4830424182569417f10dc712
2016-11-26 13:43:36.7964 Info App: [NextPvr] Start GetTimer Async, retrieve the 'Pending' recordings
2016-11-26 13:43:36.7964 Info HttpClient: HttpClientManager POST: http://localhost:8866/public/ManageService/Get/SortedFilteredList?sid=0066ce8b4830424182569417f10dc712 

This is not a light call, to poll there are better choices, but that 700ms frequency seems too high.

Martin

Edited November 30, 2016 by emveepee

[jordy 284]

Hey @@Luke, I'm still seeing a 1hour time difference between the actual time and the TV Guide.

 

I have checked that the time/Date settings on both the server and Phone are correctly set and are accurate, but the TV Guide on Android is 1 hour behind. I have tried all combinations of date and time setting on the phone but the guide always shows 1 hour early - unless I manually change the time backwards by 1 hour on the phone, then the guide time matches the phone. I'm wondering if its something to do with Daylight savings time here in Aus.