Hello All, bear with me if I miss anything as forum posting is relatively new to me
I think I came across an odd bug running NextPVR on Debian. Since we have been hitting limits on available tuners recently I decided to pick up a second tuner card for our server. However, I can only get 7 tuners functional. As soon as I try to utilize tuner number 8, things start getting weird.
Troubleshooting around, I have come across a couple things:
1. the issue does not seem to be hardware specific. My original attempt was with two Hauppauge WinTV-quadHD tuners (one PCIe & one USB). Thinking it was a weird issue with different tuner chipsets, i bought a second PCIe card and the issue persists
2. trying to load a channel that utilizes tuner 8, it sits there trying to start the stream, but ends up failing with a 'transcoder exited' error
3. Here's where it gets weirder. If tuner #1 is being used (usually when something is recording) I get 'No tuner was available for the requested channel' and 'ERROR Device or resource busy while opening /dev/dvb/adapter0/frontend0' even though the tuner should be adapter7/frontend0
4. Even though I am unable to watch any channels on tuner 8, I can still scan for channels just fine (i was unable to confirm if this was actually using a different tuner to scan)
I have also attached the logs as requested in the wiki. A quick look at the end of device-adapter0.log shows the most recent attempt of the tuner trying and failing. I do not see a log file for adapter7
I am genuinely curious if anyone else is having the same issue I am as it's odd but seems to be easily reproducible from my end.
The device log for a recording starting at 20:00:47.839 on channel 20 does not stay on this channel for the full hour for this program. The device appears to switch to channel 5 at 20:05:05.852, then 32 at 20:06:08.361, then back to channel 20 at 20:07:11.439, then to 33 at 20:08:13.806, and jumps to a few more channels until it appears to stay on channel 26 for the rest of the hour.
Been running NextPVR on Windows 11 PC as backend and Kodi frontend on various devices in UK with Hauppage DVB-T2 quad tuner for some years without major issues.
From beginning of 2025 timers seem to disappear or not appear, even when requested on WebUI they sometimes fail to appear and recordings are not being made. Would be very grateful if anyone could help with solution. We did not see this behaviour previously so something seems to have changed.
I attach logs
Am contemplating full reinstall but obviously would prefer to avoid having to set up again!
All of a sudden I'm finding that one of my channels (Channel 4 in the UK) has no guide data at all on any of my Kodi clients using the NextPVR addon. When I log onto the server I can see there is EPG data for that channel and as far as I can see the settings are as per all the other channels (e.g. EPG Source = DVB/ATSC EPG).
The Server is on Windows 10, the clients are in Kodi using the NextPVR addon. I can of course post logs but unclear which ones (server and/or client) but also I recall reading somewhere that this is a known issue but I can no longer find that post and can't remember if that was a really old post or something current.
I have been primarily using 2 HDHRs with Xfinity cable cards for all of my recordings. But I also have a HDHR connected to an OTA antenna which picks up all of the local channels. I had initially kept these channels "separated" with the OTA channels having major.minor channel numbers and the cable channels using the cable company's channel numbers. I've also got lots of recurring recordings of type "Record Season (NEW episodes on this channel)" for the cable channels (800 range).
In preparation for cancelling Xfinity later this month, this afternoon I merged the corresponding cable channel with the the OTA channel for all of those local channels. I thought that by doing this, all of the recurring recordings would still work. However, I did notice that when the channels were merged, the channel kept the OTA major.minor channel number and the OTA name (which sometimes matches, but usually is slightly different) rather than keeping the cable channel number/name (which is what all of the recurring recordings point to). Should all of those recurring recordings have gotten updated to point to the "new" merged channel?
But, now tonight, all of my recurring recordings are failing with the error "Channel not found. Deleted?".
I had the thought that maybe I needed to do an EPG update afterwards to get the specific recurring episodes to reschedule on the "new" channel, so I did an Empty EPG and Reload EPG before Chicago P.D. was scheduled to start. But, it still failed with the same error. Looking at the log from where I emptied the EPG and reloaded it, I see:
I'm not sure why it would have been "already pending", since the empty EPG & reload EPG should have gotten rid of any of the previously scheduled recurring recordings, right?
The Late Show With Stephen Colbert tonight appears that it did schedule:
Code:
2025-02-05 20:50:52.549 [INFO][18] UpdateRecurringRecording(213, 'The Late Show With Stephen Colbert'):
<Rules><EPGTitle>The Late Show With Stephen Colbert</EPGTitle><ChannelOID>8248</ChannelOID><ChannelName>WCCO-DT</ChannelName><StartTime>2019-10-23T03:35:00.0000000Z</StartTime><EndTime>2019-10-23T04:37:00.0000000Z</EndTime><PrePadding>1</PrePadding><PostPadding>11</PostPadding><Quality>0</Quality><Keep>0</Keep><RecordingDirectoryID>[Recordings3]</RecordingDirectoryID><OnlyNewEpisodes>true</OnlyNewEpisodes></Rules>
2025-02-05 20:50:52.955 [DEBUG][18] LoadListingsMatchingTitle(channel=8248,title=The Late Show With Stephen Colbert)
2025-02-05 20:50:52.956 [DEBUG][18] - Potential episode at: 2/5/2025 10:35:00 PM
2025-02-05 20:50:52.957 [DEBUG][18] ...check IsValid()
2025-02-05 20:50:52.957 [DEBUG][18] ...scheduling episode
And when I look at the TV Guide screen, it is highlighted in red. I guess that I will see if it records OK. And looking at tomorrow in the TV Guide, I am seeing shows highlighted in red like they will be recorded. Maybe Chicago P.D. was just a "fluke" and all of the other recurring recordings will work. I guess I'll see...
![[Image: YWBNG9l.png]](https://i.imgur.com/YWBNG9l.png)
