NextPVR Issue

[Sven 136]

Or it changed maybe in the last version?

Because before we didn't have that problem...

[sub3 64]

There hasn't been a new NextPVR release in the last 6 months, and as far as I know this stuff hasn't changed even then. 

 

Is it just kingy444 having this issue?

Edited June 21, 2017 by sub3

[UncleJohnsBand 1]

Taking a look now to see if I see anything that hasn't already been covered.....

[UncleJohnsBand 1]

Load the attached to: web\App_Code\Classes  wherever you have your NPVR data files loaded. 

 

Then stop the npvr service, delete all logs, start npvr service, schedule through emby and then post the log files from npvr.  

 

This has debug statements that should help see why it is falling through as a bad recording.

webServiceEPGEvent.zip

[emveepee 132]

@@kingy444

 

You are getting really sparse EPG data for most data. For the channel that returned the error 7184 You got only 7 shows,

 

2017-06-21 15:30:19.180 [iNFO][41] # channelId querystring found from GuideService/Listing: 7184

2017-06-21 15:30:19.188 [iNFO][41] #***

2017-06-21 15:30:19.188 [iNFO][41] #*** Created listing for 7 events in 0.8 seconds.

 

Have you always been able to work with less than one day of data?

 

Martin

Edited June 22, 2017 by emveepee

[kingy444 117]

@@kingy444

 

You are getting really sparse EPG data for most data. For the channel that returned the error 7184 You got only 7 shows,

 

2017-06-21 15:30:19.180 [iNFO][41] # channelId querystring found from GuideService/Listing: 7184

2017-06-21 15:30:19.188 [iNFO][41] #***

2017-06-21 15:30:19.188 [iNFO][41] #*** Created listing for 7 events in 0.8 seconds.

 

Have you always been able to work with less than one day of data?

 

Martin

Sven might have chosen a channel that is a non-XML TV listing one. We unfortunately have poor XMLTV listings in AUS so work with what i have. Most channels are fine and populated for a week

[kingy444 117]

Potentially something to point the issue out
 
XMLTV are downloaded at 7AM and 7PM daily from my available source.
EMBY then ingests these files from NextPVR at 7:30am and 7:30pm
 
This morning around 9am when testing the debug file from @UncleJohnsBand everything was miraculously working again. I undid the changes and everything was still working - go figure.

 

Come home this afternoon and everything is not working again - until after the 7:30pm sync of files - then everything starts working again.

 

I guess the next step would be to test how long after the sync time 8:30, 9:30, 10:30 etc that the error starts occurring, and whether a forced sync of the same XML file fixes the issue - I can't see why this should effect anything though.

 

Any ideas? The EPG doesnt change that much in those 12 hours to start throwing errors. 

 

edit: note that the epg source is only updated every 12 hours too - so there would be no change in files if i ran a sync at say 1pm

Edited June 22, 2017 by kingy444

[Sven 136]

It shouldn't matter for the plugin. You do the mapping at NextPVR level... As we don't support anything else. Except the EmbyTV itself...

But with the plugin we always use the EPG from nextpvr... So it can't be any different EPG numbers...

 

It's indeed weird behavior.... 

[emveepee 132]

No matter how many times Emby makes requests, the EPG data NextPVR only gets the data from the source once every 24 hours and you have it setup to happen at 12pm. That means from 12pm until 7:30pm Emby and NextPVR will be out of sync and you won't be able to record even if live tv continues work The rest of the time will use the 12pm DVB and 7:30 am xmltv data.

 

Assuming you choose 12pm to get as much data in the evening as possible, it would make more sense to download your xmltv source closer to the NextPVR update time, and then follow that with the Emby download also once a day.

 

You might want to consider alternative EPG sources, have you considered Schedules Direct?

 

I have confirmed that the log message

 

2017-06-22 09:02:14.915 [DEBUG][29] Unknown schedule record

 

occurs when the EPG ID is not valid and NEWA returns a 404

 

Martin

Edited June 22, 2017 by emveepee

[sub3 64]

Yeah, Martin is correct. You have the situation where Emby has stale data, and (for example) it's asking NextPVR to record show ID 12345, but 12345 no longer exists in the database, 

 

You'd be best to have NextPVR update the EPG at some early hour like 3:00am, and have Emby pull in the listings from NextPVR soon after that (like 3:30am). Just one a day is probably enough, and avoid trying to update the EPG in primetime like 7pm. 

Edited June 22, 2017 by sub3

[kingy444 117]

XMLTV are downloaded at 7AM and 7PM daily from my available source.

EMBY then ingests these files from NextPVR at 7:30am and 7:30pm

 

When i said this i meant i am already doing extra syncs

[sub3 64]

I'd get rid of those, and only do a single update about 15-30 minutes after NextPVR is scheduled to do its overnight EPG update. Ideally set NextPVR to do it's EPG update well away from any time you might be recording. (ie, like 3am)

 

The problem was occurring between the times NextPVR updated it's EPG (12PM) and the time Emby reloaded it's EPG from NextPVR (7PM). During this time Emby would had stale show data, with show IDs that no longer match the real shows in the database. (at least that would be with XMLTV or DVB EPG...Schedules Direct works differently and unlikely to have the same issue)

Edited June 22, 2017 by sub3

[kingy444 117]

so i tested at 6:30 this morning - no issue. 11 hours after the epg update, ill try around 5-6 pm today aswell. perhaps from what your saying at 1pm as well?

 

Why would this make a difference when the same XML data is being loaded at 7:30 and 12pm?

 

i forgot to mention that after i download the updated epg files at 7am, i also do a force update of the nextpvr epg - hence leaving till 7:30 for emby to do the sync. why would we doing less epg updates be preferable? wouldn't keeping the epg up to date as possible be the best solution?

[sub3 64]

Why would this make a difference when the same XML data is being loaded at 7:30 and 12pm?

 

Ok - let me explain in more detail why you should do the Emby update just after the NextPVR EPG update.

 

(below relates to using XMLTV or DVB EPG in NextPVR)

When NextPVR updates it's EPG it effectively deletes all the listings that are in the database, and replaces it with the new EPG data. When it does this each show is allocated the next show ID. So...at 7PM tonight might be NCIS, and it's allocated ID 12345.

 

At some point after that Emby is pulling in the NextPVR EPG data. It then also knows there is a show called NCIS at 7PM tonight, with a show ID of 12345.

 

If NextPVR then updates EPG again, 12345 is deleted when the new EPG data is inserted. NCIS at 7PM is still in the new EPG data, but it gets a new ID, like maybe 23456.

 

If Emby hasn't refreshed its data, and you try to schedule a recording for NCIS, it'll effectively say to NextPVR "record show 12345", and NextPVR is return "sorry, I don't have a show 12345". 

 

So... to minimize the risk of this happening, just make sure Emby updates it's data just after NextPVR has updated EPG. This way, Emby will have the correct show IDs, and you won't encounter the situation described above. 

Edited June 22, 2017 by sub3

[sub3 64]

As mentioned you're also best to keep the EPG update time away from any time you're likely to record. Most people do it in the middle of the night, when it's all infomercials. 

 

NextPVR is only updating the EPG once per day (in a standard setup), so there is no benefit in updating the EPG in Emby multiple times a day. 

Edited June 22, 2017 by sub3

[kingy444 117]

As mentioned you're also best to keep the EPG update time away from any time you're likely to record. Most people do it in the middle of the night, when it's all infomercials. 

 

NextPVR is only updating the EPG once per day (in a standard setup), so there is no benefit in updating the EPG in Emby multiple times a day. 

 

Updating away from peak times makes sense with the description of clearing the DB.

 

is there any benefit in a situation such as mine where i am forcing nextpvr to update more often? Ignoring the fact that the epg gets wiped, say i ran the sync at like 10am/10pm? Would be great if we had scheduledirect but unfortunately no AUS service.

[sub3 64]

is there any benefit in a situation such as mine where i am forcing nextpvr to update more often? Ignoring the fact that the epg gets wiped, say i ran the sync at like 10am/10pm? 

 

Why are you trying to update more than once a day? Most people are happy with once a day. 

 

What capture device are you using? ie, if it's a digital tuner, you should be able to get multiple days of listings using the DVB EPG, without having to worry about xmltv. 

[kingy444 117]

hdhomerun, think its more of an AUS thing but my dvb listings dont seem to be that great

[sub3 64]

So you're using xmltv instead, and they're giving you good, multi-day listings? If that's the case, there is unlikely to be any value in updating the EPG more than once a day. 

[emveepee 132]

Actually kingy444 uses a mix of DVB and xmltv EPG updates, the DVB ones are not great which is why I suggested Schedules Direct.

 

Martin

[kingy444 117]

Actually kingy444 uses a mix of DVB and xmltv EPG updates, the DVB ones are not great which is why I suggested Schedules Direct. Martin

 

@emveepee I would love Schedules Direct - Unfortunately not enough demand atm for AUS based service from them. Unless you know something I dont 

[kingy444 117]

Also 3:40pm and it seems to be broken again with the last sync happening at 7:30 this morning (test at 8 am worked fine)

 

Run a manual "Refresh Guide" task in emby to sync the file from 7am again, Even though it is the same data being synced - the same recording now works...

 

While the approach of doing less syncs makes sense, it appears that resyncing fixes the issue? Any ideas now?

[Luke 42077]

@@kingy444 I think what they are trying to tell you is that you have two pieces of software that need to refresh their data at various times, so you're going to need to manage that, making sure next pvr refreshes it's data before emby.

 

@@pir8radio @@Sven this topic re-inforces the idea of turning the next pvr plugin into a dumb tuner source and just having emby manage the guide + dvr features.

[Sven 136]

@@Luke that's indeed something to think about...

[kingy444 117]

@@Luke

I get the managing the sync, which was why i allow the 30 minutes differencefrom nextpvr import to emby ingestion

 

But i feel its strange that while emby works fine at 8am after the 730am ingestion it doesnt wlrm at 3pm. Then resyncing that same file from 730 makes the recordings work again

It shouldnt make any difference because the nextpvr epg hasnt changed in those 8 hrs

 

Does this make sense?

I don't get why syncing the exact same info into emby makes it work again