nPVR stopped recording and cannot delete files (but can watch)

[dshoup]

Subject pretty well describes the issue...I can watch anything but a couple days ago nPVR stopped recording and I can no longer delete things that had previously recorded. Several recordings still show up under pending recordings even though they are days old. This all appeared to start when I found we had an over the air channel that changed frequency. I re-scanned to get the new frequency and tried to edit the old channel to match the new channel frequency. I apparently have screwed things up and now cannot figure out how to fix it. I've attached logs. Can you suggest the way to get things back to normal?

[Graham]

Can you suggest the way to get things back to normal?

The nrecord.log has ...

2018-11-26 08:06:58.364 [ERROR][10] Unexpected error parsing EPGEvent xml: System.NullReferenceException: Object reference not set to an instance of an object.
at NUtility.EPGEvent.Parse(String xml)
2018-11-26 08:06:58.364 [ERROR][10] xml:
<Event>
<OID>0</OID>
<Title>Movies-kids</Title>
<SubTitle>Madagascar</SubTitle>
</Event>
2018-11-26 08:06:58.366 [ERROR][10] Unexpected error parsing EPGEvent xml: System.NullReferenceException: Object reference not set to an instance of an object.
at NUtility.EPGEvent.Parse(String xml)
2018-11-26 08:06:58.366 [ERROR][10] xml:
<Event>
<OID>0</OID>
<Title>Movies</Title>
<SubTitle>Jungle Boy</SubTitle>
</Event>

Suggesting the database is muddled.

Plus npvr.log has ...

2018-12-05 21:13:19.542 [ERROR][1] TV Listings: error reading settings from database: Could not load file or assembly 'System.Data.SQLite, Version=1.0.65.0, Culture=neutral, PublicKeyToken=db937bc2d44ff139' or one of its dependencies. The located assembly's manifest definition does not match the assembly reference. (Exception from HRESULT: 0x80131040)
2018-12-05 21:13:19.542 [DEBUG][1] TV Listings: Exception details: System.IO.FileLoadException: Could not load file or assembly

First and foremost ... make copies of all of the recording backup xml files in the NextPVR data folder ... and make a copy of npvr.db3 ... just in case

Rerunning the installer (without doing an uninstall) might fix the missing "file or assembly" ... Clicking Empty EPG and then Update EPG in NextPVR Settings might tidy the database (but I suspect it is records of previous recordings that are broken).

[dshoup]

Thanks Graham...a reinstall fixed it! One quick question though. Is there any easy way to transfer/edit old recurring recordings that used the old channel frequency to now use the new channel? I think this is where I screwed things up last time as I renamed the newly found version of the channel to the old channel and put "old" at the end of the old channel name...apparently scrambling my database in the process. I have moved all currently airing shows manually by creating new recurring programs and deleting the old, but there are a handful that are not currently in my listings (air during the summer time)...any way to set those up as recurring recordings on the new frequency or do I just need to wait until they appear in a TV listing some time in the future?

[Graham]

Is there any easy way to transfer/edit old recurring recordings that used the old channel frequency to now use the new channel?

The quickest and easiest way to handle frequency changes is to do nothing, absolutely nothing.

The record in the database for the, for example, series recording says "record on channel with an id of N" where N is a value in the database that points (indirectly) to a record for a channel and the channel record holds the tuning info for the channel.

NextPVR will keep on keeping on and will record on the channel with an id of N using whatever tuning info is in the database for that channel at the time of the recording.

[mvallevand]

Graham I'm not sure I follow. With an atsc channel is changed a new scan is required which creates a new channel ID so N changes.

Martin

[Graham]

Graham I'm not sure I follow. With an atsc channel is changed a new scan is required which creates a new channel ID so N changes.

Ok ... I stand corrected ... I thought that if only the tuning data changed then the row in the channel table did not change so no change to the oid so nothing needed to be done.

[mvallevand]

ATSC actually has two channels the display channel and the frequency channel. I think you are correct with HDHR mode tuners when the display channel stays the same doing nothing is okay. The BDA mode doesn't store the display frequency and I am not sure if sub does anything to map tsid when they stay the same. Since about 1/2 the US channels are changing we probably will find out.

A sqlite replace comment probaby would work for technically inclined

Code:

update recurring_recording
set match_rules = replace(match_rules,'<ChannelOID>old</ChannelOID>','<ChannelOID>new</ChannelOID>')

Martin