EPG update whoopsy

[liteswap]

Mine updates at 0430 - I'm never watching or recording then.

[imilne]

I haven't looked at it, no. I can send you what I've done with the plugin if you wanted to try that...it has its own update time separate from the main one and will (optionally) only run it if no live tv or recordings are active.

I'm surprised you have a similar problem though. Every other tuner I've had has been fine with DVBGuide and npvr/gbpvr.

Iain

[Reddwarf]

I haven't looked at it, no. I can send you what I've done with the plugin if you wanted to try that...it has its own update time separate from the main one and will (optionally) only run it if no live tv or recordings are active.

I'm surprised you have a similar problem though. Every other tuner I've had has been fine with DVBGuide and npvr/gbpvr.

Iain

Normally I wouldn't, but since I have only one dvb-t and one dvb-c tuner left on the computer that has a strong enough signal to get a correct epg... Yes please, I'd like to try it.

[imilne]

Here it is. This is still trial code so I wouldn't recommend anyone else using it unless they wanted to test the EPG functionality. It wasn't really designed to be public.

You'll need to manually add the following entries to C:\Users\Public\NPVR\Plugins\System\System.xml:

Code:

<AutoEPG>2</AutoEPG>
<AutoEPGHour>08</AutoEPGHour>
<AutoEPGMinute>00</AutoEPGMinute>

<AutoEPG> has three values that relate to running an EPG update:

0: don't run
1: run regardless of tuner status
2: only run if the tuners are free, and no recordings are due to start in the next ten minutes

The plugin won't make a wake-up event in Windows for the time set. If you need that you'll have to set one up manually (and make it for a minute or so before the EPG was due to update).

Iain

[Graham]

Here it is. This is still trial code

I stopped using auto EPG yonks ago after problems with the Radio Times website or Internet connection left me with an empty EPG and no recordings. I currently use a manual batch file with a file size test that warns me if the XMLTV file is too small.

If you want to make your plugin even more jazzy, you could add a test for "something" in the UpdateEPG batch file and only do an EPG update in NextPVR if the test is passed. Setting an environment variable might do it or a liitle prog that could be included in the batch file.

[imilne]

If you want to make your plugin even more jazzy, you could add a test for "something" in the UpdateEPG batch file and only do an EPG update in NextPVR if the test is passed. Setting an environment variable might do it or a liitle prog that could be included in the batch file.

The plugin has no interaction with the batch file though. It just asks NPVR to do an update and captures the messages output while it runs.

If you needed to test on filesize, a better option might be to do that in UpdateEPG.bat and then delete/move the file if it's too small. I think (could be wrong) that NPVR will just keep what EPG data it already has if it can't find new stuff.

Iain

[Reddwarf]

Here it is. This is still trial code so I wouldn't recommend anyone else using it unless they wanted to test the EPG functionality. It wasn't really designed to be public.

You'll need to manually add the following entries to C:\Users\Public\NPVR\Plugins\System\System.xml:

Code:

<AutoEPG>2</AutoEPG>
<AutoEPGHour>08</AutoEPGHour>
<AutoEPGMinute>00</AutoEPGMinute>

<AutoEPG> has three values that relate to running an EPG update:

0: don't run
1: run regardless of tuner status
2: only run if the tuners are free, and no recordings are due to start in the next ten minutes

The plugin won't make a wake-up event in Windows for the time set. If you need that you'll have to set one up manually (and make it for a minute or so before the EPG was due to update).

Iain

Thanks, I'll give it a go when I have a spare moment this week.

[Turas]

same problem here. settings are:
<EPGUpdateHour>None</EPGUpdateHour>
<EPGUpdateTime>03:38:00</EPGUpdateTime>
<EPGUpdateEnabled>false</EPGUpdateEnabled>

but wakeup-timer is installed nevertheless:
Timer set by [SERVICE] \Device\HarddiskVolume1\Program Files (x86)\NPVR\NRecord.exe (NPVR Recording Service) expires at 03:34:07 on 04.04.2013.

on my client i don't need any wakeup at all.
would be enough to wakeup my server to update the epg. (or for me it would be even better to only wake the server up once every third day).

an option to set <EPGUpdateTime> to "None" like it was possible for <EPGUpdateHour> would be helpful for me.
<EPGUpdateTime>None</EPGUpdateTime>

br turas

[Zeb]

There was a brief exchange between sub and I regarding the new <EPGUpdateTime> in posts 5-7 of http://forums.nextpvr.com/showthread.php...out-2-6-2& I recall looking at config.xml soon after that; and just as sub indicated, no time had yet been saved. The null value might have been "-" or "--", something like that. I'm sure that sub could say, or any user who has installed 2.6.2 but hasn't yet visited Settings/Misc2. If one was determined, they might try uninstalling NPVR, deleting (or moving/renaming) config.xml, reinstalling, then changing <EPGUpdateHour> to "None" (and changing any other Misc2 settings) by editing the new config.xml. If you must look at Misc2, exit via Cancel or [X] rather than OK. I'm happy with my XMLTV updates personally, and this might not solve the problem or even cause other problems for all I know.

[Turas]

There was a brief exchange between sub and I regarding the new <EPGUpdateTime> in posts 5-7 of http://forums.nextpvr.com/showthread.php...out-2-6-2& I recall looking at config.xml soon after that; and just as sub indicated, no time had yet been saved. The null value might have been "-" or "--", something like that. I'm sure that sub could say, or any user who has installed 2.6.2 but hasn't yet visited Settings/Misc2. If one was determined, they might try uninstalling NPVR, deleting (or moving/renaming) config.xml, reinstalling, then changing <EPGUpdateHour> to "None" (and changing any other Misc2 settings) by editing the new config.xml. If you must look at Misc2, exit via Cancel or [X] rather than OK. I'm happy with my XMLTV updates personally, and this might not solve the problem or even cause other problems for all I know.

thx for the suggestions, but it seems putting >-< or >--< or >-:-:-< is not acceptable. startup of service fails. seems it must have been some other value that you used...