Tuning wrong channel

[snagglewest]

Ok, this is a bit weird but..

I use NextPVR mainly for a recorder and to serve up live TV thru various Kodi appliances (several Raspberry Pi2 w/OSMC, a Linux box with Ubuntu 14.04 and several laptops with Win 8 & 10)

Over the last week or so I've had several occasions when I tuned a channel only to have the wrong channel come up. It's happened on both the Raspberry Pi2's and most recently on the Linux box about 30 min ago. The most recent time was about 7pm when trying to tune channel 1101 which is SCI-HD. I didn't catch exactly which channel actually tuned but I know it wasn't a close by channel so it wasn't a case of clicking 1 up or 1 down by accident. I don't recall which ones where the other times but I'll try and keep closer track next time it happens.

The only thing that's changed in the last few weeks was adding a second HDHR Prime but that's been 3 weeks or so and this problem started in the last week or so.

Like I said, weird. Anyone have any ideas?

Snag

Oops, forgot the logs

[ATTACH=CONFIG]42227[/ATTACH]

[sub]

The only time I remembered this happening for a user in the past, was when them had multiple channels with the same channel number. That's fine in NextPVR itself, but via Kodi you get a random one of those channels. Something for you to look into...

[snagglewest]

I'm not following? Do you mean merged channels? When I added the 2nd Prime I just imported the channel list from the 1st Prime which has been running for over 1 1/2 years without a hiccup. Can you give me a few hints please?

On another note, might you post a copy of the patch to fix the 0% buffer issue with live TV discussed here? I have the same issue but it's not on any one particular channel. Sometimes when surfing I get a 0%. No set pattern, sometimes it's the first channel, other times I can tune 5-6 or more times and then I get a 0%.

http://forum.kodi.tv/showthread.php?tid=...pid2347748

Snag

[sub]

I mean that there is nothing to stop you having the multiple channels with the same channel number. No idea why you'd want to do that, but some poeple have done it before (probably accidentally). It's usually people that have a mixed type of devices, where they might have an overlapping set of channel numbers. I don't know if that is what is causing the problem for you, but it's the only thing I'm aware of that can give these symptoms.

If it's not that, post the logs and the exact details of what happened and we'll take a look. The description is a bit too vague to look at the previous logs.

On another note, might you post a copy of the patch to fix the 0% buffer issue with live TV discussed here?

Attached.

[snagglewest]

Ok, just happened again at approx 14:38 on the linux box via Kodi 16.1. I had attempted to tune channel 1059 (HIST-HD) and channel 1066 (TNT-HD) popped up.

Here's a pic showing the wrong channel. The description is HIST-HD but its clearly TNT-HD
[ATTACHMENT NOT FOUND]

Here's a second attempt which tuned the right channel
[ATTACHMENT NOT FOUND]

I checked the channels and it doesn't appear I have any duplicates, they both show only 1 channel in the details

[ATTACHMENT NOT FOUND]

And of course the logs
[ATTACH=CONFIG]42236[/ATTACH]

Snag

[sub]

There ia few channel changes shown in that log. I can see it tuning to 1059 around that time. I can't see it tuning to 1066, so I don't think this can be a problem of NextPVR's making.

What you should probably do...wait until this next happens, then leave it viewing that incorrect channel so you can do some analysis.

I'd probably do this:
1) check the nrecord.log, searching the nrecord.log for the last occurrance of "/vchannel". This will show you what tuner and channel NextPVR has asked your HDHR Prime for (tuner2 channel 1059 in this example):

Code:

2016-06-19 14:39:04.358    [DEBUG][28]    Executing: C:\Program Files\Silicondust\HDHomeRun\hdhomerun_config.exe 132056C7 key 99042 set /tuner2/vchannel 1059

2) run up the HDHR Config utility to see what channel that tuner is tuned to.

[snagglewest]

So they how come is solved. A bit of background, when I posted the last logs I stopped the NPVR service and copied the logs I posted. NPVR was in the middle of a recording but no big deal. After restating the service the recording picked back up as it should have. The "show status" showed the #0 tuner recording as it should so I went to the HDHR web page and checked the tuner status. Much to my surprise I found the #1 tuner showing channel 1066 (TNT). A check of the HDHR config utility also showed tuner #1 on 1066. Here's tuner#0 with everything as expected.

[ATTACHMENT NOT FOUND]

Here's tuner #1 but note that NPVR isn't showing the tuner in use...

[ATTACHMENT NOT FOUND]

So the question now is why? I thought NPVR would check for the tuner in use and lock the tuner when it was in use and unlock it when it was done? Have I somehow discovered a strange bug or is there some other possibility?

Snag

[sub]

After restating the service the recording picked back up as it should have. The "show status" showed the #0 tuner recording as it should so I went to the HDHR web page and checked the tuner status. Much to my surprise I found the #1 tuner showing channel 1066 (TNT). A check of the HDHR config utility also showed tuner #1 on 1066. Here's tuner#0 with everything as expected.

Here's tuner #1 but note that NPVR isn't showing the tuner in use...

So the question now is why?

NextPVR's status is only going to list the things it knows are happening. ie, if it's started a recording on tuner #1, then it'd list that as in use. If it hasn't started anything on tuner #2, it has no way to know that the HDHR's tuner #2 is doing something (whether it was some other application using the device, or a recording started on previous run of the application), so you won't see anything listed for tuner #2.

I thought NPVR would check for the tuner in use and lock the tuner when it was in use and unlock it when it was done?

If you configure a tuner as being available for NextPVR, then it'll try using it. While using an HDHR, it locks the tuner, and unlocks it when done. If it returns an error, then the recording attempt is marked as failed, and an appropriate reason.

[snagglewest]

This is a bit odd. The there is only 2 things on the machine NPVR is on that could use the tuner. One is the HDHR viewer and until today, it's never been even opened so I'm fairly confident it wasn't holding the tuner. The only other thing is the HDHR setup program which was closed for weeks until I opened it this afternoon.

There are 2 HDHR Primes, the first is Device F3A which of course has tuner #0, #1 & #2 (total of 3). The second is Device 6C7 which has tuner #0, #1 & #2 (total of 3) for a grand total of 6 tuners available. 13217F3A is the first unit in NPVR and does the majority of the recording. 132056C7 is the second unit and does 99% of the live TV as I have "use reverse priority for live TV" set.

Just assuming something was holding the tuner, but I don't have any idea what it could have been, would the HDHR Prime tell NPVR the tuner was in use or throw an error of some sort? Or would it just connect to the tuner and start outputting the stream it was locked on? It just seems odd that the time where the wrong channel displayed was the same one the HDHR showed as open.

I'm not pointing fingers, just trying to figure out where things went sideways so I can avoid it in the future.

Snag

[sub]

Just assuming something was holding the tuner, but I don't have any idea what it could have been, would the HDHR Prime tell NPVR the tuner was in use or throw an error of some sort? Or would it just connect to the tuner and start outputting the stream it was locked on? It just seems odd that the time where the wrong channel displayed was the same one the HDHR showed as open.

I would expect it'd return some type of error. I'm not 100% sure NextPVR would handle it correctly though - since I don't have one of these tuners myself, and no way to test them here. ie, a lot of guess work involved in support for this type of tuners.