Frequency updating challenge

[pabaxt]

This probably explains what happened, but not why my recent rescan did not pick this up:

13th January 2026
25: U&W moves from COM6/ArqB to COM4/SDN. The old copy of this channel appears on channel 791 after retuning.
74: U&Dave Ja Vu moves from COM4/SDN to Local/Comux. Limited UK coverage. You may not be able to receive this channel.

I deleted the channel from the Hauppage device, rescanned, and then just added that channel, which now looks like it has the correct frequency and SID. Dave JaVu will also need to be done. I will see if I can write an SQL query to detect this issue in the future, but clearly, my general rescan routine is wrong.

[Bobins]

We're working on some improvements to the NPVR channel update process for a future release.

Knowing that things have changed is always tricky but we should be able to automate the way NPVR handles some of the changes.

Ray

[pabaxt]

We're working on some improvements to the NPVR channel update process for a future release.

Knowing that things have changed is always tricky but we should be able to automate the way NPVR handles some of the changes.

Ray

Thanks for the update. Is there guidance on the 'best' way to perform a rescan without losing scheduled recordings whilst capturing multiplex or SID changes? I find that I don't always get name changes, but I recently found that it's simple to change the channel name to match the Freeview TV guide.

[mvallevand]

A rescan itself shouldn't lead to missed recordings since channels are deleted during a scan it is more a question of understanding what the scan does.

The possible risk with DVB-T and ATSC

- you are able to receiving multiple transmitters and you pick a weaker one and NextPVR doesn't see it as a duplicate.
- you delete channels after the scan and delete the wrong channels
- you don't sync all the mapped channels after the scan so not all tuners are capable of recording.
- your channels weren't in sync to begin with, this is actually more common than you think.

Perhaps the reason for earlier failures had nothing to do with the scan but the you interpreted it that way.

I do always backing up your database before a scan but since it is a database you should be doing this daily anyway.

If you are concerned, untick all and tick just that channel and only it will work.

Martin

[pabaxt]

Thanks.

I discovered this morning that a scheduled U&W recording (scheduled before I updated the channel) caused the NPVR service to crash (recodings stopped, no scheduled recording started). I have never had this before in years of using NPVR. As a precaution, I deleted and re-added the recording on this channel. I scheduled an in-progress programme, and this appeared to work fine, but again this caused the service to become unresponsive (it still showed as running in Service Manager) . Is there a log that I could attach to assist with diagnostics? I also noted that I had not merged the two instances of channel 25 in the list (1 for Hau, 1 for HDHR), so I have now done this.

[Edited post as originally I thought that immediate recording was working, but it seems to have crashed later]

[mvallevand]

Certainly update the zipped logs and we can log to see what might have happened. Look in the Windows Event viewer too and copy any relevant notes into a message. I am pretty rough on my test database using database from many users and it is truly rare to see the service actually crash.

Martin

[pabaxt]

The in-progress recoding ran for about 35 minutes before crashing the service, so this is truly strange. Attached are the logs (after service restarted).

[pabaxt]

If it helps, I can try to find a time when nothing else is scheduled then schedule a U&W recording, and grab the logs before I restart the service.

[mvallevand]

Unfortunately the server logs stopped well before the recording finished, but it doesn't look like a tuner error. Did you look in the event viewer?

Martin

[pabaxt]

IN teh event viewer I get

Faulting application name: NextPVRServer.exe, version: 1.0.0.0, time stamp: 0x696f0000
Faulting module name: unknown, version: 0.0.0.0, time stamp: 0x00000000
Exception code: 0xc0000005
Fault offset: 0x00007ff8ce783b3e
Faulting process id: 0x69FC
Faulting application start time: 0x1DCE757535F69C2
Faulting application path: C:\Program Files\NextPVR\NextPVRServer.exe
Faulting module path: unknown
Report Id: 35b43e67-e2fe-4479-8eb8-8eeebde2da52
Faulting package full name:
Faulting package-relative application ID:

and

Application: NextPVRServer.exe
CoreCLR Version: 8.0.2426.7010
.NET Version: 8.0.24
Description: The process was terminated due to an unhandled exception.
Exception Info: System.NullReferenceException: Object reference not set to an instance of an object.
at NShared.RecordingService.WorkerThread()