DVT Tuner remains locked after EPG update.

[Bobins]

I'm now regularly seeing a DVB-T tuner remaining locked after a daily EPG update. This is not every day but regularly.
It is not happening with EPG update on DVB-S tuners.

On a good day, on EPG update the dvb-t tuner log shows:-

2025-06-27 08:05:42.565 [DEBUG][4] locked=1, present=1, strength=84, quality=49  (took 47ms to check)
2025-06-27 08:05:42.565 [DEBUG][4] StartStream()@exit handle=1
2025-06-27 08:05:42.565 [DEBUG][4] StartStream succeded. Handle: 1
2025-06-27 08:05:42.565 [DEBUG][4] pipe client connected (NPVR_0ac7a17a-e851-45c3-be27-ef5b2cfa9e9b)
2025-06-27 08:05:43.124 [DEBUG][4] Processed 83848 bytes
............>
2025-06-27 08:06:42.710 [DEBUG][4] Processed 83848 bytes
2025-06-27 08:06:43.221 [DEBUG][4] Processed 83848 bytes
2025-06-27 08:06:43.827 [DEBUG][4] Processed 83848 bytes
2025-06-27 08:06:44.433 [DEBUG][4] Processed 83848 bytes
2025-06-27 08:06:45.168 [DEBUG][4] Processed 83848 bytes
2025-06-27 08:06:45.869 [DEBUG][4] pipe client disconnected (NPVR_0ac7a17a-e851-45c3-be27-ef5b2cfa9e9b)
2025-06-27 08:06:45.874 [DEBUG][4] Getting ready to stop stream
2025-06-27 08:06:45.874 [DEBUG][4] stopping stream
2025-06-27 08:06:45.877 [DEBUG][4] stream stopped
2025-06-27 08:06:45.877 [DEBUG][4] activeHandleTargets count = 0
2025-06-27 08:06:45.877 [DEBUG][4] No more active streams. Stopping device.
2025-06-27 08:06:45.879 [DEBUG][4] Graph stopping...
2025-06-27 08:06:45.881 [DEBUG][4] Graph reports state 'Stopped'
2025-06-27 08:06:45.881 [DEBUG][4] Graph stopped (async)
2025-06-27 08:06:45.881 [DEBUG][4] Removing filter  MPEG-2 Sections and Tables
2025-06-27 08:06:45.881 [DEBUG][4] Removing filter  BDA MPEG2 Transport Information Filter
2025-06-27 08:06:45.881 [DEBUG][4] Removing filter  MPEG-2 Demultiplexer
2025-06-27 08:06:45.884 [DEBUG][4] Removing filter  NPVR TS Mon
2025-06-27 08:06:45.884 [DEBUG][4] Removing filter  Capture
2025-06-27 08:06:45.884 [DEBUG][4] Removing filter  Tuner
2025-06-27 08:06:45.884 [DEBUG][4] Removing filter  Network Provider

On a bad day

2025-06-28 08:05:41.472 [DEBUG][4] locked=1, present=1, strength=84, quality=49  (took 47ms to check)
2025-06-28 08:05:41.472 [DEBUG][4] StartStream()@exit handle=1
2025-06-28 08:05:41.472 [DEBUG][4] StartStream succeded. Handle: 1
2025-06-28 08:05:41.472 [DEBUG][4] pipe client connected (NPVR_25473abe-be00-46e5-9a98-4a6e61199997)
2025-06-28 08:05:42.102 [DEBUG][4] Processed 83848 bytes
2025-06-28 08:05:42.771 [DEBUG][4] Processed 83848 bytes
2025-06-28 08:05:43.377 [DEBUG][4] Processed 83848 bytes
2025-06-28 08:05:44.143 [DEBUG][4] Processed 83848 bytes
2025-06-28 08:05:44.589 [DEBUG][4] Processed 83848 bytes

There is no pipe disconnection and the "Processed 83848" entry continues to infinity leaving the tuner locked.

The NPVR service has to be re-started to free the tuner

Full logs attached.

Ray

[mvallevand]

Out of curiosity are you having to trouble with recording quality when this happens? I appears the tuner isn't locked exactly since recordings and another EPG update even occurred even as that pipe thread [4] loops

It definitely finished parsing though and moved on to Freesat, I think I saw this log behaviour before and it is hard to spot if things actually work.

Code:

2025-06-28 08:06:42.558    [DEBUG][23]    TSSecionParserEIT returning 348 listings
2025-06-28 08:06:42.567    [DEBUG][23]    ProcessListings received 348 listings
2025-06-28 08:06:42.575    [DEBUG][23]    0 events for unknown channels
2025-06-28 08:06:42.625    [DEBUG][23]    About to save listings
2025-06-28 08:06:42.644    [DEBUG][23]    Listings saved
2025-06-28 08:06:42.646    [DEBUG][23]    CaptureSource.LoadAll()

Martin

[Bobins]

Martin.
Not having any issues with recording quality.
There are 3 other tuners on that DVB-t card so this problem hasn't impacted terrestrial recording.
The DVB-S is a separate card so isn't impacted either.

For some reason it looks like the DVB-t tuner periodically doesn't get / or doesn't respond to the instruction to end the pipe.

My NPVR system automatically reboots each morning to give the day a clean start. Before the reboot, it double checks the system isn't in use/recording. With this tuner stuck, the reboot doesn't happen because it sees it as a current recording.

Ray.

[mvallevand]

There are 3 other tuners on that DVB-t card so this problem hasn't impacted terrestrial recording.

Right but NextPVR is mainly using one tuner (you haven't adjusted your tuning priority to avoid the EPG screwing up your recordings) so the DVB-T recordings are happening on the tuner you indicate is locked and is changing frequencies.

Martin

[Bobins]

Martin,

Just checked this mornings logs and yes I agree, the tuner is changing frequency and recording OK then stopping the recording stream.
I just seems to regularly fail to close the EPG pipe after EPG update completion leaving the logs filled with nothing but 10000s of "Processed 83848 bytes" messages

Given the tuner works reliably starting/stopping recording streams, this would imply the problem is in the DVB-T EPG update area. (no evidence in the tuner log of an attempt to tell it to disconnect the stream and close the pipe)

The EPG data gathered from the DVB-T tuner does actually look complete.

Ray