Unable to tune to certain re-mapped channels on Prime after 4.2.1 update

[2leftfeet]

I am not sure how to go about describing this, but I'll give it a shot.

I have another issue (yes I have quite a few recently), I am not sure whether I did something wrong or something changed in 4.2.1.

A while back, I had re-mapped a block of channels (about 9 of them) to a different set of channels numbers. Whenever I wanted to watch one of those channels, I selected the re-mapped channel number and watched away. But today, I have noticed that when I select one of those channels to watch, I get the dreaded "tuner not available" message. For whatever the reason, I am not able to tune to those channels (on HDHR Prime). This was the first time I tried one of those channels, since I updated the server on Thursday, so I am not sure if it something change embeded in 4.2.1 or something I did to screw it up. This issue is present on the kodi client, nextpvr client and server running nextpvr frontend.

It appears that issue affects only that block of channels, other re-mapped channels seem to work fine. It seems that npvr has lost the association of the re-mapped channels and their tuning information.

How did I screw up? Is there a way of fixing this?

I did try deleting the affected channels, and then rescanned to add those channels back, but this didn't seem to help.

The HDHR software plays those channels fine, as does VLC - so it's not the channels or the Prime, something else.

Help!


The attached log file contains the info from trying to tune to 4 of the 9 channels on the server using nextpvr in standalone mode.

[2leftfeet]

After testing more, I found additional very strange behavior. An example:

1. On one of the remapped channels (WFMZ accuweather 464 ->514 - available on both Prime and Connect), I tune to ch514 since the Connect has priority, NPVR selects the Connect, tunes to the channel and the correct channel plays (accuweather).

2. Then I tune to a different channel, only available on the Prime (CNN-600), it plays as expected.

3. Then I tune back to first channel (514 - available on both Prime and Connect) and instead of playing accuweather, WUVP plays instead. The problem with this is that WUVP (originally scanned as ch 514) has been and currently is disabled on all devices - even though it is disabled - it is still being tuned to by NPVR and plays instead of the re-mapped accuweather station. As a result, I am unable to tune to the correct channel with the Prime in this case.

Does this make sense?

Something has definitely gone South here - Help !!!

[2leftfeet]

sub,

I believe this is the fault of 4.2.1

I built a test server running 4.1.1. On the test, I re-mapped a few channels as I did on on my house server.
Everything worked well, as expected, including the remapped channels.

I then applied 4.2.1 to the test server, I did not apply the patch you made yesterday for the nrecord crash issue.
Sure enough, the same thing is happened as soon as 4.2.1 was installed - lost the ability to tune to the re-mapped channels on the prime and also, I when tuning to ch514, I get WUVP instead of accuweather, even though WUVP is disabled on each Prime tuner and accuweather is enabled, but remapped to 514.

Upon further testing, I recant my statement that only certain remapped channels won't play, Instead, I have found that all re-mapped channels will not play prime channels.

I then reverted back to 4.1.1, but was unable to recover the ability to play re-mapped channels.

Two different servers, one of those a total clean install, same result, 4.2.1 hoses re-mapped channels available to Prime.

[sub]

I haven't had a chance to look at the logs yet. Busy with day-job stuff today. Should be able to find some time later though.

[2leftfeet]

It appears that re-mapping is the issue. If I un-re-map the channel, it will play on the original channel number from the Prime scan.

[sub]

Can you see if this helps with remapped HDHR Prime channels?

[2leftfeet]

sub, initially, I thought no, no change. The patch still would not let me tune to the existing re-mapped Prime channels.

But, I found that if I deleted the remapped channels, then re-add them via device scan, then re-map those channels, the patch does work.

A little work on my part, but I can live with this - thanks!

[2leftfeet]

OK, re-scanned and remapped, all working, except ........

two Prime channels (neither re-mapped) won't play in Kodi but will with nextpvr client. I tried on multiple clients.

In the logs the two channels are 628- history channel and 670 - travel channel

[sub]

sub, initially, I thought no, no change. The patch still would not let me tune to the existing re-mapped Prime channels.

But, I found that if I deleted the remapped channels, then re-add them via device scan, then re-map those channels, the patch does work.

A little work on my part, but I can live with this - thanks!

The main change I made was to store a little more channel information at scan time. It sounds like this worked, and did the job.

I did make a second change, to try to make it work with your existing channels, which didn't have this extra info stored. Sounds like that didn't work - I'm not too worried about this one.

[sub]

OK, re-scanned and remapped, all working, except ........

two Prime channels (neither re-mapped) won't play in Kodi but will with nextpvr client. I tried on multiple clients.

In the logs the two channels are 628- history channel and 670 - travel channel

Those look fine from NextPVR side - ie, can see it's successfully opened the stream, and streaming it to Kodi. It sounds like Kodi's player doesn't like something about these channels.