Recording Failed: Channel not found. Deleted?

[qam1600]

I am having a lot of failed recordings with error [Failed: Channel not found. Deleted?] At first, i was getting [Failed: No errors, but no data delivered. This is usually because the device failed to lock a signal.] and I assumed this was because I had ATSC 3.0 channels on all 4 of my HDHomeRun Flex 4K tuners. During a switch from XMLTV to Schedules Direct, I deleted all channels and rescanned, which was probably unnecessary, but removed ATSC 3.0 channels from tuners 2 and 3, since it appears to only use 0 and 1. The  no data delivered errors have stopped, but the  Channel not found errors are killing me. I thought it was only ATSC 3.0 channels that had that problem, but tonight I had it on a regular 1.0 channel (30.1). Log attached in case anyone has a chance to take a look, thanks!

[mvallevand]

Logs need to be zipped. If the problem is one ATSC 3.0 channels or if you are also using another server you would need this patch https://forums.nextpvr.com/showthread.ph...#pid577728

There.

[qam1600]

Logs need to be zipped.  If the problem is one ATSC 3.0 channels or if you are also using another server you would need this patch https://forums.nextpvr.com/showthread.ph...#pid577728

There.

Strange, I keep dragging the log attachment into the post but it doesn't actually get attached. I was able to attach logs to a previous post but somehow can't figure it out now. I'll try the patch, though.

[mvallevand]

And they are zipped and under 2MB?

Martin

[qam1600]

And they are zipped and under 2MB?

Martin

2.03MB, so that must be the problem. Here it is on Google Drive - https://drive.google.com/file/d/18qsOwhP...share_link

[mvallevand]

I got the file but the post processing spam makes it difficult to check for the problem. Maybe change your post processing to redirect to a file or NUL and dupliciate the problem using the new NShared and I can have a look. That is one reason the logs are a little bigger than expected.

Martin

[qam1600]

I got the file but the post processing spam makes it difficult to check for the problem.  Maybe change your post processing to redirect to a file or NUL and dupliciate the problem using the new NShared and I can have a look.  That is one reason the logs are a little bigger than expected.

Martin

Thanks, not sure how all outout from ffmpeg is getting into the nrecord.log, but I am redirecting it to nul now. I did have a recurrence of the failure on an ATSC 1.0 channel tonight, after installing the patched DLL. I found in the log was where it was setting up to record later:

2023-01-23 20:11:03.989 [DEBUG][9] [Bob Hearts Abishola] at 1/23/2023 8:30 PM
2023-01-23 20:11:03.989 [DEBUG][9] Requesting wake up for 'RecordingOID2259' [Bob Hearts Abishola] at 1/23/2023 8:28 PM

Around 8:28 nothing whatsoever happened except that I was watching a show that had previously been recorded. Nothing shows up in the log about this failed show until later:

2023-01-23 21:59:34.998 [DEBUG][49] {
"recordings": [
  {
    "id": 2259,
    "name": "Bob Hearts Abishola",
    "desc": "When Bob alerts MaxDot's longtime friend and sock manufacturer that he will no longer need their services, Dottie steps in to try to salvage their relationship; Abishola is uncomfortable while attending a drag brunch with Olu and Morenike.",
    "subtitle": "S04E11 - Twerk O' Clock",
    "group": "Bob Hearts Abishola_03230221",
    "startTime": 1674523800,
    "duration": 1800,
    "firstrun": true,
    "season": 4,
    "episode": 11,
    "original": "2023-01-23T05:00:00",
    "epgEventId": 1599086,
    "status": "failed",
    "size": 0,
    "quality": "QUALITY_DEFAULT",
    "channel": "WANF",
    "channelId": 8033,
    "blue": false,
    "green": false,
    "yellow": false,
    "red": false,
    "prePadding": 1,
    "postPadding": 1,
    "genres": ["Sitcom"],
    "reason": "Channel not found. Deleted?",
    "recurring": false,
    "recurringParent": 0
  }
]
}

I double checked the devices and 46.1 WANF is there on all 4 tuners.

[mvallevand]

Can you send the zipped logs anyway? I know the problem is that you rescanned and deleted channels after creating the recurring recordings I want to see how many you need to change.

Martin

[qam1600]

Can you send the zipped logs anyway?  I know the problem is that you rescanned and deleted channels after creating the recurring recordings I want to see how many you need to change.

Martin

Sure, attaching fresh logs now, but after I saw that all recurring recordings had channel 0 instead of the channel I had set them to record on, I deleted all of them and recreated. That was before I reported this problem. I could delete and recreate the recordings I am seeing seeing issues with.

[mvallevand]

Thanks for the logs they are actually quite helpful since I see a definite problem perhaps it was caused by the deleted. You have scheduled recordings that don't appear linked to a recurring recording but when the rules are run, upcoming recordings are not flagged for recordings because they are considered already scheduled.

When the scheduled time does arrive there is no log activity at all, normally on a failure it would try to record by unique id. Then they are marked as channel not found.

It will take 2 week for these orphaned schedules to clear out so sub definitely needs to look at this. You probably will no with your morning recordings whether you fixed it or not.

Also your ac4 to ac3 conversion is still spamming the logs. The logs capturing the data is deliberate to help diagnose bad scripts, but once it is working it is best to redirect. Another option would be to use an ffmpeg option like -v error or -v panic.

Martin