Channel numbers messed up by HD mux

[jpsa]

There have been some changes to channels recently, so I deleted all the channels and performed a rescan. All the expected channels were found, but most (perhaps all) of them had the wrong channel numbers. I did this scan three or four times, at different times of day, and the behaviour was consistent.

I noticed that the mux containing the HD channels was scanned first, and that those HD channels had been allocated the first few channel numbers (where SD channels ought to be). So I generated a modified tuning config file which omitted the HD mux, and did a rescan using it. Now all the channel numbers are as expected.

Is NextPVR failing to pick up the channel numbers from HD channels properly?

Logs from scans both with and without the HD mux are attached. I'm using 3.1.1 with the R1a patches.

[Reddwarf]

What happens if you scan the HD frequencies last?

[jpsa]

Now that's not what I was expecting! If I scan the HD Mux last, the HD channels come in with their correct channel numbers.

[Reddwarf]

That what I figured

[jpsa]

Any chance you could enlighten me, as I'm still puzzled?!

I can see that, scanning the HD mux first, if for some reason nPVR can't get the HD channel numbers, it might allocate them from 1 upwards. Then when I later scan the SD muxes, even though it knows the channel numbers it can't use them because those numbers are already in use. So the SD channel numbers all get messed up too.

But I'd expected scanning the HD mux last to get the SD channels right, and then put the HD channels into the first free channel numbers (actually 8, 26, 48...), but it didn't. It got their correct numbers (73, 101, 102...).

Why does scanning the HD mux last mean that nPVR can determine the HD channel numbers properly?

[Reddwarf]

Npvr does not utilize free channel numbers, to my experience. When it finds new channels it assigns them numbers from the highest existing in the databse. How the inner workings of that is, I don't really know. Maybe Sub can answer that.