Scheduled EPG Update from DVT stream Partly Fails and Deletes Existing Entries

[ralphy]

I have what seems to be a similar problem to http://forums.nextpvr.com/showthread.php...dates-fail, but rather than hijack that thread, I thought I'd post separately.

Until recently returning to Australia, I was using TVxb and updateEPG.bat to populate the EPG without issues. However, now that the EPG is within the DVT stream and I don't use Pay TV, my UpdateEPG,bat file is now empty.

Whilst I can update the EPG manually from the System plugin, and can also have individual channels update when watching during LiveTV, the auto-update of the EPG at 5AM results in many entries of the EPG being cleared with 'no show details'.

Attached are extracts of NRECORD and NVPR logs around the times of the automatic update (5AM) , and the manual update (11:14AM). The only thing that seem significantly different is that the 5AM update doesn't report saving as many listing at the manual update does (eg auto update reports in NRecording.log only a handful of listings saved, whereas the manual update reports in NPVR.log hundreds of listings being saved)

I note that the logs report "Asking NDigitalHost to start: c:\devxxxxxx\null.ts". I do not see this file in the c: folder, however, maybe this gets cleaned up.


Yes, I know I am a number of versions out of date (2.5.5), but my machine spec's are starting to age (incl XP), so I'd like to stick with an older version and the assumption that resource requirements may be less. There must be something unique about my setup, as I can't believe this is a bug in NPVR 2.5.5. However, if this is indeed a bug, then I guess I'll need to try a newer version.

[Lao Pan]

Whilst I can update the EPG manually from the System plugin, and can also have individual channels update when watching during LiveTV, the auto-update of the EPG at 5AM results in many entries of the EPG being cleared with 'no show details'.


Yes, I know I am a number of versions out of date (2.5.5), but my machine spec's are starting to age (incl XP), so I'd like to stick with an older version and the assumption that resource requirements may be less. There must be something unique about my setup, as I can't believe this is a bug in NPVR 2.5.5. However, if this is indeed a bug, then I guess I'll need to try a newer version.

Probably a wrong assumption - there have been a multitude of bugs fixed between version 2.5.5 and version 3.2.9, in fact there have been at least 10 since 3.2.9 was released!

to quote Johnsonx42's excellent sticky thread:

These updated files represent the latest version of NPVR code, and may include other changes not documented, so your problem may already have been fixed. Also, other later patches you may find posted by sub may fail if all your NPVR program files are not up to date. (no, it is not necessary to install any patches before upgrading to a new release of NextPVR - unless otherwise stated, you can upgrade from any release of NextPVR to any later release).

I don't think there are any more resources used by 3.2.9 - apart from requiring .net4 to be installed - newer versions have probably become more efficient with maturity.

The only thing that I would suggest, is to untick the update epg during live TV setting - I think this still has bugs for a lot of people.

[ralphy]

The only thing that I would suggest, is to untick the update epg during live TV setting - I think this still has bugs for a lot of people.

After two overnight updates, looks like this configuration option (in misc) was the culprit. Thanks!

[Nistrod]

There was a problem like this some time ago (http://forums.nextpvr.com/showthread.php...date/page8) that was solved by unticking Use Out-of-process Digital Recording (on the Recording tab).
If the problem recurs, try that.